You seem to agree that two is not a good number. Better bring four then, so that you're not left with only two after your mishap.
Or bring only two, but step on one immediately, to get rid of the cursed pair situation, and also to get the clumsiness out of the way early. Old sailor's trick.
I wrote this coincidentally a few days before the recent news about Tailwind’s layoffs and revenue downturn due to AI’s impact on doc use leading to their paid product distribution being affected.
In my own AI-heavy workflows, I’ve noticed that AI tools are great at generating layouts quickly, but the results tend to converge on a certain look and feel and often lack polish around responsiveness and design details.
Templates still accelerate my builds. They encode decisions, constraints, and taste that I don’t want to recreate from scratch... even with the help of a coding agent.
As AI becomes more central to how we build things, do templates continue to retain value, or is this just a transitional phase?
I've made a few small projects that were built almost exclusively with Cursor (if that's considered vibe coding, I'm not sure). They don't have many users.
A few weeks ago I built a very simple metrics tracker that I had been looking for myself... a middle ground between complex observability platforms and tracking a number yourself and then finding a way to visualise its change over time.
I had had the idea and the domain registered for years and recently just took the leap to put it out there.
reply