1729
might be a form of Jevons Paradox
(thelemmy.club)
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Of course not. It's rather easy to see how one can choose to be lazy and not do hard work while being "productive" doing easier tasks. But this isn't about the dev, it's about the culture.
Again, stop thinking I'm calling the dev lazy, you're completely missing my point.
This is the laziness. The constraints imposed by management to get new features out the door at the expense of making their existing features work better is a hallmark of the current development era.
I'm not even going to respond to the last bit because it's entirely irrelevant to (and completely misunderstands) the point I'm making.
Can you then give me your definition of "lazyness" The dictionary just gives me "the quality of being unwilling to work or use energy; idleness."
And i don't see it anywhere in this situation. They're asked to do a job a certain way (or for management, to make sure it happens in a certain way), and they do that to the best of their ability.
Could they do it better from an performance/software engineering standpoint if they had infinite time/budget? for sure. But that's not the world we live in.
Nah, I'm sick of trying to get you to understand that it's not the person I'm talking about, but the mentality of management through the whole process. I don't know if you're just not reading the words I write or what, but I'm not willing to keep repeating the same point to a wall
In a way I understand him, the culture is too one sided in its values. There isn't a balance or a good middle ground. If you appreciate irony, it's too optimised for "features". For which I generally agree. So the people upholding these values are too lazy to find the balance.
As an aside, every Dev I know would love to endlessly iterate and improve a single thing. So I understand finding that balance isn't easy either.