Introduction

OK, here goes...

I work in IT Support - mostly Windows PCs, some server, networking, telephony, yada yada.  No Linux what so ever.  Not deep, but broad.  

I like making things better.  Bad design should be illegal.  Poor processes are horrific.  Make a mistake once, learn something, document the fix, and don't do it again.  Kaizen is where it's at.

My son is 15, and he's a technical boy, too.  However, these days, it's hard to get your hands dirty.  It's all about the shiny.  And the fact that you can't even take the battery out of an iDevice makes me irrationally angry.  It's like buying a car with the bonnet screwed down.

So, here's the Raspberry Pi.  Bare naked circuit board, just asking for some mad idea to be thrown at it.  With a nice open-source ethos that appeals.  And, a bit of a vertical learning curve.  

OK, I've taken enough ideas and fixes from the internet over the years, and not repaid a lot (with the exception of a few thousand hours on www.experts-exchange.com).  Time for me to return the favour, with some reflections on my faltering early steps with the Pi.  Wish me luck!