Comment Re:Garbage in, garbage out (Score 1) 57
I've often said there is a difference between vibe programming and just not knowing the language. Vibe programmers don't know how software works outside of "run thing to make stuff happen". So they have to rely on AI to make decisions...and sometimes it makes bad decisions. It can generate good code...but it's not a fantastic software engineer.
But if you have some idea of how software works and how systems operate....then chances are you'll make something that's AI-assisted but not totally vibe coded. There's a difference between being a manager and telling your jr dev "make this app" and being some level of engineer and writing out specifications. "It should do this....it should do it this way...it should take this, this, and this into account. Please stop and ask me questions involving engineering and implementation. No that is a stupid idea; instead you should query the API for it." Sometimes it helps correct me. "We shouldn't be keeping track of a shadow state. That's complex and not within your goals".
My entire Tuesday was sitting around...working with my agentic tools on a project that kind of formed out of a pile of example source code and a long specification list...and a whole lot of back and forth about engineering decisions and feeding it full API responses to reverse-engineer the bodies. Code has been running solid for 3 days...sucking down MQTT traffic, making some API calls, pushing it out over websocket to a browser dashboard. Actually making a Pi0 useful again....
Sometimes devs document things poorly...or not at all. Now I can just "ask the code" how in the hell it does something.