Silberengel @Laeserin - 20d
AI-assisted coding burns me out, much faster than normal coding. The expectation is that anything, regardless of novelty or complexity, has to be vibe-coded in 3 minutes. Things are constantly whizzing across the screen, which is mentally exhausting to focus on, and there's all of this busyness, but now it takes me an hour to realign some card components. It used to take me an hour, but it still does. You won't have to fire developers, in the end. They're gonna quit. This is a really crappy job, now.
This is always the plan. LOL
Everything is fun until about 10k-20k lines of code. The problem is that those lines are a grey box. You can see the code, but you can't navigate around in it. You are stuck stumbling around, trying to figure out how it works, so that you can take it from there. The temptation to just throw it in the garbage and start over, by hand, is high.
As soon as you pay attention, you're reduced to screaming at the screen to SLOW DOWN, SO I CAN READ THE CODE. But then you lose the speed factor. You're still glad you did it, as the code invariably has some WHAT THE ACTUAL FUCK? bits in it, but it's arguably slower than just writing it yourself. And you immediately start forgetting how to write it yourself. Your brain quickly removes those faculties because they are expensive and have fallen in disuse. Literally draw a blank, when you want to print a line to the console. Also, just... You can't even imagine the sheer tedium of auditing someone else's code, full-time. Just reading generated code, all day, every day.
🌍👩🏻🚀🔫
It just occured to me that boring-out and de-skilling every dev with a clue makes it much easier to roll out intentionally-bad code. Nobody will ever read the code, again, so you can put whatever you want in it. Tests might be able to find that, but they're vibe-coding the tests, as well. Sort of the way that the quality of bread completely collapsed, once it was being made by machines in big factories, as the people standing around the machines were no longer bakers. Nobody in the bread factory knew how to bake bread.
Align it with a #PurpleKonnektiv meetup and meet the whole crew.
d475c - 19d
Well. If you don’t insist and don’t know what fronted does in the background to produce responsive pages, it will derail quickly. There will be miles of consecutive fixes for self-inflicted problems, when all that was needed was to adjust a too-tight constraint on some element that broke the flow. All pages are responsive until you add CSS. LLM wants to force it.
Silberengel @Laeserin - 19d
Yeah, it was rotating through fixes for half an hour, last night, and then I was like, Hmm, maybe the outer container is too narrow. 🤔 *Change 5 characters. Problem fixed. Push commit. Go to bed.* Someone else's AI had broken the responsiveness of the outer container, in a previous PR. The AI tech debt just goes 📈
Once you start doing SSR and BFF and active relay management and advanced caching and native storage and other performance magic ✨, then the frontend/backend divide sort of melts and everything is full stack.
The entire code base quickly degrades to the AI saying "Trust me, bro.*
Haha, we’re all drowning in imposter syndrome here. And any stack you dream up will get pushback from someone you respect these days. 🙈
Nostrich.house bot strikes again.
You can usually cut the code it writes down by at least a ⅓.
I'm starting to hate using Cursor. Ollama Codestral is more my style, especially as I can run it locally and query it in the browser, and don't sit, there, terrified, frantically smashing the STOP button.
Yeah, they all do weird stuff. Buggy. The vibe-coding AI has also been vibe-coded by the same AI, so...
Yeah, I just use VS Code and my favorite plugins and codestral, at work, and it's stress-free AI. As soon as the AI is running in the IDE, it gets nuts, fast.
