3 ms·
“yet I don't have to know or care about implementation details” Implementation details can very much matter though. I see this attitude from my managers that n
by switchbak 7mo ago
“yet I don't have to know or care about implementation details”
Implementation details can very much matter though. I see this attitude from my managers that now submit huge PRs, and it is becoming a big problem.
I definitely agree that these tools allow one with an in-depth developer background to cover territory that was too much work previously. But plop me into a Haskell codebase, and I guarantee I’d cause all kinds of problems even with the best intentions and newest models. But the ramp up for learning these things has collapsed dramatically, and that’s very cool.
I still don’t want to have to learn all the pitfalls of those frameworks though. Hopefully we will converge on a smaller number, even if it’s on tooling that isn’t my favourite.
- waffletower 7mo agoMerges can become more fraught with multiple engineers vibe coding on the same codebase. However, LLMs will become delegates for that too.
- switchbak 7mo agoConflicts are the least of our worries, and yes llms can handle that well. I’m taking about the things you can’t easily handle, the complexity that slowly overwhelms a codebase with no easy way out except a rewrite. And a rewrite of a non-trivial application, even with the AI goodness, is still a big proposition and full of all kinds of risk. If you have a trivial application, you probably don’t have much protecting you from someone else vibing up a competing replacement either.