"Don't overengineer this. We need to move as fast as we can."Too many business representatives The Agile Manifesto is built on 12 pillars, the 9th of which (at the time of writing) is: Continuous attention to technical excellence and good design enhances agility. I regard the Agile Manifesto as a thing of truth. It has … Continue reading Technical Excellence
An essay on why software patterns become anti-patterns and how to avoid pattern rot.
https://www.thoughtworks.com/insights/blog/fitness-function-driven-development?utm_source=linkedin&utm_medium=social&utm_campaign=tech A great post from someone who really understands the problem. Worth a read!
At the time of writing this post, I am 41 years old, I've been in the business of writing software for over 20 years, and I have never ever experienced a release weekend. Until now. It's now nearly 1 pm. I've been here since 7 am. There are a dozen or so different applications which … Continue reading My First Release Weekend
I've heard a lot of people say something like "but we don't need huge scalability" when pushed for reason why their architecture is straight out of the 90's. "We're not big enough for devops" is another regular excuse. But while it's certainly true that many enterprises don't need to worry so much about high loads … Continue reading Scale or Fail
There are lots of problems that prevent businesses from responding to market trends as quickly as they'd like. Many are not IT related, some are. I'd like to discuss a few problems that I see over and over again, and maybe present some useful solutions. As you read this, please remember that there are always … Continue reading What’s Slowing Your Business?
Sample code here. Recently I've been looking into Specification by Example, which people keep defining to me as BDD done the right way. Specification by Example fully implemented includes the idea of an executable specification. A concept that has led me back to FitNesse having given it the cold shoulder for the last six or seven years. … Continue reading Getting FitNesse to Work
Developer's machine > dev shared environment > staging environment > UAT > production. Probably not exactly how everyone structures their delivery pipelines but probably not that far off. It allows instant feedback on whether what a developer is writing actually works with the code other developers are writing. And that's a really good thing. Unfortunately, it misses something... Each environment … Continue reading Integration Testing Behaviour with Mountebank
Moving from a monolith architecture to microservices is a widely debated process, with many recommendations and nuggets of advice available on the web in blogs like this. There are so many different opinions out there mainly because where an enterprise finds their main complexities lay depends on the skillsets of their technologists, the domain knowledge … Continue reading Going Deep Enough with Microservices
A particularly tricky epic hits the development team's radar. The Product Manager has been mulling it over for a while, has a few use cases from end users and has scoped things pretty well. He's had a session with the Product Owner who has since fleshed things out into an initial set of high priority stories … Continue reading When Things Just Work