|Type:||Seminar or Conference|
Technical debt is something that most project teams or independent developers have to deal with - we take shortcuts to push out releases, we don't focus on quality, deadlines need to be met, we inherit legacy code, or it's that quick fixes slowly become the standard. Whatever the reason, if we don't manage our technical debt (not unlike financial debt), before too long our applications are technically bankrupt, and we are forced to completely refactor and start anew. In this talk, we will discuss what technical debt is, when it is acceptable and when it isn't, and strategies for effectively managing it, both on an independent and team level. We'll talk about where it comes from, how we can pay it off, and how we can keep it from coming back.