Vibe Debugging: Enterprises' Up and Coming Nightmare
marketsaintefficient.substack.com
Vibe Debugging: Enterprises' Up and Coming Nightmare
1–10 of 69 posts
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#2> To fix this bug, I need to understand the code.
Almost every day on this site for the past few months has been an instance of Mugatu's "I feel like I'm taking crazy pills!" moment.
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#3Wasn’t the point of vibe coding to write throwaway code you will never maintain or care about?
Why do people think it means we can write enterprise applications without understanding the code/specifications?
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#4> 81% of developers agreed that AI increases their productivity
I've had a few AI generated PRs come my way and the code-review process is, shall we say, not fun. It takes me a lot more time to review these PRs, there is way more back-and-forth between me and the 'developer', and it takes much more time to get the PR merged. That's not saying anything about the increased difficulty in modifying this code in the future.
I have a feeling these claims of being more productive don't account for the entire development cycle.
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#5Self-inflicted nightmare.
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#6> 81% of developers agreed that AI increases their productivity I've had a few AI generated PRs come my way and the code-review process is, shall we say, not fun. It takes me a lot more time to review these PRs, there is way more back-and-forth between me and the 'developer', and it takes much more time to get the PR merged. That's not saying anything about the increased difficulty in modifying this code in the futur…
The recent RCT on open source ai bug fixing had most participants feeling like they were more productive but actually being less productive. It may just be perception error, and then the issue you identify makes it even worse.
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#7> 81% of developers agreed that AI increases their productivity I've had a few AI generated PRs come my way and the code-review process is, shall we say, not fun. It takes me a lot more time to review these PRs, there is way more back-and-forth between me and the 'developer', and it takes much more time to get the PR merged. That's not saying anything about the increased difficulty in modifying this code in the futur…
I think employees (myself included) often think, "I'm more productive" when in reality what they are actually experiencing is, "My job is now easier."
Easy does not necessarily mean more productive when you're trading ease for something else. In the case of coding, you're trading ease for things like understanding and maintainability.
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#8I have a basic rule: understand and agree with every line of code in a PR I’m responsible for generating (manually or via agent). This simple act prevents 99% of AI-related bullshit code.
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#9> I suspect best practices for "vibe coding" will end up like test-driven development: a proven method for writing better software that many engineers still choose to skip.
I’d like to see the proof for TDD; last I heard it slowed development with only minor reliability improvements.
Re: Vibe Debugging: Enterprises' Up and Coming Nightmare
#10> I suspect best practices for "vibe coding" will end up like test-driven development: a proven method for writing better software that many engineers still choose to skip. I’d like to see the proof for TDD; last I heard it slowed development with only minor reliability improvements.
I see TDD exactly as the best practice for vibe coding! Context is stored as test coverage, to make sure they don't break things when they hallucinate.
YMMV though.