Subscribe: Evan Bottcher » ThoughtWorks
Preview: Evan Bottcher » ThoughtWorks

ThoughtWorks – Evan Bottcher

// TODO: think of a witty and intelligent tagline

Last Build Date: Tue, 23 Oct 2012 11:00:21 +0000


DevOps – Ten tips for developers

Wed, 15 Sep 2010 22:39:08 +0000

Last weekend I attended the ThoughtWorks Australia ‘Team Hug’ – a weekend away for all Australian TWers to get together and share ideas and have some fun. On the Saturday we run a conference program. This year we had so much interest (and quite a few international visitors) so sessions were kept short and punchy … Continue reading DevOps – Ten tips for developers

DevOps and the Iteration Showcase

Sun, 29 Aug 2010 04:31:37 +0000

Look down. Look up again. You’re on the agile team your team could be like. It’s the end of the iteration, and there’s a showcase this afternoon (sprint demo if you prefer) demonstrating all the new functionality the team has built in the last two weeks. In the room are members of the project team, … Continue reading DevOps and the Iteration Showcase

Projects are evil and must be destroyed

Sat, 28 Aug 2010 14:07:44 +0000

The majority of organisations I’ve worked with deliver new system functionality as development projects. These are funded with capex, and have a start and an end. Even projects that are ‘agile’ are still expected to finish at some date in the future, then once the system has been delivered it will undergo ‘handover’ to ‘BAU’. … Continue reading Projects are evil and must be destroyed

DevOps Mind Map

Tue, 22 Jun 2010 13:14:51 +0000

In the last couple of years I've become very interested in the interactions and collaboration between development and operations teams, the 'last mile' of delivering working software into production, and keeping that software healthy and sustainable in production. I've had some satisfying experiences working in teams that have bridged part of the divide between development and ops...

Enterprise Service Bust

Thu, 17 Jun 2010 12:53:06 +0000

When ESB advocates (or vendors) sell bus integration, they can make that diagram look so nicely clean and ordered - with nice square lines that never intersect. This appeals to the obsessive compulsive pointy haired boss types. The Enterprise Service Bus will guarantee to make your whiteboard diagram 42.4% less complex.

Build Manifesto

Wed, 16 Jun 2010 11:15:12 +0000

I met a team in the recent past who were adopting automated testing. Developers would write some automated unit tests for their application code, and run them in the IDE before marking their work as complete. Testers would then write down the testing scripts for the completed software, and then manually execute those tests, recording results. An automation tester followed behind, writing automated functional tests from a growing backlog of completed manual tests...

Whiteboard architecture – SEE???!!!

Sat, 12 Jun 2010 12:01:14 +0000

I once worked with an architect who was responsible for the technical direction of a major web project. When I arrived on the project it was clear that the intended architecture was not universally understood. There was some architectural documentation and wiki pages but they didn’t convey the information well and were already out of … Continue reading Whiteboard architecture – SEE???!!!

Continuous Integration – Ruthless Automation

Tue, 08 Jun 2010 05:23:48 +0000

I think 'Ruthless' presents the right intent when automating repetitive tasks - it's more than just aggressive or compulsive. My previous post talked about deployment repeatability primarily, but our goal is to improve the consistency of all processes that are repeated in the process of creating and maintaining system. A sequence of actions performed manually multiple times is a surefire recipe for disaster...

Continuous Integration – Repeatability

Wed, 02 Jun 2010 09:44:42 +0000

There's some simple rules to follow to reduce the unexpected - particularly in build and deployment as part of a Continuous Integration process. If something works, I expect it to work again next time, and will put in place something to make sure it happens exactly the same next time. If something fails instead of just fixing it, I want to put something in place to make sure it never happens again. Simple application of these rules can bring calm and order.

Continuous Integration – Commit Frequently

Fri, 28 May 2010 22:02:44 +0000

I thought by 2010 that this would be a standard doctrine, but it’s not (at least with the customer teams I coach). Commit regularly – minimum once per hour. Every minute past one hour should make you very uncomfortable. The hair on the back of your neck should start to stand up at 1.5 hours. … Continue reading Continuous Integration – Commit Frequently