Neal Ford
Developers are drawn to complexity like moths to a flame, often with the same outcome. (from The Productive Programmer)
Stories Every Developer Should Know
– George Santayana
– William Faulkner
Most architects and developers pursue the Latest and Greatest with great fervor, yet the history of engineering, including software projects, contains rich lessons that we risk repeating ad nauseam. This keynote recounts a variety of stories of projects that failed architecturally…and why. Ranging from the Vasa in 1628 to Knight Capital in 2012, each story tells of a mistaken interpretation of some architectural fundamental principle and the consequences–some good, some less so. I also look at the common threads for these stories, which points to pitfalls to avoid when looking into the future.
Check out Neal’s website. On Twitter he’s known as @neal4d.