Skip to main content

Do you still get the buzz? I do!


Whatever else I do to earn a living, I am a software engineer at the core. Outside of work other things give me a reason to smile - heavy metal bands, science fiction books or my family - but when it comes to work, writing software is what gives me the biggest buzz. Even after 33 years!

Recently I spent the weekend writing some software for a client. They have an app, which we built, that allows them to take photos and complete a questionnaire for installations so that they can record compliance. The software I wrote receives the photos and questionnaire responses from the app, generates a PDF document detailing the responses and attaches it to an email, along with the photos, to send to the client. Not a particularly exciting process most would agree.

It’s a straightforward piece of software (despite the security concerns and image processing which took a little while to get just right) which delivers exactly what the client needs, but we wanted to be doubly sure. So, in the early days of the software running for real (i.e. the client is using it, not just us testing it) we got copies of the emails the app generated so we could check everything was working as it should. And that’s where the buzz of being a software developer begins.

As developers, we’re not always able to monitor in what way or how frequently the software we write is being used by our clients. There are confidentiality issues to consider, as well as the practical aspects and cost concerns of implementing a suitable monitoring process. This means a lot of the time we rely on anecdotal responses from our clients, and of course feedback when something goes wrong (which thankfully, isn’t too often).

With this particular client we knew each and every time they used the software as an email would appear and we could see how the app was working until we, and they, were satisfied with the process. Even though it was such a simple thing, every time an email pinged through from the app I got a twinge of excitement and a flush of pride. To see something I’d created from scratch work successfully and be used by someone was a small but genuine reward for me and reminded me why I love doing what I do. The buzz of seeing software work.

What gives you that buzz every day and keeps you doing what you’re doing?

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