MXL Consulting

Originally Published - 2/20/15 Poor process, lack of documentation, limited training and favoring convenience over security are all examples of Technical Debt at an infrastructure level. During due diligence you have Limited Time Limited Expertise Limited Information to reduce the risk of the acquisition. How can you tell if you should be concerned about the targets level of Technical Debt? Obtaining the following information (examples of poor process, limited training and co

Originally published - 2/16/15 During the discussion of DevOps, "Technical Debt" came up and is worth discussion. What is Technical Debt ? Ward Cunningham first used the term in the context of software development and is an analogy for all those things that should have been done but were not during the Development cycle. Typically these things included documentation, full QA testing and addressing "structural issues". There has been some good debate about whether Technical De