In this final installment of my article on refactoring loops to collection pipelines, I tackle a loop that's performing two different validations on the identifiers for a person.
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.
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.
Tue 14 Jul 2015 09:06 EDT
Sat 11 Jul 2015 15:34 EDT
Thu 09 Jul 2015 09:22 EDT
Agile software development has broken down some of the silos between requirements analysis, testing and development. Deployment, operations and maintenance are other activities which have suffered a similar separation from the rest of the software development process. The DevOps movement is aimed at removing these silos and encouraging collaboration between development and operations.
Wed 08 Jul 2015 09:42 EDT
I've put together a resource guide for microservices: a page that selects and organizes information about microservices. I don't intend it to be a comprehensive listing, but rather my selection of articles, videos, and podcasts that provides the best compilation of material on the topic. The links cover what they are, when to use them, how to build them, and who has used them. If you're looking for more information on these topics, this should give you a solid starting point.
Tue 07 Jul 2015 10:00 EDT
In this fourth installment, I refactor a loop that summarizes flight delay data by airport.
Wed 01 Jul 2015 09:36 EDT
Many development teams have found the microservices architectural style to be a superior approach to a monolithic architecture. But other teams have found them to be a productivity-sapping burden. Like any architectural style, microservices bring costs and benefits. To make a sensible choice you have to understand these and apply them to your specific context.
Tue 30 Jun 2015 09:50 EDT
In this third installment, I show an example of making sense of a loop that marks preferred offerings from a list.
Thu 25 Jun 2015 10:00 EDT
In this second installment, I show an example of refactoring a simple nested loop.
Tue 23 Jun 2015 10:31 EDT
I've long been a fan of the programming pattern that I call the collection pipeline. This allows me to write computation on collections in the form of a pipeline of familiar operations (eg filter, map, reduce). More and more language environments now have the language features and collection APIs to support pipelines, but since they have been limited in use for so long, more people are familiar with loops. In this article (which I'm releasing in installments) I'll take some loops and show how I'd refactor them into collection pipelines.
Sun 21 Jun 2015 13:05 EDT
Fri 19 Jun 2015 11:17 EDT
Recently I got chatting with a friend who was toying with trying out the TV series "Doctor Who", but was put off by its long history and sheer amount of episodes. So I decided to make another pass at article that helps people cherry pick some of the best episodes. With this you can enjoy many of the best bits of Doctor Who without feeling you need to see every episode.
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 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.