Welcome back to the new blog, almost the same as the old blog

The Lone C++ Coder's Blog from The Lone C++ Coder's Blog

The move to the other side of the Atlantic from the UK is almost complete, I’m just waiting for my household items - and more importantly, my computer books etc - to turn up. So it’s time to start blogging again in the next few weeks. Due to some server trouble in the UK, combined with the fact that I do like Serendipity as a blogging system but was never 100% happy with it, I’ve switched to using WordPress on a server here in the US.

About

The Lone C++ Coder's Blog from The Lone C++ Coder's Blog

I am a software engineer and occasional development manager with over 25 years experience writing production code, mostly in C++. During that time I’ve worked on anything from Windows device drivers when people said you couldn’t write those in C++, to financial trading applications. I have an interest in programming languages in general and am a firm believer that you cannot call yourself an experienced software engineer if you aren’t able to write good code in multiple programming languages.

The homebuilt NAS/home server, revisited

The Lone C++ Coder's Blog from The Lone C++ Coder's Blog

This is a reblog of my “building a home NAS server” series on my old blog. The server still exists, still works but I’m about to embark on an overhaul so I wanted to consolidate all the articles on the same blog. I’ve blogged building my own NAS/home server before, see here, here, here and here. After a few months, I think it might be time for an interim update.

Building a new home NAS/home server, part IV

The Lone C++ Coder's Blog from The Lone C++ Coder's Blog

This is a reblog of my “building a home NAS server” series on my old blog. The server still exists, still works but I’m about to embark on an overhaul so I wanted to consolidate all the articles on the same blog. I’ve done some more performance testing and while I’m not 100% happy with the results, I decided to keep using FreeBSD with zfs on the server for the time being.

Building a new home NAS/home server, part III

The Lone C++ Coder's Blog from The Lone C++ Coder's Blog

This is a reblog of my “building a home NAS server” series on my old blog. The server still exists, still works but I’m about to embark on an overhaul so I wanted to consolidate all the articles on the same blog. Unfortunately the excitement from seeing OpenSolaris’s disk performance died down pretty quickly when I noticed that putting some decent load on the network interface resulted in the network card locking up after a little while.

Reblog: Building a new home NAS/home server, part II

The Lone C++ Coder's Blog from The Lone C++ Coder's Blog

This is a reblog of my “building a home NAS server” series on my old blog. The server still exists, still works but I’m about to embark on an overhaul of these posts so I wanted to consolidate all the articles on the same blog. The good news is that the hardware seems to be behaving it for a while now and everything appears to Just Work. FreeBSD makes things easy for me in this case as I’m very familiar with it so I only spent a few hours getting everything set up.

Reblog: Building a new home NAS/home server, Part I

The Lone C++ Coder's Blog from The Lone C++ Coder's Blog

This is a reblog of my “building a home NAS server” series on my old blog. The server still exists, still works but I’m about to embark on an overhaul so I wanted to consolidate all the articles on the same blog. Up to now I’ve mostly been using recycled workstations as my home mail, SVN and storage server. Nothing really wrong with that as most workstations are fast enough but I’m running into disk space issues again after I started backing up all the important machines onto my server.

The joy of using outdated C++ compiler versions

The Lone C++ Coder's Blog from The Lone C++ Coder's Blog

Thud, thud, thud… The sound of the developer’s head banging on the desk late at night. What happened? Well, I had a requirement to make use of some smart pointers to handle a somewhat complicated resource management issue that was mostly being ignored in the current implementation, mainly on the grounds of it being slightly to complicated to handle successfully using manual pointer management. The result - not entirely unexpected - was a not so nice memory leak.