The Underlying Issue Behind My Inaction on Technical Debt

My reluctance to tackle technical debt is somewhat disappointing. The primary reason is the administrative burden that comes with it, along with the manner in which I'm expected to manage it.

Let’s break it down:

We have a designated 20% of our time to focus on resolving debt, yet it feels like the entire organization expects us to address these issues, which can hinder our overall progress. Within our team, this has translated into a requirement to label tickets as either technical debt or technical enablers, ostensibly for reporting purposes.

We all have a shared disdain for “the business,” don’t we?

While I don’t necessarily oppose tracking work in this way—since I believe the organization is genuinely trying to foster positive change—what I do take issue with is being called out during a stand-up meeting after I’ve complied with the latest directive.

I was confronted rather aggressively about whether I had marked a ticket as technical debt. I had indeed done so, yet I was then subjected to an explanation of why it required updating, right in the middle of my status update.

Sure, I’ll make sure to verify this in the future.

This is subtly my way of expressing my frustration with the individual in question. I’ve already fulfilled your request. Why the need for further guidance?

It seems like a tactic to assert authority within the organization.

The Impact

It’s a minor issue, and I feel embarrassed about it. Yet, I seem unable to escape this cycle.

So what does this mean?

Consider the possibility that this attitude is mirrored across different teams within my company. A group of disgruntled and unmotivated developers.

I must be honest; this is the environment I’m currently navigating.

What a disheartening situation. It truly makes me want to cry.

About The Author

Professional Software Developer “The Secret Developer” can be found on Twitter @TheSDeveloper and regularly publishes articles through Medium.com.