So, you have your shining, ticketing, tomato-shaped timer on your desk and you are a proud practitioner of the Pomodoro Technique®. I’ve got bad news and good news. The bad news is the Pomodoro Technique® can seriously damage your team’s productivity. The good news is that it’s very likely that you are not practicing the … Continue reading Pomodoro Technique® Considered Harmful (don’t worry: you are not using it)→| Arialdo Martini
Fork me on GitHub or just grab the code from the gist.| Arialdo Martini
Also available in Czech, kindly translated by Aleš Roubíček TL;DR Writing Legacy Code* is a distributed activity. *In Working Effectively with Legacy Code Michael Feathers defines Legacy Code as “Code with no tests“, which reflects the perspective of legacy code being difficult to work with. I’ll stick to this definition. Long version Oh, no! Bad … Continue reading How To Spot The Legacy Code Writer In Your Company (Hint: It’s You)→| Arialdo Martini
TL;DR Want to help editing a collaborative version of Definition Of Done checklist, driven by questions, rationales and “don’ts”? Click here and feel free to share your ideas! Long Some months ago my team and I had to define a Definition of Done for one of our projects. Each item of DoD should be an … Continue reading The Definition of Definition of Done→| Arialdo Martini
I agree with Michael Kennedy when he says that Software Development could be modeled as a Knowledge Discovery Process, “the process of going from 0% knowledge about an idea to 100% knowledge of a finished product ready for delivery to a customer“. I agree so much that I decided to adapt my future Daily Scrums … Continue reading What-If Daily Scrums→| Arialdo Martini
Some weeks ago I gave a talk at AgileDay.it. My talk was about a weird experimental Kanban board, and the Leitmotiv I used was around the differences between Principles and Rules. The topic was: we often learn methodologies mocking rules (often, without getting the point) rather than trying to understand the principles behind them. This … Continue reading Principles and Rules→| Arialdo Martini
tl;dr version Rule #1: write commit comments before coding Rule #2: write what the software should be supposed to do, not what you did Long version Dan North changed my life You should read Dan North’s epic post Introducing BDD. It might be a little of an oversimplification, but the whole (revolutionary) Behavior Driven Development … Continue reading Preemptive commit comments→| Arialdo Martini
Kent Beck is credited as the TDD inventor. Yet, he claims he just re-discovered it. When asked why does he refers to the rediscovery (not the invention) of test-driven development he explained: The original description of TDD was in an ancient book about programming. It said you take the input tape, manually type in the … Continue reading You won’t believe how old TDD is→| Arialdo Martini
This the second part of How I Was Able To Be Successful Even When Forced To Use Waterfall Rule #1: take your time Luckily, your estimation meeting will be much more fortunate than mine (see Part I)…| Arialdo Martini
Some days ago, one of my colleagues showed me an unit test, coded by someone else. It was something like| Arialdo Martini
