home articles sponsorship

šŸ“ My User Manual

Hey there,

Welcome to my user manual! Iā€™ve written it to help coworkers get to know how I work, and my quirks. This document is a work-in-progress (obviously) and things will be adjusted based on my current team.

Latest update .

My role at #{your_organisation}

My official titles usually are ā€œback-end developerā€, ā€œsoftware engineerā€ or ā€œfullstack developerā€.

Iā€™m here to translate business needs into code. This follows three main paths:

What I value (and build)

My style

What I need to improve, work-wise

Best way to communicate with me

I prefer asynchronous communication. Hereā€™s a breakdown:

If you send me something urgent there, please ping me on Slack.

Most notifications are muted on my machine. When I read your message, Iā€™ll mark it with a ā€œmemoā€ emoji (šŸ“) so you know Iā€™m not ghosting you. If you need me urgently, please let me know upfront so I can prioritize your request. Focus is my main priority, though.

Working hours

How I give feedback

How I like to receive feedback

What I have zero patience for

Topics Iā€™m always happy to talk about

You wonā€™t shut me up about hiking, climbing, cooking, raising kiddos, pour-over coffee nerdism.

I can also be quite a bore when it comes to art history - specifically stained-glass, medieval churches and Roman mosaics.

Other things you might want to know:

Morning coffee