@Surendar__05 Absolutely, vibe coders inject bugs and we will clean up their shits and it will frequently.
Software engineers can adapt to vibe coding but vibe coders can't
I think going into 2026, as a developer, you'll have to accept that AI is "a thing" and won't go away.
Take advantage of it or ignore it (if you can) but don't hope for it to disappear.
I think there's a bubble that will burst at some point but that does not imply that the technology will disappear.
It does have its use and it does change things.
But just to be clear: AI is NOT that thing that will make you as a developer obsolete. Vibe coding is not the future for devs. It may be good for one-off, throwaway software but that's it.
Instead, I convinced using & controlling AI assistants is the future. Just as we've used auto-completion before AI.
Obviously, the amount of usage will differ on the problem you're tackling and it's easy to rely on AI too much.
I've said it before: Don't limit your skill level to that of the AI you're using. Instead, combine your skill & knowledge with AI assistants.
At least, that does work for me.
There are no limits anymore. Anyone can do anything. The only limiting factors are agency and ambition.
Never has a college degree, work experience, network, even the accumulation of knowledge been worth less.
You can just ship things.
@nextjs This kind of framework which has been updated frequently every month for a couple of months, to be honest we as engineers need to carefully use in our production grade development.
Who knows when it breaks and we debug hours and lose productivity.
โฒ ~/๐๐๐๐๐๐/๐๐๐-๐๐๐๐๐๐/ ๐๐โ
I'm announcing 22 $1,000USD grants for foundational open source projects.
I selected a set of amazing contributors who are working on diverse problems in the JS/TS ecosystem.
Since I've mostly spent time on React (web) and Next, I've specifically chosen to support people working in other areas: Bun, Nitro, Vue, Nuxt, React Native, Viteโฆ
โฆ but also the foundations often overlooked, like the people quietly maintaining half the Node.js ecosystem, testing infrastructure, inheriting mature projects like Lodash, or contributing to TC39.
I plan to do more of these over time. There are a ton of people who deserve these and I haven't gotten around to yet, so expect more soon. I'm also always on the lookout for supporting the lesser-known up-and-comers, tips welcome ๐
Part of this is the financial contribution, but also very importantly: recognition. (PS: these are personal, not affiliated with Vercel, and fully unconditional)
https://t.co/GH17tOB1dg
@timneutkens@nextjs Yeah, true the last major release was last year, but there have been quite a few incremental updates and experimental features since then.
Migrating large projects can be painful (and not always fully backward-compatible).
@kinder_grinder@nextjs It's not about old and new, it's all about stability. I know some people don't want stability over excitement โ they chase trends, updates, and the next big thing. But in the end, stability is what keeps things running smoothly when the hype fades.