In May this year I had the pleasure of hosting Michael Feathers at Motorola Solutions in Krakow. We invited Michael to do a kind of extension, in the form of workshop and a lecture, to his great and well-known book "Working Effectively with Legacy Code".
Michael's skills are very rare as not only is he skilled in teaching the methods of dealing with legacy code, but he also feels comfortable with doing so in C++, in addition to Java and C#, which both are more pervasive among XP professionals.
It was a great experience and I think many of us will remember some of the ideas we learnt during this visit.
I have had the rare opportunity of watching and being part of the change that the software industry has gone through throughout over 20 last years. This blog is a collection of my reflections on pursuing agility path. It includes observations and advice regarding development teams and notes on useful engineering practices. Enjoy! Piotr Górak.
Friday, October 31, 2014
Michael Feathers' visit
We may often come across a piece of code that was written without Unit Tests at all. In addition, the piece of code may be dealing with IO l...
Google Mock provides several ways to maintain state inside mock objects. One way of implementing state maintenance is with SaveArg . Consid...
Google Mock provides a way to return newly created objects from a mock method. Suppose we have a Generator class that is supposed to ...
Can we verify that a mock object is properly destroyed? Of course! There is a couple of subtle differences between mocking regular func...
Requirements have a long history in software industry. We all have heard or read terms like: requirements definition, requirements managemen...