Hops Driven Development
The first post: why I started the blog, what you will find here, and my very own development methodology.

This is the first post, I write it to break the ice.
I started this space to jot down what I learn while building software: fixes to problems that cost me hours and attempts that went well (or badly). But it is not a purely technical blog, and I will get to that in a minute.
So, Hops Driven Development?
Here we go. Over the years I have tried several development methodologies: TDD, BDD, DDD. Then I noticed something: the good ideas almost never show up in front of the screen. They come later, once the laptop is shut. Sometimes during a padel match, more often over a good IPA, while the problem sits there “fermenting” on its own.
I named it “Hops Driven Development”. Careful: it is not an invitation to write code after a beer (it does not work, trust me). It is just the observation, unscientific and very practical, that stepping away is part of the craft. The most stubborn bug I usually solve far from the keyboard, and I come back to the computer with the fix already in hand.
That is how this blog started: notes taken on the way back from those breaks.
What to expect
Short, no-nonsense posts, in Italian and English. No theory dumps: where it helps you get code, links to the repos and the odd photo. And when something breaks I write about it anyway, because telling a failure often teaches more than a fake success story.
Topics
A bit of everything rattling around my head. Mostly code: side projects and ideas I had been sitting on for years that today, with a hand from AI, are finally within reach. But between one commit and the next there is also the beer I try to brew at home, padel, and whatever else grabs me at the moment.
Enjoy the read. And if you have a good beer within reach, even better.
Comments
Comments are moderated: I read them before they go public. This box loads only if you ask for it, so no request leaves for external services until you press the button.