The Technical Debt Community

So you’ve got Technical debt… now what? Ward Cunningham coined the metaphor back in 1992, and it has since been taken on by the industry to describe the consequences of poor software architecture and bad coding. This website encourages a pragmatic view of technical debt, attempting to elevate the discussion from merely defining technical debt to finding approaches for business technology organizations to use technical debt awareness as a vehicle to fix fundamental problems

Recent blogs posts »

Managing Code Quality and Technical Debt

By Frances Lash • April 26, 2016

Technical debt is often given a bad name in the development process. This stems from the fact that when it becomes a topic of … read more

 

Get a Grip on your Technical Debt

By Frances Lash • April 22, 2016

In simple terms, technical debt is the work that you’ve been putting off that is needed in order to complete a job. In other … read more

 

On Technical Debt and Mergers and Acquisitions

By Frances Lash • April 21, 2016

Mergers and acquisitions can always result in some sort of unplanned issue emerging – whether it be about competition or integrating two disparate IT … read more

 

How to Avoid the Brittle Code of Technical Debt

By Frances Lash • April 18, 2016

One of the greatest issues of dealing with technical debt is the brittle code that comes along with it. Brittle code is any code … read more

 

A CFO’s Guide to Technical Debt

By Frances Lash • April 13, 2016

A CFO’s job is to form a company’s investment strategy, and one critical area of investment in any organization is technology. Now, a CFO … read more

 

How To Deal with Technical Debt in Different Environments

By Frances Lash • April 11, 2016

Most technical professionals can agree on at least one thing: that things would’ve been done better and problems would’ve been solved quicker if they … read more