“The problem isn’t just laziness. It’s degradation. Engineers stop exploring. Stop improving. Stop caring. One more layer of abstraction. One more lazy fetch call inside a render loop. Eventually, you’re living in a cathedral of technical debt, and every user pays.”
This quote has the no one wants to work anymore vibe.
We all predicted this when web frameworks and object relation mappers were introduced… And we were right… Kind of. The average programmer is certainly worse - but there’s also many more of us, getting a lot more done. And there’s still plenty of us who master the craft.
I hear that. I don’t judge anyone using copilot to cover the gap between perfect and good enough. I use it that way, as well.
A coder passionately loving Copilot strikes me as a bit like a sailor passionately loving life boats.
It’s perfectly rational, and… it implies that they routinely deal with some shit that probably, ideally, ought to get fixed.
I’m projecting my own experience a lot here. When I’m working with code I’m really happy with, I find copilot getting in my way more than helping. When I’m working with code that’s newer and messier, I find copilot pretty handy.