Problem Creep: Technical Debt Difference

Previously, I wrote about slowly fixing when solving the local development on-boarding is a problem.

In essence, when there is a problem that affects the technical side of software development, such as difficult local development on-boarding, the right solution is to always fix it slowly.

As a technical leader, the business or project side should never prioritize technical issues. Why?

That’s your job!

Take time and fix it - I wrote about that here and learned that from Sandi Metz’s NYC.rb POODR panel.

What makes the local development on-boarding different than other technical debt? The creepiness? The scope?

Probably because this is a pure technical situation - no business requirements or deadlines set against it.

Only the technical team decided.

This change in audience also make solving the problem harder than other pieces of technical debt.

Another way to think of it: problems with the local development on-boarding process is: purely technical, debt.

That’s a real test of a technical leader.

Next, I talk about breathing and solving the problem.