About me · Luis Aldrich Guzmán
Luis Aldrich Guzmán González, known online as LuisAldrichGuz, is a Full Stack Developer based in Mexico City. He currently works at Secretaría de Desarrollo Económico de la CDMX as Technology Advisor to the Secretary and Head of the Technology Department. He is also Founder of Whools?, since 2020. He holds a degree in Computer Systems Engineering from Instituto Tecnológico de Iztapalapa (TecNM). He is currently studying a Master's in Software Engineering at UNIR, and is certified in UX/UI.
Where he has worked, what he built at each place and the technical detail of every project is on the experience page.
Software
Desktop with WinForms and WPF, mobile with React Native and Flutter. C# is my favourite and I'm not about to justify it.
Backend
The part that can be art or an absolute disaster, depending on who you put to work on it. It's the one I spend the most time on. I love it when the database is properly art: efficient, secure and scalable, the holy trinity. I'm used to doing my own deployments, so the scripts that make my work easier always come from me.
About me
My biggest strength is curiosity, and the dopamine of watching something work. I'm obsessive about it: I finish my work in React and go build my own things. I once had a model analyse this portfolio and it told me I tend to over-build. It wasn't wrong. Coding is social work, people are going to read it. I try to make mine explain itself; if it needs comments to explain it, it's badly written. Video games, vinyl records and science fiction on the Kindle.
Studies
What I studied and what I'm still studying, plus my UX/UI certifications. Although honestly, most of what I use day to day I learned outside the classroom.
Databases
Relational and NoSQL. I mostly consume them, but designing them doesn't scare me. What does bother me is an unnormalised database: a spreadsheet with delusions of grandeur.
Frontend
I've had an eye for detail since I was a kid: I learned HTML and CSS, and at 14 I won a SOLACYT contest with a page to encourage reading, a Duolingo for reading back when Duolingo still wasn't a thing in Mexico. I like things to look good and be efficient, and I'm a minimalist. What really teaches you is sitting down to watch someone use what you built, and biting your tongue.
Games
This is what I want to do for a living. I like it when everything reacts, and building the logic underneath. The front page of this site is one of mine: you can play it, and it has enemies, bosses and multiplayer.
AI
I've led teams of developers, and now I also direct AI agents. I've been an entire technology department on my own, and with agents I cover far more ground in less time. I'm against vibe coding. I get why it looks like you can ship things that way, but when it all falls down and you don't know which part is failing, that's when the fun starts. I work with local AI and with remote models. In government there's data that can't go through somebody else's server.
Tools and technologies
- AWS: Cloud when the project needs room to grow. And when someone else is footing the bill.
- C#: My favourite language and I'm not justifying it. Desktop, internal tools and Unity — I do everything with this one.
- Docker: Everything on my server runs in containers. No more "but it works on my machine".
- Figma: I'm not a fan of it, I feel faster in code. But for demos it's indispensable, and I do know how to use it.
- Git/GitHub: No history, no way back. Everything of mine lives in Git, even the stuff I'm embarrassed about.
- Java: Where I learned to think in objects and architecture. And to write an awful lot to say very little.
- Linux: My server and my desktop. Yes, I use Arch. No, I won't bring it up again.
- Node.js: JavaScript on the server too. One language end to end, and one excuse fewer.
- Python: Scripts, data, and anything that has to be ready today.
- React: My favourite. It's my work wife and my testing ground: I know its flaws and its virtues.
- Unity: Where I've been making my games for years: mechanics, physics, enemies and bosses.
- Computer Support and Maintenance: Before I learned to code, I learned to fix computers. So I know the tool I work with inside out.
- Computer Systems Engineering: The degree I spent years waiting to study, the one that stands for what I love and what I want to do my whole life: systems.
- Master's in Software Engineering: Something on the side, mostly for the master's title, but honestly nothing I hadn't already learned. At UNIR because I work and I need it fully remote.
- Game Design: What makes a game feel good. It's the hard part, and the one nobody sees.
- Angular: For when the project grows and you need everyone writing the same way. It has a LOT of opinions, and sometimes that's exactly what you want.
- Blender: I make the models here. I know just enough for it not to show that I'm no artist.
- Django: Expert level. Batteries included: when what's urgent is getting the API up, I don't pick fights with anyone.
- FastAPI: Expert level, and you're using the proof: the API behind this site is FastAPI. Async, typed, and the docs write themselves.
- Firebase: To get going without standing up a server. Perfect right up until it isn't.
- Flask: The bare minimum to stand a service up. The whole point is what it doesn't bring.
- Flutter: One codebase, two stores.
- Kotlin: Android without all of Java's ceremony.
- Laravel: PHP with structure. If the system already runs on Laravel I'll maintain it, no problem... and if it's properly legacy, I'll also tell you the truth: tearing it down and rebuilding comes out cheaper.
- MongoDB: For when the data genuinely doesn't fit in a table. Genuinely, though.
- MariaDB: The one I started with. I'm fond of it and it still gets the job done.
- Oracle: The enterprise world. Heavy, expensive, and you still have to know your way around it.
- PostgreSQL: The one behind this site, and my default pick. I almost never regret it.
- React Native: Everything I know about React carries over to mobile. What you have to learn on top is the native bridge and navigation.
- Tailwind CSS: Expert level, and this site is the proof: all of it runs on Tailwind, with its own palette and its own shapes layered on top. It looks horrible for the first few days and then you never want to go back.
- Three.js: The front page of this site is a 3D game and the About section is a solar system. The orbits, the shaders and the physics are all hand-written.
- Vue: This one I'm an expert in, though the joke writes itself: not every project needs artillery... or skills, it's what a backend dev grabs when they get stuck doing the front.
- Claude Code: I've used it since the day it launched, literally, and it's what I open every day. I pay for the Max plan myself, for my own projects: my games and even the 3D modelling.
- Claude API: Support chat inside the system, reports that write themselves in PDF, Excel and PowerPoint, agents that research and analyse data, vision to read documents and social media automation. Some of the things I've built, and the possibilities are endless.
- Agents and MCP: An agent with no tools is an expensive chat. With MCP I give them access to the database, the files, Blender and my server, and I run several in parallel without them stepping on each other.
- Local models: Facial recognition, audio and 3D model generation, and querying the notes from all my projects. It all runs on my own RTX 5070. This is where I get to play, and where I put whatever can't leave the machine.