Skip to main content

Norfolk Tech Journal: Second Issue Out Now!

Trite as it may sound, I moved to Norfolk for love. I was working in London to pay for a flat in Colchester which I wanted because it was an easy commute to my job in London. My girlfriend, however, lived in Norfolk and I was travelling to see her every weekend. Clearly, the only logical move was to get a second mortgage, based on my London salary; jack in my job the instant that mortgage cleared and move to Cromer with two mortgages, no income and no job lined up.

My thinking at the time was that my wife (a zoo keeper) would find it hard to find work if she moved and I (as a senior java developer with years of banking experience, plus the conceit that that brings) would simply walk into a development job. I had overlooked one tiny detail: there are only about 8 Java shops in Norfolk. It was sheer luck more than anything else that landed me my current role.

I’m not sure if the dearth of Java jobs in the county is a reflection on Norfolk or on Java but what I do know is that we desperately need an injection of fresh talent into this county; it’s getting harder and harder to find people.

A large part of the problem revolves round the pigeon holing of developers. We shouldn’t be talking about Java Developers and C# Developers, we should just be talking about Developers. A good developer can pick up a new language in minutes and algorithms and best practices are largely language agnostic which can be applied anywhere. Even when idioms don’t translate well between languages a good developer will know this turning to Google which is awash with articles on “Language X for Y developers”. So why shouldn’t a good C# developer be considered for a Java role and vice versa? They are, after all, very similar languages. But it seems you must have X years experience in language Y and, for the ultimate irony, you will be interviewed about design patterns from a book on C++.

The second issue is out now and can be downloaded here.

Words: Dom Davis

Comments

Popular posts from this blog

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...