In this industry, 15 years is enough time to watch "cutting edge" become "legacy slop" three times over. For me, it hasn't been a climb up a corporate ladder; it’s been a 15 year long debugging session.
Looking back, the stack has changed, the titles have gotten fancier, and the pots of coffee have gotten significantly larger, but the core drive the need to know exactly how the machine works hasn't moved an inch.
The Low Level Roots (C & Memory)
Most people start with a framework. I started with a compiler and a headache. My true beginning wasn't in web dev; it was in the C based GTA modding scene.
Those years were a masterclass in pain and precision. When you’re dealing with memory offsets and hooks, you don’t get a helpful error message in a console; you get a system crash. It was a cycle of sleepless nights staring at VS Code, manually calculating logic that most modern devs take for granted. That foundation in low level C is what defined my "hardware first" mindset. It’s the reason I’m so obsessive about server hardening and infrastructure today I like to know what’s happening at the metal.
Scaling the Chaos: FiveM, Infinity, and Cadence
Eventually, that low level logic met the community driven world of FiveM. I still make FiveM resources today because there’s a pure, sandbox energy there that you don't find in SaaS.
But as my stack shifted toward TypeScript and Node.js, the projects grew into systems. Infinity Bot List (Omniplex) and Cadence were where I learned about scale. It was no longer about making one menu work for one person; it was about keeping the lights on for thousands of users simultaneously. It’s where I realized that a "pretty UI" is just a mask if the backend architecture isn't rock solid, the whole thing is just a house of cards.
The Professional Pivot: Emberly & NodeByte
The last few years have been about consolidation, taking everything I learned from the modding forums and the bot lists and turning it into something professional.
CordX evolving into Emberly was that turning point. Merging Nexium into that ecosystem earlier this month was the final piece of the puzzle: creating a unified hub for developers. It’s a massive build that requires every bit of the 15 year history I’ve got.
Currently, that history is being poured into NodeByte and the public beta of ByteSend. Shipping a email delivery platform like ByteSend feels like the ultimate test of everything I’ve learned about reliability and data integrity.
The Constant: Coffee & Code
Fifteen years later, and some things never change. I’m still powered by dangerous amounts of caffeine. I’m still the guy who would rather spend 12 hours fixing a bug than 12 minutes admitting defeat.
I’ve traded mod menus for VPS infrastructure and C hooks for full-stack ecosystems, but the feeling of a clean deployment still hits the same. To the next 15 years of broken builds, fresh pots of dark roast, and never settling for "good enough."
Stay caffeinated. Stay real.