You think that Arnold and Sylvester movie careers were head to head? Let me tell you the story of what happened before that. <Dissolve Effect> Arnold and Sylvester had a struggling software development business. Arnold wanted better code design. Because he was after better design, he chose TDD, with all the design goodness it brings.
Uncle Bob Martin recently blogged about the hordes of untrained developers coming into the industry, which eventually leads to some huge software disasters. James Bach wrote about the failures of HealthCare.gov that stemmed from incompetence in software management. These are very good articles, that make you think: Should software professionals (developers, testers, managers) be regulated?
A recent comment on (the now legacy) “4 signs that agile is declining”: “Let me be clear: Every single failing or failed project I have seen in the last 35 years, regardless of development process, has had self-inflicted mortal wounds from execrable language skills and the resulting breakdown of communication. People nod their heads up
There are many agile conferences these days. Many of them are not about what we used to call “agile” anymore. In fact, a friend pointed out when I mentioned a TDD session from an agile conference, saying: Really? An agile presentation with code? Most of the topics today are moving towards lean, kanban, leadership and
Here’s another example of why language matters, and how the words we choose matter so much. I tried to join the European Lean-Kanban tour, not in person, but on twitter. (By the way, seems like an awesome tour, I’m thinking about going there next time around). And then the following tweet comes up: “@cyetain: Talking
When asked:”What’s the best thing I can do right now to improve my code quality” I always answer: code reviews. A code review is the best bug preventer out there. And even more, I like its older brother better: Pair programming. Because if a code review finds bugs after the fact, working in pairs finds
I’ve been thinking lately about how agile turned out to be the way we know it today. And the more I think about it, I get more depressed. You see, agile was supposed to save us all. It was supposed to be the bridge between business and developers. And 10 years after its inception, we
I want to thank everyone who come to my presentation yesterday. I got my inspiration (and a few jokes) from the following presentations: Agile Overview – Robert Martin The Land that Scrum Forgot – Robert Martin The Mistake at the Heart of Agile – Michael Feathers And for the people who want to read the
Here’s a short, incomplete list of my upcoming public speaking engagements. When I know, you’ll know. I’ll be speaking at the Agile Development Practices East Conference on Wednesday November 9th, at the Rosen Centre Hotel, Orlando, Florida. My talk is about “8 Principles for Better Unit Testing”. I’ll be at the conference area throughout Wednesday
Last week I had great time hosting a Typemock Webinar called “10 secret unit testing tips”. The fun thing was that I’ve discovered both in preparation and answering questions live that I have at least 20 tips in me for at least two more webinars. So prepare for “10 secret unit testing tips strike back”