• Home
  • /
  • Learn
  • /
  • Technical Debt (TD) – what is it and when does a little become too much?

Technical Debt (TD) – what is it and when does a little become too much?

Datapreneur Khyanafi
pbinsightz post page

Prakash Baskar

October 19, 2020

minutes remaining


I got introduced to this term about a year ago. Initially, to me, this seemed like a few other terms we are used to – backlog, put-it-in-the-back-burner, parking-lot item, etc.

But I was wrong.

While the others are more for features, functionality or activities, TD is a ‘quick-hit’ super-tactical technology/design/architecture/coding-related compromise that is taken.

And invariably, in a lot of cases, this happens because of somebody with limited exposure to the technical details committing milestone deadlines and delivery dates to somebody else – within the organization, to the customer, the board or the market/investors.

TD, without a plan to fix or mitigate, becomes corrosion, infected wound or a stage-III/IV cancer.

When is a time when you have never had anything to work on in data/analytics area? So when do you think you will be able to fix all the technical debts that were taken?

Please stop killing your company from within. Don’t commit dates without consulting your technology leads and don’t take too much of technical debt that you sink the program, your team or company.


Share

Tags

Data Architecture, Data Strategy


You may also like

Become an Insider

Want Unconventional Ideas and Insights Directly Delivered to You? 

Insiders get periodic mini-coaching and personalized follow-up that is not available otherwise.

Take Your Career To New Levels .