Need to discuss tech debt

[ghost]

How to identify it, how to address it, when to accept it.

[miketheman]

I suspect this may have something to do with this topic: http://www.opsschool.org/en/latest/soft_skills_201.html#business-acumen-in-operations

I do consider Tech Debt as a business-oriented consideration - would be curious to know if others think otherwise.

[edunham]

It seems like the soft skills 201 section is more about leadership and management, whereas being able to identify and report areas of technical debt to one's manager is a skill that even the lowest tier ops people with no aspirations to leadership need to have.

Introduction to tech debt might belong in http://www.opsschool.org/en/latest/soft_skills_101.html#the-importance-of-documentation , since it often goes hand in hand with, and is exacerbated by, bad docs.

Somewhat unrelatedly, https://github.com/tomheon/git_by_a_bus is a neat way of trying to quantify potential sources of technical debt in a codebase.

[simskij]

My opinion is that it would fit just as good under http://www.opsschool.org/en/latest/bcp.html as tech debt is the number one reason to business continuity failures.