21–30 of 312 posts
The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
The issues with Claude Plays Pokemon (an overview here: https://arstechnica.com/ai/2025/03/why-anthropics-claude-sti... ) is essentially due to the 200k context window being finite, which is why it has to use an intermediate notepad. In the case of coding assistants like Cursor, the "notepad" is self-documenting with the code itself, sometimes literally with excessive code comments. The functional constraints of code are also more defined both implicitly and optionally explicitly: For Pokemon Red, the 90's game design doesn't often give instructions on where to go for the next objective, which is why the run is effectively over after getting Lt. Surge's badge as the game becomes very nonlinear.
Although, both vibe coding and Claude Plays Pokemon both rely on significant amounts of optimism around the capabilities around LLMs.
Most tech savvy places will avoid it, most good programmers will never encounter it. A bunch or us will make a career out of fixing the mess it makes after it explodes.
My first real job was doing just that at a broker trader which lost 10m on a trade made by an Excel spreadsheet that used a stale yahoo finance API to get exchange rates.
The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
Speeding up your work does lead to job loss. If some developers can suddenly be 3x as productive than a company doesn't need as many engineers.
The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
Speeding up your work does lead to job loss. If some developers can suddenly be 3x as productive than a company doesn't need as many engineers.
"ever since I started to share how I built my SaaS using Cursor" random thing are happening, maxed out usage on api keys, people bypassing the subscription, creating random shit on db as you know I'm not technical so this is taking me longer that usual to figure out - (leo, 2025)
The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
Wait 10 years, though.
The more I work with LLMs and try things like "vibe coding" the less worried I am about AI taking my job any time soon. In the right contexts, I find LLMs can speed up my work a lot. But it's nowhere close to being able to replace what I do.
I work at a company relatively well-known in Startup-land and I've replaced a product team which had 9 devs 2 years ago with 2 devs with AI. Devs are just coping so hard around LLMs its hard to watch. OTOH the few engineers who have embraced it are excelling.
The good thing about vive coding is it avoids the software development lifecycle completely from the user perspective in a platform that has an integrated SDLC which means from defining idea to ensure visibility in changes to a runtime where the user can see it. In my mind, modifying without a hassle in a controlled environment is what users look for. Software development assisted by AI will be a thing for engineers but Vive coding is aimed for users outside of engineering. I sadly see only a handful of companies being able to pull this off.