For technical projects, you have README files that (hopefully) give you all the information you need to work with a project.
This page is here for the same reason. It’s a README for me.
For feedback, just come and find me — there are plenty of ways to reach me.
TL;DR: there isn’t one. You’ve got these few minutes, so read on.
What does success in the job mean to me?
I work in a thorough, careful way while staying pragmatic.
I like continuous improvement. I like delivering solid work that can robustly withstand whatever QA and users come up with. I've got an okay-ish idea on when to call it a day and ship. And I like tickets/projects/milestones finished on time without the need for "crunch time" – no matter if it's before or after a launch.
How I communicate
If you've worked with me for a bit, you probably know I like to talk. I'm mostly transparent with everyone and share information as soon and as much as possible. I happen to be quite fast in that regard, so you might want to check back if things are unclear after a probable wall of text from me.
It doesn't matter if it's chat, email or direct conversation, I rarely have a hard time communicating. I mean… what are you reading right now, eh?
What I don't like at all, though, are unscheduled, spontaneous video calls. Even if something is super urgent, I'd like to have at least an idea of what we're going to talk about and what the goal of our conversation is.
On Fridays, I'm only working half a day, so I'm not available for meetings in the afternoon. As soon as I'm spending time with my daughter, I am not available at all. I'm going by "As long as no one is dying, we're probably fine until tomorrow".
Things that could annoy you about me
There are two quotes I really like:
There is more humor than hate to be found in just about every situation.
(Ryan Holiday: The Daily Stoic)
When we're miserable, we're miserable. Now what needs doing next?
(David K. Reynolds: Constructive Living)
I try to weave these thoughts into my daily work. That's why I might react in a way you won't think is appropriate – which can potentially annoy or confuse you.
I'm well aware that the ideas these quotes are based on can be very (VERY) challenging, depending on your personal situation. AND I'm at the same time sure that they are helpful despite or even exactly because of this.
Most of the time, I'm in a pretty good mood. Which also means that I confront challenging situations with a smile on my face, thinking "Oh, that's interesting!". I haven't gotten feedback from people about this being confusing, but I can imagine it might be. Don't worry! :D
How do you gain or lose my trust?
Generally, I'd describe myself as trusting and optimistic. So it doesn't take much to earn my trust in the first place.
I work from the assumption that everyone I work with is capable and willing to learn. Meaning: able to do their job competently, and to close their own knowledge gaps under their own steam.
When I see people getting more independent and better at what they do – through pairing, through digging something up themselves, through whatever initiative – my trust grows accordingly. When people don't do that over a longer stretch, I get sceptical.
A good quote on that:
"When in doubt, play the [person] who makes the fewest mistakes." Not a bad way to think about a lot of things in life.
(Dan John: Never Let Go)
My strengths
I love trying out new technical things. I like CSS a lot – enough that I'll happily chase down and fix obscure bugs in it.
I get into new technical things far enough to feel like I've understood the underlying principle, but not down to the last detail. Put another way: I can play quite a few different instruments reasonably well, but a Metallica guitar solo was always more work than I wanted to put in. And no, "Nothing Else Matters" doesn't count.
That curiosity is also what pushes me to bring new technical things into projects, once I've kicked the tyres on them and think they make sense.
So if you're stuck yourself: I might have an idea about where to look, or which direction to think in.
I'd also name communication as a strength – I mean… I'm writing a manual for working with me, right?
Where I want to get better
I was once told that I find technical problems interesting only until I've solved them to my own satisfaction. That feedback is a while ago now, but I think parts of it still hold: I get impatient when I have to explain things too often. Especially when I consider them obvious and "simple"™. Which, of course, they usually aren't. So staying with it, and explaining things differently, more simply, better – that's certainly something I can improve.
I've worked with a lot of great JavaScript people and learned a great deal from them – enough that, for years, this section said I wasn't as good as they were. I've stopped believing that. The useful half of it stuck, though: I know who to ask in which area, and I'd rather ask early than be clever on my own. And when none of us knows how to go on, we've obviously found a great situation to learn something in.
When it comes to communication, I'm very happy to avoid conflict. I work on that constantly – and I'm sure I can get considerably better at it. So if you don't hear from me, or I only ever say nice things: please point out that I'm allowed to talk straight with you or with others. And hold me to it.