Dean Wampler, one of the ever great ObjectMentor team, writes about the need to incorporate multiple development languages into a project. I agree with most of the things he said. It is important to choose the correct tool for the correct job. In our projects we have C#, C++, VB (6), SQL, HTML and VB
One of my greatest decisions ever (in my view, anyway) was on a project I managed a few years back. Under pressure, and no time to waste – sounds familiar, I know – all we could do is produce more bugs. I asked the test team lead to assign testers to developers, to sit with
Paul Stovell created a tool for traceability between code and requirements. All you have to do is add attributes to the classes/methods, and through reflection, it correlates the tested code to requirements. Therefore, it can actually create code coverage report against requirements. Cool stuff. [via Brian Harry]
I listened during my commute to the latest HanselMinutes. This time it was a bit different. Scott talked Tim Ferriss, the author of the best seller “The 4-Hour Work Week“. One of the things Tim talked about why working on email on a plane is more productive than doing that in the office. The two
All I have to say is Amen to this. TDD maybe new-ish, but software engineering practices aren’t. We just need the discipline. And do yourself a favor. Read Jeremy’s blog regularly. And memorize everything. Powered by ScribeFire.
This is cool. In one corner it’s Steve McConnell, author of Code Complete and a regular god in the software field. In the second it’s Eric Wise, one of the good bloggers on CodeBetter. Steve says absolutely Yes. Eric said No. Then little-ol’-me link Eric’s post on Steve’s comments and presto – a conversation erupts.
Scott is very smart, and may be sometimes very expressive (read: extreme) in his views. His blog is on CodeBetter, where other great bloggers are abound. He has a posts on dependency patterns. A primer. Very readable, and accessible to a newbie. It’s a good read. Read it here.
Check out my collection of ClearCase posts and feel my pain. Continuing our latest adventures with ClearCase, (I haven’t worked on anything else since Wednesday) today we reviewed the situation. We had to roll back the changes made on Thursday, due to side-effects that appeared. (Basically square one). Currently there’s no real solution in sight,
So a minute after I’m tossed into the ClearCase mix here’s what happens: We are opening a channel to our partners in the company’s headquarters to work on the server. ClearCase being what it is, it looked like a small task but grew into a large one. Most of the chages were done by TesCom,
I’m not that crazy about this, but I’ll play along for awhile. Our flop of the ClearCase implementation has left us with an addiction for the implementation company. In the past I’ve reduced the dependency by transferring knowledge to IT. This worked and now we want to get rid of the on site support completely.