Like all software developers, I like to think of myself as being irreplaceable. Clearly no-one on the entire planet combines my depth of technical knowledge, my amazing familiarly with the business domain and my legendary humility. I am truly a unique gift to any and all employers.
So I was particularly disappointed this week when I was replaced my this play-mobile figure at the family dinner table . I was out that evening so the daughter placed this unkempt looking plastic figure in my chair . She felt it was an adequate or even superior replacement. It’s uncertain whether my wife noticed the difference. Certainly the level of conversation was improved that evening.
So not as irreplaceable as I thought. I once replaced a colleague with a blow up sheep and sent him the photo. I thought it was very funny at the time – I realise now that it wasn’t as funny as I thought. I really hope my employer doesn’t realise how easily I can be replaced by a cheap child’s toy.
I’m particularly pleased with the photo of myself on this blog. I normally look a bit odd on photos but this one was taken about 2 days into a new job for an id card. I still had the new job glow. I was relaxed, tousled haired and the future lay ahead bright and clear. I look happy. So I thought I would upload it into Microsoft Cognitive Services Emotion API to get the confirmation that was indeed 100% happy.
I am shocked that even at my most happy I only achieve 92.8% happiness. My British reserve clearly means that I hold back 7% for that neutral stiff upper lip feeling. There are flickers of other emotions with contempt peeking out. Where does that come from ? It’s a new job. Surely contempt should only be registering when I’ve been there a month or two. I uploaded an uncropped image of myself a few months previously and I was registering about 3% fear . The only difference is that the very top of my head was visible that time. I’ve clearly got a very fearful haircut.
Is there a serious point to this? Probably not but it is my first foray into machine learning and as a professional software developer it certainly won’t be the last. I’m pretty fascinated about it. I hope I can start to register 100% happiness when I get into it more. At least 95% – come on!
After 18 months in the planning I am formally issuing a HTTP 301 request for the Brown family – we are emigrating to Australia. Right now our life has been dismantled and put in a 20 foot shipping container – I’m surrounded by removal people, boxes and general chaos as I write. We fly out in two days and land in Brisbane on 10th August where we will reassemble the Brown life in sunnier climes.
I’m very excited / tired / sad / hopeful plus a number of other emotions that I don’t know the names of. But whatever happens it will be an adventure. I do know that you regret the things you don’t do; you don’t regret getting out there and giving things a go – a fair go.
So the 301 request has been sent. As Wikipedia (almost) says
The HTTP response status code 301 Moved Permanently is used for permanent software developer and family redirection
Wish us luck!!
In my day job I send a lot of very routine emails announcing new deployments or pleading with people to fix the continuous build. I’ve started to amuse myself by sending them as haikus (3 line poems with 5, 7 then 5 syllabus on each line). I don’t think anyone has noticed. They just think I’m being a bit more terse than usual.
I this spirit I’m going to share with you 10 more beautiful haikus about software development. I’m sure you’ll agree that they capture the exquisite beauty of the software craft, the bittersweet sadness of an application crash and the inevitable fragility of a software patch to live. They are also short, don’t have to rhyme and are easy to write.
Traditional haiku collections are split into seasons. I’ll also split them but into categories that better juxtapose the joys and frustrations of the software development cycle.
Build server is slow
Disk whirs, lights flash but no builds
Test build being deployed
We wait for the build green line
Sadness. It’s amber
TFS build red
Queue the integration build
TFS still red
Build has been deployed
Is available for test
Please handle with care
SRP and OCP
Still don’t know Liskov
Flakey code base
Instigate peer code reviews
No one has the time
Detailed error report but
Where is the stack trace?
Corporate fruit bowl
Apples, bananas and plums
No-one eats kiwi
Our daily stand up
Managers attend. Involved,
But not committed
Personal dev blog
I watch the web traffic. Why?
I don’t really know