fsd
fsdfgdfg
- Obtained
- Mar 275760
- Verification code
- 333
3333333
Living CV
Alejandro Aguilar Torices
Construyendo | Conectando | Contribuyendo
Soy estudiante autodidacta de administracion de sistemas Linux y DevOps, con un gran interés en el desarrollo tecnológico y una alta motivación para aprender y crecer profesionalmente. Soy autodidacta, lo que me ha permitido desarrollar autonomía, habilidades para la resolución de problemas y una curiosidad constante por entender cómo funcionan las cosas.
Ahora busco dar el siguiente paso: trabajar en equipo, aportar valor a proyectos reales y seguir desarrollando tanto mis habilidades técnicas como las de comunicación y colaboración.
Estoy disponible para una incorporación inmediata y con total compromiso.
Si mi perfil se ajusta a lo que estás buscando, por favor, pónte en contacto conmigo.
Certifications
What I have sat the exam for, and where each one can be checked.
AWS Certified Solutions Arquitect
Amazon Web Services
- Obtained
- Nov 2025
Foundational certification covering core AWS services, pricing and the shared responsibility model.
VerifyCertified Kubernetes Administrator
CKA
Application deployment, configuration and observability on Kubernetes.
Verify33333
3333
- Obtained
- Feb 222
- Verification code
- 2222222222
222222
Courses
What I am working through, and how far along I am.
100%
sddd100%
System Design Interview: An Insider's Guide95%
lol62%
Rust FundamentalsReading
Books I have finished, and what I actually took from each.
Reading it now · 560 pages
The Rust Programming Language
Placeholder — replace with your own notes. Still working through it alongside the course; the ownership chapters are worth the whole book.
What I took from itThe borrow checker is not in the way of the design — it is asking a question about the design that I had been avoiding.
Finished May 2026 · 144 pages
Shape Up
Placeholder — replace with your own notes. Thin, opinionated, and mostly about a team size I have never worked at — but the framing of appetite over estimate stuck.
What I took from itFixing the time and letting the scope move is the only version of a deadline that has ever held for me.
Finished Mar 2026 · 616 pages
Designing Data-Intensive Applications
Placeholder — replace with your own notes. The one book here that changed how I argue about storage rather than just what I know about it.
What it does wellEvery chapter builds the vocabulary the next one needs, so by the end the hard parts are being described in words you already own.
What I took from itThat most 'database choice' arguments are really arguments about which failure you are willing to live with.
Finished Jan 2026 · 448 pages
Refactoring
Placeholder — replace with your own notes. A catalogue more than a narrative, and better for it — you read the parts you need on the day you need them.
What it does wellEvery move is shown as a sequence of steps small enough that the code never stops working in between.
What I took from itThat refactoring is a separate activity from adding behaviour, and mixing the two is what makes both of them risky.
Finished Nov 2025 · 352 pages
The Pragmatic Programmer
Placeholder — replace with your own notes. Short chapters that each land one idea, which makes it a book you can put down and still be reading.
What it does wellIt gives names to habits I already half had, and a name is what makes a habit arguable.
What I took from itLeave the code better than you found it, and keep the fix small enough that you actually make it.
Finished Aug 2025 · 256 pages
Grokking Algorithms
Placeholder — replace with your own notes. The drawings do the explaining, which is unusual and works.
What it does wellIt picks a handful of algorithms and shows each one properly, instead of surveying forty of them badly.
What I took from itBig-O finally stuck once I had a picture of the growth rather than a table of it.
Projects
What I have built — every milestone, and every thing that broke on the way.
eefsefe
Private repository
- This project
Nothing logged here yet
The rail runs unbroken from end to end — no checkpoints have been written for this one.
A Frutiger Aero-styled personal site that doubles as a changelog for everything I'm learning and building.
- This project
Take the gear along the rail
It walks the project on its own, from the start to today. Grab it and hold to go faster, or back — wherever it is, that part of the story is here.
- Achievement
Project kickoff
Scoped the idea: a retro-to-modern reveal, badges, courses with hand-updated progress, and a project timeline.
What it taughtAstro Content Collections map almost perfectly onto 'add a file to add content' — no CMS needed for a single-owner site.
- Development
Design language pass
Built the Frutiger Aero token system: glass panels, glossy buttons, bevel shadows, gradients.
What it taughtLayered box-shadows (inset light + outer soft shadow) get you 90% of the way to a convincing glass bevel without images.
- Development
Retro shatter interaction
Implemented the 5-click crack overlay and GSAP shatter transition from the 2000s landing screen into the modern site.
What it taughtSplitting a layer into clipped shard elements is cheap to animate and reads as 'breaking glass' with the right easing.
- Error
The field of grass changed size with the window
The grass strip was sized in vh while the photo behind it was sized by viewport width, so the slice of the picture on show swung with the window's shape — 43% of it on a squarish window, 18% on an ultrawide, which is the hazy far distance rather than the sharp foreground.
How it was fixedSized the strip as a fraction of the height the photo actually renders at, so the strip and the image finally scale off the same number.
What it taughtTwo lengths that have to agree must be derived from one another, not merely tuned until they match on the monitor in front of me.
- Development
Courses became tubes of falling spheres
Replaced the progress bars with a small rigid-disc simulation per tube, fused into a liquid body by an SVG threshold filter.
What it taughtThe merging is purely a rendering decision — the simulation has no idea it is liquid, which is why spheres in mid-air still read as spheres.
- Error
Nothing in a tube ever lost energy
The liquid never quite came to rest. The viscosity term was applied as pow(DRAG, dt) with DRAG set to 1 — and 1 to any power is 1, so the decay the code described had never once run.
How it was fixedDropped it to 0.99. The pile settles now instead of simmering, and the frame loop can park itself once nothing is moving.
What it taughtA constant sitting at its own identity value is a disabled feature wearing the costume of an enabled one. The comment above it had been describing an intention, not the behaviour.
- Development
Certifications became a stream of bubbles
One clock drives the whole row as a conveyor: each bubble's phase is that clock minus its place in the queue, so pausing the stream stops the clock rather than any single bubble.
What it taughtPausing one bubble on its own would let the one behind it walk straight through it — the queue has to be one object.
- Achievement
Every section is its own object
Badges, tubes, bubbles and now a zip: no section of the page is a list of cards any more, and each one is driven by its own small simulation.
A bare-metal 3-node k3s cluster for practicing everything from the CKAD syllabus.
Private repository
- This project
Take the gear along the rail
It walks the project on its own, from the start to today. Grab it and hold to go faster, or back — wherever it is, that part of the story is here.
- Achievement
Cluster bootstrapped
Installed k3s across 3 mini PCs, set up a private container registry.
What it taughtetcd is picky about clock drift between nodes — chrony fixed a cluster of mystery errors.
- Error
Nodes kept dropping out of the cluster
Workloads were evicted at random and the control plane declared healthy nodes NotReady, several times a day.
How it was fixedThe three machines were on a switch that reordered traffic under load; moving the cluster onto its own VLAN and raising the kubelet's node-status timeout ended it.
What it taughtRead the events on the node before the events on the pod. The pods were the symptom, and I spent two evenings debugging the symptom.
- Development
Added observability stack
Deployed Prometheus + Grafana via Helm, wired up basic node and pod dashboards.
- Development
Paused for exam prep
Shifted remaining time toward CKAD practice exams; cluster left running as a sandbox.
Open to help, work, contribute
If any of this overlaps with something you're building, I'd like to hear about it.
Say hello