A new post, on the anti-patterns in unit testing has arrived on EverydayUnitTesting.com! This time we’re talking about tests imitating code, or in a more catchy name: Code matching. Check it out!
I’ll be at Agile Greece this year! In addition to the “Advanced Agile Programming Techniques” workshop, I’ll do the new, improved and highly Star-Wars enabled “Why TDD is important for everyone“. First, get your ticket, and then enjoy this interview about those topics and Star Wars.
If you’re already doing agile wrong, retrospectives are one of the first things you let go of. A shame really, but if you’re doing something wrong, you better screw up the thing that will bring you the most value. Why does dropping retrospective seem the least harmful? If you think planning is important (because it shows
Another one in the series! This time it’s about using tests for casting a big net, when what you’re really looking for is a small fish. Check it out on Everyday Unit Testing.
Last week I had a very interesting session. My dad and his friends have their own meetup, when they invite speakers to present topics of all kinds. I presented this week. While some of them did have ties to the tech industry, the topic was how organizations are built, and how they work. Why they are
Continuing the series of anti-patterns in the wild world of unit tests, this time we’re exploring writing logic (conditionals, for example) in tests, and why it may not be a good idea.
“Everybody, please, stand up”, I remember encouraging everyone to rise to the occasion of another daily stand-up “meeting”. Even with a room full of people who knew the drill, I still felt I had to ask them. With every practice we do, we anchor around one or two basic assumptions, we believe will help us achieve the
There’s a new post on Everyday Unit Testing (it’s been awhile, right?). I’m s tarting a new series of anti-patterns, what to look for, and how to fix them. The first post is about TDD without refactoring. Enjoy!
Had a great fun at the meetup yesterday. Plenty of interesting discussions. We also talked about the upcoming #APIL17 conference, and if you want to speak there, head on to the Call For Speakers page. Here are the slides from the talk.
Last time, we talked about the Definition of Done. We use is as vision of where we want to be at the end of the iteration. The question is: What happens if we’re not completely done? The truth is if we’re using the Definition of Done as a measurement, rather than a guiding light, we’ll