And the vibe coder is also blissfully unaware of all the zero days he/she has also deployed along with his prompted autocomplete output of a program.
Great work! Very efficient!
Comment on GitHub CEO delivers stark message to developers: Embrace AI or get out.
Jaded99@lemmy.world 3 weeks ago
Ah yes, the noble Caveman Coder, hunched over their keyboard like it’s a slab of stone, grunting at a missing semicolon for the past three hours. Meanwhile, the AI user already built the same app, deployed it, A/B tested it, and had time for a coffee break and existential crisis. But no worries, Caveman insists “real coders solve things manually” as they slowly reinvent the wheel… square-shaped, of course. Fire bad. IDE scary. AI tool? “Witchcraft! Burn the witch 🧹
sp3ctr4l@lemmy.dbzer0.com 3 weeks ago
sobchak@programming.dev 3 weeks ago
I’ve tried Copilot for a while and played around with Cursor for a bit. I was better and faster without Copilot due to sometimes not paying enough attention of the lines it would generate. This would cause subtle bugs that took a long time to debug. Cursor just produced unmaintainable code-bases that I had no knowledge of, and to make major changes, would be faster for me to just rewrite it from scratch. The act of typing gives me time to think more about what I’m doing or am going to do, while Copilot generations are distracting and break my thought processes. I work best with good LSP tooling and sometimes AI chatbots (mostly just for customized example snippets for libraries or frameworks I’m unfamiliar with; though that has its own problems because the LLMs knowledge is out of date a lot) that don’t directly modify my code.