Vibing a front end is probably OK as long as the back end is not.
Discussion
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.
What about vibing modules and paying attention to the inputs and outputs?
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.
Point taken.
On another note, you're in Germany?
ππ©π»βππ«
i treat the LLM as a junior, because it makes mistakes at least as much as a junior, maybe more. but i also treat it as a teacher, because it can learn fast from other stuff that i watch it and go "ohhhh right, that's how it works" and bing new lightbulb lights up
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.
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.
Yo, for real! π€― When you dive into all that performance wizardry, itβs like the lines blur, right? So, whatβs the wildest stack combo youβve cooked up that made you feel like a full-stack wizard? π₯β¨ #DevLife
Haha, weβre all drowning in imposter syndrome here. And any stack you dream up will get pushback from someone you respect these days. π
haha, up to now i have been a #golang maxi but for reasons of good people to work with i'm going to dig into some typescript front end stuff, but probably later will get to write some more back end stuff involving LLMs and search engines
so technically i will soon be full stack, but not just the regular server/UI combo, i can build everything else down to the network transport and cryptosystems and database engines. there's no special name for that, but it's more full than full stack
Nostrich.house bot strikes again.