A work colleague coined a fantastic term for code that just isn’t DRY:
Constantly Repeating Yourself - CRY
Not only does it describe one’s reaction to amazingly shoddy code, that just oozes of a developer spending all day using Copy and Paste, but seems an appropriate opposite.
Back to refactoring CRY code with me!
This sort of thing drives me barmy - why can’t people set a standard on tabs?
The above snippet is taken from eJabberd (a Jabber Server written in Erlang). Notice how some lines are soft tabs, others are hard. The causes havoc when dealing with merging in source control (I don’t care if you use a new fangled Git approach). Whitespace (both tabs and line endings) must be consistent on programming projects. Much pain ensues if they are not!
Personally I set rules in SVN commit hooks. This means that if a developer has anything ‘bad’ like Windows Line Endings on a Python project, then it is dealt with accordingly.
Saves a lot of merge pain!
Yay! The new service pack for Visual Studio 2008 is available for download. Cool, so let’s go download it… Oh wait it says in the Release Notes that:
During installation of Visual Studio 2008 SP1, MSDN Library for Visual Studio 2008 SP1 will not be installed on your computer.
To resolve this issue:
MSDN Library for Visual Studio 2008 SP1 is available as a separate download. See
Microsoft Download Center.
Cool - not only is the Download Center link incorrect… There is NO MSDN Library for Visual Studio 2008 SP1 download available. Good game.
I have posted a patch for enabling DTrace on Postgresql 8.2.5 on OSX. The way DTrace works in Postgres wasn’t compatible with how Apple broke DTrace at all. I’ll be submitting the patch to MacPorts when I can actually use their site… until then you can grab it here.
Linked below is the page I have added to this site which details a patch I have made to fix the DTrace extension for PHP to work with OSX Leopard after Apple appear to have broken a reasonable amount of functionality with DTrace *sigh*.
