With AI, You Need Fewer npm Packages Than You Think
How AI shifts the build vs. buy decision for npm packages — when to use external libraries and when to write custom solutions for long-term stability.
How AI shifts the build vs. buy decision for npm packages — when to use external libraries and when to write custom solutions for long-term stability.
How deep CSS expertise made me resist Tailwind for years — a personal story about when experience blinds us to innovation and why experts can be wrong.
After working with Next.js, I went back to single page applications for admin interfaces. Here is why an SPA fits apps that live behind a login.
My detailed experience building a Next.js app with Claude Sonnet 4 in agent mode — exploring benefits, pitfalls, and why human oversight still matters.
How to choose the right tech stack for each project: when plain HTML is enough, and when to use a static generator, Next.js or a separate backend.
How I built Old School Games, a site for playing classic DOS games in the browser, with DOSBox and a deliberately old-school, server-rendered stack.
How I built and deployed a quiz website in 2 hours with a Claude Sonnet 4 agent — what the AI handled well and what still needed my decisions.
Why AI coding tools might push web development toward more conservative technology choices, long-term architectural thinking and less framework churn.
An honest look at the Next.js App Router and Server Components in production: authentication, mental overhead, loading states and hidden complexity.
Why I started this blog: practical writing about web development that favors simple, pragmatic solutions over hype and unnecessary complexity.
New posts about small software, games and the web. Subscribe via RSS or follow @RobertLibsansky on X.