hey i'm adam. i'm a software engineer who's way too into backend, distributed systems, and hunting down edge cases for fun. also i play piano by ear and math's kinda fun
right??? I saw a guy who posted something about how AI refactored his entire codebase, rewrites features...etc and finally nothing worked and my question to him is: " what was your prompt? let me see your prompt, mate "
Distributed backend specialist. Perfectly happy playing second fiddle—it means I get to chase fun ideas, dodge meetings, and break things no one told me to touch, all without anyone questioning it. 😇
My approach here is to use one of the more “simple” models like Haiku, and really be the human in the loop. Sure it’s not “pls fix”, but you’re getting a good understanding of what’s going on, and you can spot a breaking change before it spits out 10k LOC.
But this isn’t something a new vibe coder would do, at least not yet.
Distributed backend specialist. Perfectly happy playing second fiddle—it means I get to chase fun ideas, dodge meetings, and break things no one told me to touch, all without anyone questioning it. 😇
This is true if you've able to take the time to walk the LLM through the solution. The way I see things though, speed to delivery will be expected to increase naturally as the cost of LLM use continues to rise. That's a whole other exponential problem, but even Sonnet has trouble delivering accurately without granular details.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
right??? I saw a guy who posted something about how AI refactored his entire codebase, rewrites features...etc and finally nothing worked and my question to him is: " what was your prompt? let me see your prompt, mate "
the prompt? " please refactor this "
that's it.
And I'm positive that "refactoring" was exactly what was accomplished in the end, too. 🤣
Classic. Make no mistakes.
My approach here is to use one of the more “simple” models like Haiku, and really be the human in the loop. Sure it’s not “pls fix”, but you’re getting a good understanding of what’s going on, and you can spot a breaking change before it spits out 10k LOC.
But this isn’t something a new vibe coder would do, at least not yet.
This is true if you've able to take the time to walk the LLM through the solution. The way I see things though, speed to delivery will be expected to increase naturally as the cost of LLM use continues to rise. That's a whole other exponential problem, but even Sonnet has trouble delivering accurately without granular details.