# How to Avoid Brittle Code

<https://www.go.cd/2016/03/24/how-to-avoid-brittle-code.html>

- Host: [go.cd](https://links.thingelstad.xyz/hosts/go.cd/)
- Saved: March 30, 2016 (2016-03-30T11:19:03Z)
- Record: https://links.thingelstad.xyz/links/c220509d6913/
- JSON: https://links.thingelstad.xyz/links/c220509d6913.json

## From the page (probably an excerpt, not Jamie's words)

The most common problem with legacy code is brittleness. A brittle codebase is one that a team cannot change without great pain. In ThoughtWorks’ 10 years of building products we’ve learned some hard lessons while trying to keep fairly large codebases malleable, year after year. In this post I'll share what we learned from our biggest challenges.

## Facts

- Kind: [Page](https://links.thingelstad.xyz/kinds/page/)

## Saved the same week

- [The Dropcam Team](https://links.thingelstad.xyz/links/f9a56c0a1954/) (medium.com, March 29, 2016)
- [Esquire loses a man at his best](https://links.thingelstad.xyz/links/d981b046d4f7/) (cjr.org, March 30, 2016)
- [Davos 2016 - An Insight, An Idea with Kevin Spacey - YouTube](https://links.thingelstad.xyz/links/23cda480119b/) (youtube.com, March 30, 2016)
- [Day One and the Apple Watch](https://links.thingelstad.xyz/links/13b1d04cb0db/) (myproductivemac.com, March 30, 2016)
- [Our Guide to Iced and Cold Brew Coffees — Tools and Toys](https://links.thingelstad.xyz/links/c63712fe9fd4/) (toolsandtoys.net, March 31, 2016)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/https://www.go.cd/2016/03/24/how-to-avoid-brittle-code.html