You can ignore it, tie it to unrelated company initiatives, or feign ignorance and simply not offer solutions that add to it. Or… you can adopt more above-board techniques such as Crawl/Walk/Run and the Reverse Farmer’s Rule, which reframe projects so that confronting tech debt is an upfront part of the plan.

you are viewing a single comment's thread
view the rest of the comments
[–] 28 points 2 months ago (9 children)

I work for the absolute LAZIEST engineering manager I have ever known right now. Like dude has Ages of Empires open on his desktop all day at work. He is last remaining engineer from a team long ago that created the wireless technology that put us on the map. This was maybe 15 yrs ago, he was obviously the dumbest member of that team because he is secretly hiding the fact that he can no longer get the original source code to compile and he is slowly running out of ways to bullshit around it. We are now owned by a VC so upper management could not care less, but this guy creates tech debt out the wazoo! Him and the 20 yr old EE make changes to firmware, PCBs, mechanical designs CONSTANTLY and dont document any of it. it is crazy. They break production all the time. Nothing is documented, basic assembly, programming and test documentation for production is a decade old, if it even exists. They just do not give a shit, the engineering manager is already checked out, and his protege has never even seen what a good company looks like, or what engineering design control is. I feel really bad for whatever company gets suckered into buying us as that is the only concern of the VC, cut costs (primarily labor by laying a bunch of people off) as much as possible to make the company look good. Whoever buys us is going to be in for huge surprise! lolol

Technical debt is very real and can complete fuck companies.

  • source
  • hideshow 9 child comments
  • [–] 1 point 2 months ago (3 children)

    Technical debt is very real and can complete fuck companies.

    Even though the situation you described is unfortunate, I don't think it has any relationship with the concept of technical debt.

    The term "technical debt" conveys the idea that a resource is invested in a way that requires to be repaid later. The whole concept revolves around the idea that taking shortcuts doesn't eliminate the need to actually do the work to make things then right way. Rushing to a deliverable can leave a mess in your wake, but cleaning up that mess is also work that needs to be done and doesn't magically go away.

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (2 replies)
  • load more comments (7 replies)