4 ms·

> Non technical folks under-appreciate the cost and frequency of long-term technical debt. Undoubtedly this is true, but there's an implication here in this c

> Non technical folks under-appreciate the cost and frequency of long-term technical debt. Undoubtedly this is true, but there's an implication here in this context that somehow on shore, or more well paid developers don't create such technical debt, when in fact they do. It amazes me that I see team after team of competent well intentioned developers create one ball of mud after another. It's striking really.

RealityVoid 6y ago
> It amazes me that I see team after team of competent well intentioned developers create one ball of mud after another. It's striking really. It is! But I don't understand... how? How does that happen? You should put good people together and get something good. But it is not always so. Very puzzling to me.
- krasicki 6y ago
  Oh, look, the answer is easy. Manage these projects with SAFE. SAFE is a corporate friendly Agile methodology that essentially says, "Fuck that agile stuff. Use the Agile vernacular to keep being as unproductive as you always were." This is like heroin to these corporations. They use Jira and Rally to create a cult of numerology games that reduce tasks to filling time-boxed, random things- to-do. Be sure the Agile coach is drilled in the game and clueless about "technical-things". Add an equally clueless Product Owner whose background is Word and Excel and you'll create the best Big Ball 'O Mud anybody ever wished for. And if you're running late, add a dozen or so new inexpensive -cough- "developers" from your favorite outsourcing firm.
Dansvidania 6y ago
I think software development misses a "doctrine". It is very hard to develop robust maintainable software while trying to chase the latest fad (edit: under constant pressure to deliver new functionality). I have known this as a junior, never really getting to know a technology before hopping to the next one, and I am still having to deal with this now that I have a bit more experience, trying to convince my colleagues not to be so quick to dismiss the modern for the newer. Sometimes I feel like I do not know what we are doing although being one of the senior members of the team. Stuff quickly snowballs into mud... It's like there is not enough effort or time to deliver functionality while also staving off entropy

RealityVoid 6y ago

> It amazes me that I see team after team of competent well intentioned developers create one ball of mud after another. It's striking really. It is! But I don't understand... how? How does that happen? You should put good people together and get something good. But it is not always so. Very puzzling to me.

krasicki 6y ago
Oh, look, the answer is easy. Manage these projects with SAFE. SAFE is a corporate friendly Agile methodology that essentially says, "Fuck that agile stuff. Use the Agile vernacular to keep being as unproductive as you always were." This is like heroin to these corporations. They use Jira and Rally to create a cult of numerology games that reduce tasks to filling time-boxed, random things- to-do. Be sure the Agile coach is drilled in the game and clueless about "technical-things". Add an equally clueless Product Owner whose background is Word and Excel and you'll create the best Big Ball 'O Mud anybody ever wished for. And if you're running late, add a dozen or so new inexpensive -cough- "developers" from your favorite outsourcing firm.

Dansvidania 6y ago

I think software development misses a "doctrine". It is very hard to develop robust maintainable software while trying to chase the latest fad (edit: under constant pressure to deliver new functionality). I have known this as a junior, never really getting to know a technology before hopping to the next one, and I am still having to deal with this now that I have a bit more experience, trying to convince my colleagues not to be so quick to dismiss the modern for the newer. Sometimes I feel like I do not know what we are doing although being one of the senior members of the team. Stuff quickly snowballs into mud... It's like there is not enough effort or time to deliver functionality while also staving off entropy