Author: moritz

on leadership

IT is probably fun to work in because you’re working with a bunch of folk that are pretty much successful because they’re good at finding patterns in stuff, and then finding solutions that address problems that look just like that. And that works really well for writing software. And only works so well for running […]

Post-Vacation Check In

I’ve been on a vacation for a few days and gave myself a somewhat needed break from writing posts at a high frequency. I realized that even with only 500 words, the posts get a little diluted over time. That’s ok, and it’s mostly an observation that doesn’t surprise me. What makes me happy is […]

maybe it was never hard.

A key part of my strategy of leading engineering teams is removing complexity and shaping focus, to ensure the important things are clear and can actually be built. I’ve been doing this a lot, and I’m stuck wondering why we’re building so many things that absolutely no one needs. What do I mean by "so […]

things to learn as a software engineer

Today, enjoying a day off and browsing around Twitter to get upset about nothing, I found something to get slightly excited about. I don’t have the patience to find the tweet now, but it was very much along the lines that being able to do most things as a software developer without touching your mouse […]

information symmetry

I’m a manager, and I’m spending a substantial part of my time writing things down, and hopefully creating clarity in doing so. The reason why I’m doing this is because I want to be the antithesis to a go to person. While I generally appreciate when people come to me for advise, for chatting or […]

five things to notice

I’ve got a bit of Monday advise. Mostly for me, to prepare myself for an interesting week to come (and a short one at that, with Wednesday being a bank holiday here). Since I’ve gotten myself a journal – a red one, just in case – I figured that there has to be something meaningful […]

default to really fast

In negotiations, there’s a term called anchoring. It refers to the concept that whatever first number is dropped in a conversation, is the number that will be the mental anchor for the rest of the negotiation. It’s why you should avoid saying the first number in any negotiation – if you’re too low, you’ve anchored […]

estimations

Whenever we talk about actual work, there’s a tendency of trying to understand how long something will take – or any other proxy metric that means the same thing, but in a more indirect way, such as complexity. This can serve a helpful purpose, but I think it’s mostly a distraction. Let’s talk about estimations! […]

you need a kitchen

Remember house parties in your twenties? I do, and one of the highlights – and one of the common thing between most parties – was that the kitchen would be the focal point of most gatherings. Since a lot of partying revolved around drinking various kinds of beverages, the kitchen offered itself as an ideal […]

no is such a boring word

To get something out of the way – yes, I do say no quite often. But even if "no" is in itself a complete sentence (true!), I still think it’s a really boring sentence. Make better sentences. If conversations are two-way streets, no is like a stop sign. There’s no opportunity in no, no next […]