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

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...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...