In short, Next.js allows me to deliver solutions that are technically sound and aligned with business priorities—speed, scalability, visibility, and efficiency.
When choosing a framework, I don’t just think about code. I think about how it impacts the entire development cycle and ultimately the business.
Over time, Next.js has become my preferred choice
Here are a few reasons why:
👉 Static Site Generation (SSG)
When pages can be pre-built and served instantly, apps feel lightning fast. This means less operational overhead, happier users, and better scalability at lower cost.
A new framework just dropped.
Clients want it. Devs want it.
But is it ready?
The risks:
• Untested in production
• Weak community/support
• Hidden limitations
• Slower delivery from new workflows
Innovation is great. But sometimes the best choice isn’t the newest
I hate loading screens — they’re just bad UX.
When I first used React, everything rendered at runtime and it drove me crazy.
Next.js changed that for me. SSR = instant pages, better SEO, smoother experience.
Job interview requirement:
- We need you to take this interview + coding test, all created by AI, but you can't use AI for the coding test.
Not ridiculous at all 😂
Asking Claude to build something simple be like:
Me: Can you make a cheese and ham sandwich?
Claude: Sure. And since I am at it, let me bake you a 10-layer chocolate, vanilla, and gold cake.
Me: Wait, you only baked me the cake that I didn't ask for. Where is my sandwich?😂
Lately, most of Google's products have become the opposite of what they used to be: uncluttered and easy to use.
Today, I say goodbye to Google Chrome!
If you think your tech stack is making you a better developer, think again.
You are the reason why your app is badly coded, not the tech stack!
Stop being lazy!