State-of-the-art engineering, inside and out: Why I completely revamped my website
D.Msi: Why I killed my old web portfolio
A few days ago, I looked at my website and realized it didn't represent me anymore. It looked like a standard freelancer's dark-mode portfolio. But I don't just write code; I architect systems. So, I tore it down and built Identity V.2.0.
If you've been following my work, you probably noticed the massive visual shift. Gone are the neon lights, the dark backgrounds, and the "cyber-hacker" vibes.
Why the sudden change? Because the software I build isn't a toy. Platforms like SEEM (which handles +600 daily active users), morfoly (which I will make public soon) and LinkEdu (my own EdTech startup) deal with complex business logic, AI integrations, and extreme operational pressure.
I wanted my digital home to reflect exactly that level of engineering: clean, transparent, and entirely focused on the idea that aesthetics should be on par with the engineering behind the logic.
Field Note
“if the systems running in the backend reach a certain level of sophistication, the systems' user interface must also reach that same level of sophistication”
Jorge Darío
Systems Architect & Founder
Why is everything in English now?
I am proudly based in Mérida, Yucatán, Mexico. But software has no borders.
The problems I solve every day—optimizing PostgreSQL queries, achieving 5ms latency, scaling AI agents, and currently learning Go for raw backend speed—speak a universal language. English is the default language of elite software engineering, and my goal is to build world-class SaaS products. If I want to build systems for the world, I need to speak to the world.
And hey, if you are a local client from Mérida, Yucatán reading this, don't worry. We can still talk about your next software architecture over some papadzul jaja.
What to expect from these "Essays"
I don't like traditional blogs. I won't be posting generic tutorials like "How to center a div in CSS" here.
This space is my technical journal. Here is what I'll actually be writing about:
- Architecture breakdowns of how I scale platforms like LinkEdu.
- Why I'm shifting parts of my backend infrastructure to Go Lang.
- Deep dives into Web Application Firewalls (WAF) and bare-metal VPS management.
- The reality of being a software architect and failing chemistry in high school.
Would you like to visit the old page?
Reader Signal
2 people have reacted.