Modern Software Engineering: Insights from David Farley on Agile, TDD, and Avoiding Bureaucracy
The article explores David Farley's decades‑long experience in software engineering, highlighting his early automation work, contributions to the Agile Manifesto, the principles of Continuous Delivery, critiques of traditional waterfall methods, and practical guidance on Test‑Driven Development and learning‑oriented development to deliver business value.
David Farley began automating C++ development with shell scripts in 1991, foreshadowing agile practices, and later helped shape the Agile Manifesto while at ThoughtWorks.
He co‑authored Continuous Delivery , winning the 2011 Jolt Award, and at LMAX built a low‑latency trading platform, applying agile principles at scale.
Farley critiques traditional waterfall development as bureaucratic, citing Conway’s Law and the high cost of change, and advocates clear goals, scientific, experience‑based methods, and the separation‑of‑concerns principle.
He promotes Test‑Driven Development (red‑green‑refactor) to keep code small, expressive, and maintainable, warning against “big mud balls” of tangled code.
Viewing software development as a learning process, he stresses incremental feedback, experimentation, and delivering business value over exhaustive documentation.
DevOps Cloud Academy
Exploring industry DevOps practices and technical expertise.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.