Like most people, I was building simple websites — themes, plugins, client work. It paid the bills, but after a point, everything started to feel repetitive. I was assembling websites, not really building them.
That’s when I got curious.
I started exploring what happens beyond the frontend… how data flows, how APIs work, how real applications are structured. That curiosity pulled me into learning Node.js. Then came Next.js — and that changed everything.
For the first time, I wasn’t just designing pages. I was building complete systems:
– Frontend + backend together
– Faster performance with server-side rendering
– Clean, scalable architecture
It felt like leveling up from “website creator” to “product builder.”
And somewhere along the way, I found my own style — what I call vibe coding.
For me, it means:
Building things that feel smooth, fast, and intentional.
Not just functional, but enjoyable to use.
Code that isn’t just working… but clean and future-proof.
Going full stack wasn’t a sudden decision.
It was a gradual shift — from comfort to curiosity to capability.
And honestly, it was the best move I made.
If you’re still in that phase where things feel repetitive, that’s probably your signal.
There’s always a next level — you just have to step into it.
I’ve been razzmatazzing and flibbertigibbeting with Claude Code and somehow ended up with a new yels.dev.
It finally feels like me: simple on the surface, slightly complicated underneath, and very much alive.
You can see who I am, what I do, the work behind Herodot, RaptorLabs, CyberLink Security and Solmint, plus a selection of projects I’ve built across AI, cybersecurity, Web3, product systems, education, archives, and experimental digital spaces.
The simple-on-the-surface, layered-underneath idea comes through so clearly in the presentation. I especially like how the project archive turns the site into something to explore rather than just a résumé of links.
After 6+ years of building websites, I’ve learned to ask one question early: “Who will update this after launch?”
The answer shapes the CMS, navigation, and handoff.
Fellow developers, what’s one question you always ask before starting a project?