The conference is 3 weeks away!
I hope you’ve registered, because otherwise, when you get there, we’ll have to throw you out, and it’s going to be embarrassing to both of us. I guess that’s one way to Learn Something New, but instead: Go register.
I’ve mentioned our keynote speakers’ sessions before: Angel Medinilla’s “Agile Kaizen” and Claudio Perrone’s “Lean Problem Solving with A3 Thinking & Popcorn Flow”. I would have gone to either if I could clone myself. However, I’m proudly stuck doing the other technical workshop “Advanced Agile Programming” with our next 5 Whys Challenger, Lior Friedman.
Lior also has a session on conference day, called “About Test Smells”. If you know Lior, or just read the description of the session of the workshop, you can bet on getting a whole lot of actual coding how-to knowledge at the conference. Let’s give him the mic.
Why should people come to the conference?
Because this is the place to hear what’s new in the agile world. And talk.
Why should people come to my session?
Because it’s about time people use their unit tests to actually drive their design. After all if you invest the time to automate your tests, you might as well make the most out of them.
Why did I choose this topic?
Too many times I see practitioners invest the time and effort to learn how to automate their tests, and fail to get the most out of them. They encounter difficulties in test maintenance, in enhancing their test coverage, etc. In this session I hope to help some people learn how use their tests to indicate underlying issues that may reside in their production code
I think that after so long in failing at estimating, we really need to find other alternatives. We’ve wasted enough time at getting our learning how to give dead wrong estimations.
Why did the chicken cross the road?
Cause there was a waterfall just ahead on this side
Well, now. Didn’t even to plug my own session this time. Instead, I’ll mention the “Advanced Agile Programming” workshop again: We’ve collected a few good practices that improve how we write code. But they call them practices for a reason. That’s what the workshop’s about: practicing. If you want to be a better programmer, that’s the workshop for you. Check it out.
See you in 3 weeks!