DEV Community

Discussion on: What's your worst technical debt story?

Collapse
 
buinauskas profile image
Evaldas Buinauskas • Edited

tl;dr; People don't know to.

Proper version:

I'd say that root cause is the way teams have been structured.

Physically, our department is just database department and we're supposed to deal with SQL. We're all co-located.

We've also got web development teams in other physical locations.

Now the issue is that SQL team doesn't know much about web codebase and technologies that product has been built with but knows business domain very well and underlying data structures (or at least is supposed to know).

Web team knows codebase but knows very little of SQL and domain logic.

And when you have to remove some dead code, it's quite a painful process because scrum teams are busy with sprint work and debt stories usually are somewhere at the bottom and are left behind due to higher priority work.

Of course, this does sound bad, but some of our managers (not every) are technical people and see value in technical debt removal. This moves on, but slowly.

Also, teams are now becoming more collaborative and try to enrich their skill set which will (not I shape people, T shape, E shape, all these buzzwords) which will help out to understand not just the one side of code, but the whole picture.