(Addressed to myself. I look forward to eating crow over all or most of this.) To use LLMs effectively as a programmer, You still need to know what to tell them1. Be explicit. Especially with success/failure conditions. Especially when laying out a brand new project or module. You need to check all the work. “Trust But Verify.” Did you solve the right problem? Are your tests testing the right thing? Are the docstrings and comments actually helpful (and correct)? Is the generated code maintainable, modular, readable? Are you confident you’ll be able to integrate features and bugfixes after you stepped away for six months? Vibe Coding is bullshit for anything other than proofs of concept. And atrophies your skills and your passion (that last part makes you a human being and not the thing they want to replace you with.) If you’re not a programmer, go wild. Citizen coding ftw. And if your app blows up, thank you for ensuring our job security. With all three, Wisdom and Experience will…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.