Join the Technical Debt bloggers in discussions about their personal experiences in agile development best practices and adopting agile ideas in complex business systems. If you are interested in blogging for us, let us know!
By Frances Lash | May 11, 2015
Technical debt is defined, in this post, as any code that impedes agility as a project matures. This is an important definition to keep in mind as the following attitude towards technical debt is discussed.
One of the reasons that so many start ups fail is because they take too long to get their product to market, and ... read more
By Frances Lash | May 8, 2015
It is commonly mentioned, when speaking on technical debt, that small amounts of debt incurred, if they are deliberate and well monitored, can be useful to any development team. However, it is always best to avoid technical debt as it can be easily forgotten about and has negative consequences as a byproduct of its presence ... read more
By Frances Lash | May 7, 2015
Technical debt can bog down any organization that attempts to be agile. If too much of the IT budget is spent on maintenance and not on innovation and development, productivity will decline sharply. The example used in this post is Telefonica in Spain; the company freed around 14 billion Euros and 18% of the total ... read more
By Frances Lash | April 2, 2015
This post seeks to respond to a question on how to restructure a poorly formulated monolith, and whether reformulating it into another poorly formulated set of microservices is ever the correct answer. This question is used to highlight the idea that a team which is incapable of creating a well structured monolith probably won’t be ... read more
By Frances Lash | March 25, 2015
This post beings with an interesting statement: that in a start up environment technical debt often feels inevitable. Technical debt can be seen as a function of moving fast, minimum variable products (MVP), prototypes, agile practices, and of releasing the product to market as soon as possible.
The idea of using a minimum variable product to ... read more
By Frances Lash | February 23, 2015
In this post, technical debt management is looked at from a DevOps approach. Technical debt is defined here, as the price organizations pay when releasing poorly designed code. Companies that collect a large amount of technical debt are in risk of running into a situation where any innovation takes a backseat to putting out fires. ... read more
By Frances Lash | February 2, 2015
Is technical debt still a valid metaphor in the present global software development world? The answer is yes, and this post goes on to present the benefits of such a metaphor while explaining just what technical debt is exactly. There is a growing concern on tech debt not simply because of the costs associated with ... read more
By Frances Lash | January 5, 2015
This post discusses the three categories of code that can be found within a certain project and that confusion about them plus a misunderstanding about their actual cost can lead to trouble. The three categories of code follow:
Temporary Code: or code written to throw away within a day or week – if it breaks it’s ... read more
By Frances Lash | December 30, 2014
The on going management of technical debt has become viewed as critical for the development of high quality and maintainable software, even by those who promote agile development processes. This consideration for tech debt management has contradicted the notion that development decisions should almost exclusively be driven by business value because of the difficulty of ... read more
By Frances Lash | November 12, 2014
Technical debt, as a term, serves to incentivize change within app and portfolio management. However, it fails to translate with business leaders, therefore failing to push through with the change it seeks to promote. In this post, Phil Murphy expands on his love/hate relationship with the term; lauding the “sentiment for change” it inspires, but ... read more