I am an author, speaker, and loud-mouth on the design of enterprise software. I work for ThoughtWorks, a software delivery and consulting company. This site contains lots of my writing on software development, which primarily focuses on software design and agile methods. To find your way around this site, go to the intro guide.
News and Updates
My atom feed (RSS) announces any updates to this site, as well as various news about my activities and other things I think you may be interested in. I also make regular announcements via my twitter feed, which I copy to my facebook page.
Mon 08 Feb 2016 14:55 GMT
Sun 07 Feb 2016 21:43 GMT
Fri 05 Feb 2016 14:48 GMT
Wed 03 Feb 2016 15:01 GMT
In the second part of their evolving article, Cade and Daniel describe the danger of sending malformed data to the browser, including techniques that avoid turning a Supreme Court justice into an attack vector.
Tue 02 Feb 2016 12:50 GMT
Thu 28 Jan 2016 20:35 GMT
Feature Toggles seem to beget rather messy Toggle Point code, and these Toggle Points also have a tendency to proliferate throughout a codebase. It's important to keep this tendency in check for any Feature Toggles in your codebase, and critically important if the toggle will be long-lived. In this installment, Pete covers a few implementation patterns and practices which help to reduce this issue.
Thu 28 Jan 2016 15:20 GMT
Modern web development has many challenges. Of course, you need to write code that fulfills customer functional requirements. It needs to be fast. Further you are expected to write this code to be comprehensible and extensible.
Somewhere, way down at the bottom of the list of requirements, behind, fast, cheap, and flexible is “secure”. That is, until something goes wrong, until the system you build is compromised, then suddenly security is, and always was, the most important thing.
Specialized techniques, such as threat analysis, are increasingly recognized as essential to any serious development. But Cade Cairns and Daniel Somerfield explore how security can be significantly enhanced with some basic practices which every developer can and should be doing as a matter of course.
Wed 27 Jan 2016 16:27 GMT
Fri 22 Jan 2016 13:55 GMT
Thu 21 Jan 2016 15:22 GMT
Tue 19 Jan 2016 15:13 GMT
Feature toggles are a powerful technique, but like most powerful techniques there is much to learn in order to use them well. And like so much in the software world, there's precious little documentation on how to work with them. This frustrated my colleague Pete Hodgson, and he decided to scratch that itch. The result is an article that I think will become the definitive article on feature toggles.
We're going to release this article in installments over the next few weeks. The first installment sketches out an overview story of how a team uses feature toggles in a project, and introduces various terms that explain how these toggles work: toggle points, toggle router, toggle context, and toggle configuration.
Continuous Integration and Delivery
For a long time I’ve been a champion of Continuous Integration which reduces integration risk by integrating early and often, an application of the principle of Frequency Reduces Difficulty. We’ve found CI to be a core technique at ThoughtWorks and use it almost all the time. At the heart of this is a style of development that minimizes long feature branches with techniques like Branch By Abstraction and Feature Toggles.
While this is useful, there was still risk present from software that works in the development environment to getting it to work in production. As a result we developed Deployment Pipelines to reduce this risk, moving closer to our aim of Continuous Delivery: building software in such a way that we confidently deploy the latest builds into production whenever there is a business need. We find this improves feedback, reduces risk, and increases the visibility of project progress.
For more information: take a look at my guide page on Continuous Delivery.
I’ve been involved in enterprise software for two decades and while we’ve seen huge technological change during that time, the relational database has been a constant figure. Previous attempts to dethrone relational databases have failed, but some people think the new rise of NoSQL databases will finally consign relational databases to history. While I think relational databases are going to be an important part of the landscape for a long time, I do think that there is a big change coming in the database field.
I discovered ThoughtWorks in 2000: then a small American company whose philosphy of software development was remarkably similar to my own. Now we’ve grown to around 2500 people world-wide, but kept the values that make us special. My colleagues have built critical systems for many clients in that time, and I’ve learned many lessons from them. While doing this, we found we often didn’t have the tools we needed, so we started to build them. This led to open-source tools such as CruiseControl, Selenium, Frank, and Moco as well as commercial products.
I have many opportunities, but I’ve stayed at ThoughtWorks because of the quality of my colleagues, who include both well-known speakers and those who may not be famous names but do an excellent job of software delivery (and feed me the information to write about). We are inspired by working with each other and our unusual three-pillar philosophy that raises professional excellence and social justice to the same level as financial performance.
And we are always looking for more great people to join our curious company. Maybe I’ll see you in one of our offices some day.