Wow it's been a long time since I posted last. Anyway I found this very indepth article on creating tools to assist in debugging memory usage problems in c++. I've always been interested in the behind the scene's working of memory analysers and this is a great read. Monitoring Memory Usage - Gamasutra Now if my other projects ever slow down I might just get a chance to play with some of these things.

Recently this article from Mark Roulo from way back in 2001 made the rounds on reddit. He talks about how difficult c++ is as a language and why it should never be used for a large project. He goes into great detail about his interview questions designed to frustrate the most seasoned of C++ developers and spends a lot of time berating the use of pointers in C++. I have a real problem with kind of article. They focus way to much on the c side of c++ and not the ++ part.

All software development teams are hunting for that perfect source control system that perfectly handles every case. But lets face it source control is confusing and it's a huge investment of time to investigate which source control system to use, and if you pick wrong, it can be very costly to your project. This is probably the biggest reason new Source Control Systems take so long to take traction, Why would any business manager take a known risk of changing the source control system when the current one works. It worked for our last release...Right.

Ant is a great build system, but often it can be very confusing trying to wade through all it's documentation and find out how to do something you could write in a batch file in minutes. Case in point, iterating through a directory.

Hi my name is Richard Bezemer, and I am a Software Consultant based out of Calgary, Alberta, Canada. I hope to blog about technology, consulting and coding.