A package arrived a few months ago. Inside: a deck of cards with a red telephone on the box. “The Mentor Deck” by Seth Godin. I’m a beta tester, so I got one of the first 2,000 decks ever made. Each card has a QR code on the back that launches an AI conversation with a virtual mentor—Seth himself, o…
I had a problem.
I wanted to create a YouTube channel and had my first video ready to go, but then… nothing. Weeks passed. I had ideas, I had equipment, and I’d watched enough tutorials to edit like a pro. But I couldn’t get myself to shoot video number two.
Classic procrastination.
So I did what I often do when I’m stuck: I talked to Claude. But this time, I didn’t just ask for advice. I invited two experts into the conversation to help me figure this out.
A few days ago, I had a conversation with a former colleague who interviewed for a new job because she couldn’t stand her current one. Getting a new offer made her feel relieved and optimistic again: She had escaped.
Many others may not be so lucky this year.
Tech layoffs are accelerating. The economy—if we’re honest and look past the AI boom—looks shaky. Gold prices are spiking, which historically signals uncertainty ahead. And if you’re reading this feeling worried about your job, your future, or the general state of things, I know well how you feel.
Over 27 years and five major crises, I’ve learned one thing: the difference between thriving and drowning isn’t luck—it’s knowing what you can change and what you can’t.
It’s December 2024. I’m at AWS re:Invent in Las Vegas, coaching speakers on how to communicate effectively with technical audiences. Meanwhile, 9,258 kilometers away in Munich, a room full of homeowners is debating whether my 7.6-kilogram solar panels will blow off my balcony in the wind. This story…
”To me, you’re not just Systems Engineers—you are Speaking Engineers. I’ve got plenty of engineers working on great products. However, I need you to speak to customers and earn their trust in our technology.” That was Scott McNealy, CEO of Sun Microsystems, talking to a room full of technical profes…
All I wanted was to press a button and hear SomaFM Groove Salad through my home stereo. 🎵
What I got instead was six weeks of diving into AV receiver telnet commands, Raspberry Pi power mysteries, and NFC webhook proxies. Sometimes I spent an entire week debugging my Home Assistant setup only to discover I’d been using the wrong IP address the whole time 🤦♂️.
But here’s the thing: the journey is the reward. Sure, I could have just lived with telling Alexa to turn on my AV receiver, connect to it over Bluetooth, then asking it to play what I want. But then I wouldn’t have learned how UPNP broadcasts get mangled by WiFi bridge modes, or that a 2.2W Raspberry Pi can teach you more about power supply stability than any electrical engineering textbook.
This is the story of how a simple goal—press button, get music—led me down some of the most beautifully complex rabbit holes I’ve explored in years. And why that complexity is exactly the point. 🐰
Working for my then employer’s Munich office in 2011, I felt it—that hollow sensation when your career becomes a treadmill. The acquisition of the company I originally joined had stripped away the technological beauty and purpose I’d thrived on for more than a decade. The rigid culture, the pure commercial focus, the loss of autonomy.
I wasn’t incompetent, broke, or irrelevant… I was just bored.
And boredom, I realized, was the first horseman of a dying career.
A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly.
Specialization is for insects.
— Robert A. Heinlein
When I read a recent article about Expert Generalists on Martin Fowler’s blog, I immediately changed my LinkedIn title. Finally, someone had named what I’d been doing for 27 years without realizing it!
“How can we become a digital company?” The manufacturing executive looked genuinely worried. “We make physical products, but everyone says software is eating the world.” I’ve heard variations of this question hundreds of times over the past decade. Sometimes it’s about cloud computing, sometimes mob…
Here’s a secret: after almost 13 years at Amazon Web Services, I still felt like most people around me were smarter and more capable than me. And now, as a blogger looking at other writers? That feeling hasn’t gone away. If this sounds familiar, you’re experiencing imposter syndrome—and you’re in ex…
Back in the late 80s, I was a computer-enthusiastic teenager helping my mother, who was leading the German consulate in Rome at the time. I still remember teaching her secretaries how to use PCs for word processing instead of their trusty typewriters. I guess that was my very first gig as tech suppo…
154 months of building solutions at AWS taught me something unexpected: the most resilient professionals are people who can build cloud architecture, debug a cultural problem, coach a group of executives, mentor a struggling colleague, and learn something entirely new by Thursday. Think Robert Heinl…
I remember a colleague, let’s call her Sarah, who was checking her phone every minute during our 30-minute meeting, apologizing for being distracted, mentioning her endless to-do list. She was drowning, and she didn’t even know it. Sounds familiar? Here’s what I learned: overwhelm is not a time mana…
So, I did it again! In the near future, I plan to blog more often (this time for real). But, meanwhile, my blogging setup felt a bit dated. So I re-factored it again. How?
I used Anthropic’s Claude Sonnet (first 3.5, then 3.7) to help me refactor stuff. Claude lives inside my new favourite code edi…
In my current job, I occasionally mentor people and one of the questions I often get is: “How do you find good opportunities?” By which people mean cool technologies to explore, great projects to be part of, opportunities to talk at conferences, great companies to join, interesting people to meet, a…
When I started blogging in the early 2000s, RSS emerged as an open standard for spreading the news. New post? Blam, everybody interested got a notification in their favorite newsreader. Back then, building a proper RSS feed was more of an art than an exact science: Crafting proper XML while taking a…
A long time ago (2017), I wrote about modernizing my blog’s infrastructure. Guess, what: Time to modernize again! Back then, I migrated from Drupal to a self-written, Jekyll-inspired static site generator written in Python (my current language of choice for most projects). I spent the majority of th…
A lot has happened since I changed my job more than 5 years ago.
I learned new stuff, met a lot of customers, blogged and podcasted (though on other platforms), and I didn’t get to give this blog much care.
In the last few articles, I shared a few thoughts on how I think the world of IT is changing, which became the context for my good-bye to the world of physical IT altogether.
As of last week, I started working for Amazon Web Services (AWS) as a Solutions Architect, helping customers architect systems and solve technical problems using the latest cloud computing technologies. I’m very thankful to be able to work here, as it brings me back to the very center of IT innovation and gives me the opportunity to do lots of new and interesting things.
In the last weeks, I’ve been digging around AWS and its services, playing with stuff and meeting lots of inspiring people. So I thought I’d put together a few links for those interested in exploring the world of the AWS cloud computing platform for you to learn more about AWS:
A while ago, I argued that the world of IT is changing, and that change is good. And that as a result of change, many people would need to change their jobs.
Well, I did it. Last Tuesday was my last working day at Oracle.
