The art of technical debt management

New product life cycle

New product life cycle

MVP development

Product market fit


Let's agree on the goal

What matters at the end of the day?

Why technical debt is critical to manage?

Your customers are the reason your job exists

The two types of technical debt

TB Type I

  • No SW/Ad hock architecture, A lot of functional code pieces.
  • No using testing, Weak QA.
  • No CI/CD or automation.
  • No environment setups, install recipes.
  • No docs or manuals (or unupdated ones).
  • Fragile/spaghetti code.
  • Wet code
  • And more…
  • Selecting the wrong chip for a product.
  • Using the wrong communication protocol/method.
  • Selecting bad framework, not a suitable coding language.
  • Using dead (non maintained) open source.
  • Using unstable technologies to build on top of.
  • And more…

The “right” balance

There is no transition day




Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Will canary replace conventional testing?

How to Setup a new WordPress Project with Docker

Monitoring Disk I/O on Linux with the Node Exporter

How cloud computing is changing project management

Moving Cloud Foundry Applications to Kubernetes

Building a Serverless Dataset and AI Model Management Tool

Forget About Agile vs. Waterfall, It’s About Silo Busting

Why Kubernetes Is Awesome: A Beginner’s Guide.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Eran Shlomo

Eran Shlomo

More from Medium

Building a software development team full of Juniors or Seniors just won’t work!

Aphorisms for Software Engineering Management

About our negativity as software developers

When Should Companies Let a Software Project Fail?

An upset woman with a computer in the background.