
Another React Website 🥱?
Maybe some again?
I like using languages that solve problems, not just ones I
happen to know well. “We’ll use it because I know it” is not a good enough reason!
I prefer frameworks that do the heavy lifting for me. And no—“React has a big ecosystem” isn’t a strong argument. By that logic, we should all just stick to plain JavaScript—it has an even bigger
ecosystem!
And maybe we should, for a simple form app, I dont need a 50MB webpack optimized react ecosystem,
just think about it!
ORMs are the worst. There’s no real standard across
them, and if you care about optimizing queries, you’ll eventually need to learn how to write raw SQL anyway. So unless your product is just a bunch of CRUD operations, there’s no point investing
heavily in an ORM.
I’m not fully driven by developer experience. Do
you think German automotive engineers were obsessed with “engineering experience”?
No—they were focused on driving experience.
Similarly, the only experience that truly matters in software is User Experience.
Because at the end of the day, no user is ever going to say,
“Wow, this was built with Svelte!” or “They used an OOP approach—so cool!”
User don’t care about the tech stack.
User care about performance, reliability, intuitive design, and a bug-free experience.
That’s what matters to user. Everything else is just an implementation detail.
→ All case studies, with stack and numbers