Oren Ellenbogen writes about TDD, testability and Scrum implementation in his team. Very interesting. The way I react today to untestable code makes me realize how far I’ve become as a developer. So far off than the “just-make-it-work” manager I used to be.
What happens when you have disparate systems? Those that don’t know how to talk to each other? You need a translator. If you’re lucky, it’s an automaton. Sure, you need to build it, but it will do most of the work for you. But if your luck’s cup is not as full, then it’s a
Scott Hanselman is moving to Microsoft. I’ve been following Scott’s blog and podcast “Hanselminutes” over the last year. I wish him luck, and that we all benefit from his new position. Scott describes himself as a geek. When he saw a CD, he wanted to see how it works (a quote from the last podcast
My last post reminded me of another thing that came up during the last audit. The code review process was just beginning, but I already had forms as proof of the process taking place. The auditor looked at them and asked “why aren’t there names on the forms?”. I said proudly (as it was my
Today one of the developers asked for a meeting with me to discuss some design issues. It’s been a while since I did one of those, but was very entertaining for me, and helpful and productive for him I hope. At the end of the session, I reminded of a question that came up during
Our management team decided to cancel entry and leave time tracking. Task time tracking will continue using our Project Server according to the project plans. I don’t think time tracking enforces anything. Since it measures the time you were at work, not the time you are actually working, and not how well you manage your
This is something that I used to hear from the developers. I bet I used it as a developer and then I got a change to use this phrase today. I have a small task scheduled to run on a server to collect bug information. It ran every day at 3am, until a month ago.
In the beginning it was dark, and procedural. So for instance, if you wanted feedback on a feature, you would either communicate it verbally, send screen shots, or wait for the release. Then the managers rebelled. We saw the obvious problem here – our customers needed to actually use the software to give feedback, sooner
Anders Noras writes about how to develop a DSL (domain specific language) in C#, using fluent interface. Most of what I’ve seen until now was in Ruby. It’s very interesting, and I need to imagine how you TDD this thing. It is a leap outside the OO world, as some OO rules are broken for
One of the processes we were planning to introduce was some root-cause analysis for things that happen along the way. As luck would have it, one of the project managers came to a conclusion he needed something like that today. A bug that was discovered was the trigger, and the three team members involved were