Post

"I will not touch anything with ai-generated code" is going to mean, in pretty short order, "I will not touch software" this is just functionally what software development is now and it's only going to accelerate from here

ceej@ceej.online

I think it’s important for anyone who (completely understandably) checked out on AI the second the crypto/nft/metaverse/snake oil chuds started pushing it to realize that, in at least the domain of software development, we are very much living in a scenario where the snake oil actually works

there's an enormous amount of poorly vibe-coded slop out there and unfortunately that is also going to accelerate but minus some individual passion projects almost nothing is written entirely by hand these days

yeah, I think this is a good place to draw the line - replacing human artists with the machine is bad but the ship has one hundred percent sailed on the code side

gubbbo.bsky.social@gubbbo.bsky.social

I guess I can't avoid the code. But I can certainly choose to avoid paying money for image gen assets, voice, images etc.

another piece of this for gaming specifically is that games are full of weird-ass corner cases and these tools have gotten shockingly better at diagnosing those - I work in a large (non-gaming) codebase and recently I have been able to hand it a bug report and say "diagnose and fix this" and it will

because is/ought posting is in fine form on bluesky today, a pop quiz: as someone who works in software and had what seemed to be ironclad job security only a couple of years ago, do you think I want anything in this thread to be true

You might have too narrow a view of software. For example, AI remains pretty useless for firmware. There is also more conventional work, but which involves super sensitive IP. But, in general, yes, steaming piles of vibe is becoming normal. But since models collapse when recursively trained… 🤷‍♂️

I just made an LLM create a browser-based virtual machine for an entirely undocumented arm5 device firmware for about US$4. My takeaway from the experience was that going the other direction and creating firmware from a fully documented hardware configuration is imminent—if not already possible.

0 reposts3 likes

Not sure this makes sense. If there isn’t a code base for the device, how did an LLM correctly use the peripherals? The chip makers put out SDKs, but their peripheral libraries are always too buggy for commercial use. Also, how would you validate the virtual machine with no existing test bed?🤷‍♂️

I see post docs learn otherwise everyday when they try to Claude their way with, say, an NXP processor, but your mileage may vary. Claude still gets confused with ST32 clock limitations (you have to manage your clocks carefully to have CAN and USB at target rates) and lots of sample code.🤷‍♂️