Background

Recently I was asked by my manager how they could improve the working life of part time software engineers. Working as part time software engineer myself, it makes sense to draw from my lived experience.

To give you context about myself, I normally work on a range of development tasks. Professionally I have mostly worked on web-based systems, from front-end with React to back end with Node-JS and Java (Springboot/Spring, custom AWS lambda and enterprise level work with Oracle message passing). My personal work includes, but not limited to, C++ projects dealing with more low level tasks such a parallel programming with OpenCL, Android applications, windows native terminal multiplexer and machine learning prototypes. I don't outline this because I want to brag, for from it. I outline my experience because I hope it gives context to my point of view and how I have experienced the software development industry.

In the following sections I use the term "do" as an instructional guideline and not as a hard rule, at the end of the day this is my opinion and you are free to do what you think is best. What I am about to say even goes against some Agile Principles.

This is especially true for principle 6,

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Again, form your own opinion and never take anything anyone says as universal truth.

My Do And Do Nots

1. Do prefer written communication - Don't assume any vocalised message is remembered and understood

2. Do give agency to people - Don't micro-manage people and their work

3. Do use tools for writing - Don't require every update to be vocal

Explanations

Do prefer written communication

Too often in meetings things are said or instructions given where I mishear things, or I am tired, or just in general not paying 100% attention when I should be. Using written communication helps ensure that the message is articulated, can be referred back to and everyone can read the message when they need to.

An example I recently experienced was I changed teams at the end of a piece of work I completed. I didn't get a chance to run people through it. Taking my own advice, I had written instructions so no knowledge was lost.

A prudent example during 2020 Covid-19 lock-downs was being on Zoom calls for meetings. Then to just have your internet disconnect. Writing your explanations and actions would mitigate any missed information.

Another example is joining a new job or team. Sitting through hours of meetings explaining things is not a great way to pass on knowledge. Instead try to write down as much of it as possible. That way you create a source of truth. Then everyone can read it in their own time and pace.

There are many examples of where using written communication is superior to verbal communication. I am biased to written communication though. It is not perfect for all situations and we still need to verbally communicate when the time comes; just be ready to challenge your assumptions.

Do give agency to people

The worst thing I can imagine when working with a manager or a direct report is being micromanaged. People need agency to do work how they want and in their own time. If you need boundaries, use your tools to establish boundaries and expectations. For instance a lot of work has time restrictions, so communicate that through your tools. I say tools because that ensures there is a good understanding from both parties through a source of truth. I've professionally used Jira in the past for communicating technical requirements. Having all the information on the card was extremely helpful when the time was taken to write it down. This goes doubly for part time workers. When they are working they know there is a source of truth and they can read it when they are actually working and not worry about missing information because it was in a meeting when they weren't working.

Do use tools for writing

Re-empathising the case for written communication. Project and day-to-day updates are the most common form of meetings I have experienced. Nearly all of them could be written. Using tools to provide written updates means you don't have to set-up meetings just to communicate updates. For example, write updates in the Jira cards, in the git pull request, in email, in instant messengers, etc.

Post Note

I wrote this post several months when I transitioned from part-time to full-time employment and I never published this. I didn't publish this for several reasons, none of which are really relevant; mostly to do with my emotional state. After spending time working full-time, I think the points I raised here could be greatly beneficial to full-time work as well. Especially now flexible working is much more common as we continue to fight this pandemic.