Have you ever worked with a developer who knows everything? The one who does a bit of tinkering in the evenings and weekends, and when the rest of the team come in, they can’t find anything in the code? Yes, it’s a bit neater, but it’s a lot more broken, because it’s less readable, because … More Bad change : The rock star developer and dealing with unexpected change
Did you learn something? Did you stretch yourself? Did you challenge your assumptions, or your practices? Do you feel like you achieved something last week? Did the frustrations inspire you to make it easier next week? Did you share them with others, in the pub, or on your blog, so others can learn from your … More Did you have a useful week?
Good architecture can respond to new requirements. It’s malleable where it needs to be. A good leader trusts their team. And builds their team so they can trust them. Architecture leads software, it defines the agility of the rest of the development, and it defines the fixed points that cannot be changed, that will always … More Embracing Agile Architecture
A great programmer sees software as a craft, honing a perfect solution from a sea of binary logic. Good software is beautiful outside and in, and even on a large scale is simple enough that there are no obvious bugs. They produce software that is precise and clean down to the last detail, continually improving … More Event Horizon : When sharpening the code means missing bug zero.
Many thanks to those of you who came along to my talk on why your API sucks. There were some great discussions during and after, and I hope I’ll be seeing slightly fewer reasons to tear my hair out in the near future. A few things that people mentioned that I want to discuss again, … More Developers are Users Too : Why the User Experience of Your API sucks #yourapisucks
If you don’t want to be chased by a horde of angry developers with axes, here’s a few things to keep in mind. And also see the making less-bad API tips from my DDDScotland follow-up post. User first : Design from the outside in Use Test-first design. And get developers to test it. Preferably developers … More Your API sucks : how to suck less
When doing scrum planning, trying to figure out what can be achieved in a sprint, there’s always variation. Especially in projects where you can’t rely on what came before. You can use yesterday’s weather, and break down tasks, but if you can’t estimate more accurately than “between a day and two weeks”, and you can’t … More Planning: the green and amber list
Finally, you’re ready to launch, you’ve integrated the API, you’ve decoded the documentation, you have passing integration tests, and FAT passed against their test server, with their test data. You go live. And everything breaks. Strawman testing Sometimes the test data or the API out of sync with live, and you find you’ve been testing … More Your API sucks : testing