I removed the writing hour blocker from my calendar. It doesn’t work. To the person who told me that it wouldn’t work: you are entirely correct.
My Fitbit for the first time alerted me to a low heart rate of 45bpm while I was awake and reading at night. That’s low indeed — normal heart rates are in the 60 – 80bpm range, and lower for trained athletes. In any case, my nurse at the cardiologist’s told me that it was just fine.
My accent is weird. This week, I have been told, by different people, that I have a German accent, a Dutch accent, and also an Edinburgh accent. I am confused.
My burnout symptoms are worse this week, despite now being off sick for about two weeks. This might be the worst instance of burnout I’ve been in.
I know it takes a long time to recover from, and two and a half weeks of sick leave isn’t going to do much here. I’ll need to figure how to proceed still.
I need to take it easy on myself.
Let’s talk about tasks versus problems.
I’ve been reflecting on what has been going badly at work and I think one thing stands out: too often was I given ill-defined tasks to work on, rather than problems. I thrive on the latter. Here’s the difference:
Tasks have their solution spelled out, and the challenge is to perform the right sequence of tasks to bring the task to completion.
Problems, on the other hand, have no solution spelled out. There might be (and likely will be) multiple solutions, or there might be no feasible solution at all. Problems present much more of a challenge than tasks.
I’m most happy when I tackle problems, but I don’t mind doing the occasional task. In the last year or so though, I’ve had primarily tasks, and ill-defined ones at that, thrown in my lap. A task is ill-defined if it doesn’t spell out a solution, or doesn’t have an associated problem.
The frustrating and fruitless eleven-month project I wrote about in previous weeknotes was a task (“build a system that does X”) without associated problem. There are still no requirements defined (to the best of my knowledge, at least — I’ve not been at work for the last two weeks); the underlying problem is unclear. This task also had no solution, which I would’ve been fine with had the underlying problem been clear (though at that point, it would’ve no longer been a task).
Inevitably, I will ask the question “why?” for any task that is given to me. I need to ask that question to figure out what the underlying problem is, because that knowledge is crucial for doing any work properly.
I suspect that anyone who gives software engineers lists of tasks, rather than problems, sees software engineers as machines, automatons, rather than skilled human beings.
This distinction between task and problem illustrates why I had such an amazing time working on closecontact. There were no tasks, just problems that we worked on together. There was nobody who told me what to do: I figured that out either by myself or in collaboration with others. (Kat, when are we going to work together again?)
Not all problems are created equally, either. Good problems are rooted in human needs and wants, not KPIs and growth targets. A problem such as “increase sales by 10%” has no human needs or wants underneath; it’s just the profit motive all over again. So many problems are a rephrasing of “we want more profit,” and I’m not interested in solving this sort of problem.
The problems that closecontact gave me were genuinely interesting, and rooted in human needs and wants. We talked about how people want their data to be treated. We talked about what people do when they are standing in the queue to a club. We talked about all the ways we foresaw data breaches could happen, and what we’d do to mitigate all the risks. We talked about how to deal with door operators potentially misbehaving, and we talked about police abuse and how to mitigate that. We tackled real problems, and that is how we ended up building an exceptionally good product.
I’ve said before that I’ve become disillusioned with tech, but I really mean the tech industry. Software development is fine, and can absolutely be used to do good — but the problems it solves need to be rooted in human needs and wants.
The acting classes that I’ve taken feel like they’re all going a little too slow. So, I’m considering signing up for an eight-week intensive Meisner course, three times per week. This course has been recommended to me by three people already, and is legit.
This Meisner course also has the option to extend it from 8 weeks to 10 months. That would put me in quite a good spot with my acting skills, but requires some careful thinking about allocating time and money.
But there’s one problem: More than usual, my brain tells me that this acting endeavor of mine is just odd. I have a skillset (software engineering) that is perfectly serviceable and in high demand, yet I’ve become interested in something entirely different where the chance of success are quite low — the cards are stacked against me. It would be so much easier to make a living with software development… but I just don’t want to anymore.
Here is short story 2 of 26: Buried.
I might have overexerted myself with this story. I’m very much not clear whether I will be physically and mentally able (I blame burnout) to continue this 26-stories project.
Behold, one of the more surreal photos I’ve taken:
I preordered Cities Skylines 2, because of reasons.
Heartstopper season 2 is very aww.
The Football Ground With A Steam Railway Running Through It (The Tim Traveler): The title says it all really
Photos of inside the ICC (Flüpke, @firstname.lastname@example.org): So pretty! I missed the Tag des offenen Denkmals (Day of the Open Monument) — maybe next year?
Artificial ruins: So many things feel “fake” these days, so I’m rather glad to be reminded that in the past, things were fake too!
All The Times We Nearly Blew Up The World (Veritasium): Yikes!
The Boundaries of Rationality (Lawrence Yeo)
Dimensions of Power (Kent Beck)
Co-Founder Of Multibillion-Dollar Cryptocurrency Scheme “OneCoin” Sentenced To 20 Years In Prison (via Web3 is Going Just Great): I love a little bit of Schadenfreude.
The REAL reason why not to use Q-tips (Julie Nolke): Including this one for that particular friend who still uses Q-tips in their ears.
Optimize for delight (Annie Mueller): Hear hear!
Mario Zechner on changing food prices in Austria/Europe: Software used for good!