You have pleased the people whose opinion counts. You saved time, again and again, by hacking in a new feature rather than investing the time required to maintain the integrity of your code base. As a result, your code base is more fragile. The time you saved today was actually borrowed from the future. Payment is soon due! Now what?
Steve's presentation offered some practical suggestions for identifying and dealing with technical debt, the inevitable result of customer demands and limited results. You can see his slides from the presentation here.
Steve is a Senior Extreme Programming Developer, Agile Engineer and Technical Coach. He is also a scientist, Bachelor of Science in Microbiology and Aquatic Biology, and spent some years doing research to cure Trypanosomiasis, Leishmaniasis, HIV and genetic research into cures for cancers and Cystic Fibrosis. Steve's experience in software, since the mid-90’s, covers a wide range of fields. A few include banking, consulting, education, gaming, healthcare and shipping/inventory. A majority of those years was consulting, working with all sorts of code, most of it heavily burdened with technical debt accrued from past hard and difficult choices. Addressing technical debt helped developers, teams and organizations cope with and improve their software. Proactively addressing Technical Debt has been a focus of Steve's, while imbuing developers, teams and organizations to become more Agile in his classroom