Posts tagged "ai"

22 posts

„Nah ist / Und schwer zu fassen der Gott. / Wo aber Gefahr ist, wächst / Das Rettende auch.” — Friedrich Hölderlin, Patmos (1803)

(Near is, / and difficult to grasp, the god. / But where danger is, grows / the saving power also.)

A few weeks ago, I wrote a post titled Thinking with Claude: why Cyborg writing works better than Centaur writing. In the LinkedIn comments, a reader named Christopher pushed back: Leaning on AI to help me write, he argued, was training my brain to “surrender executive function to external sources.” Examples: freed prisoners overwhelmed by everyday choices, ex-military struggling with civilian life, people leaving long-term institutional care. The source doesn’t matter, he wrote. The offloading pattern is the same.

While my initial answer was along the lines of “using your executive function is a choice”, I think it’s not that simple, after all, and I owe Christopher a real answer. In fact, his comment pushed me into a weeks-long thinking journey, during which I looked for research, came across interesting related articles, and reflected a lot on my own AI use. I also jammed with Claude, and yes: I used the very tool Christopher warned me about to think harder about his warning. We’ll get to that contradiction later.

TL;DR: AI made the coding part of software fast, and that speed didn’t create chaos so much as expose where your organization was already slow: the hand-offs between teams. The fix isn’t a better tool, it’s better wiring. We rewired Dev and Ops once already and called it DevOps. The next wall, between business and engineering, is coming down the same way. Here’s how to see it, and one thing you can do tomorrow.

AI is the rubber duck that pushes back

Note| In AI
| 4 minute read

Last month I sat down with Cris Roata to record an episode of her podcast, Catching More Green Lights in Life. It went live today! Cris asked me what I tell people who are afraid of AI, and I gave the answer I usually give: treat it like an intern, train it patiently, expect the first attempts to be…

Welcome Claude, my Chief of Staff

| In AI
| 28 minute read

Most people use AI like a search engine with extra steps. Ask a question, get an answer, move on. I did too, until I accidentally stumbled into something completely different.

Over the week, I’ve turned Claude into my personal Chief of Staff. What’s a Chief of Staff, you might ask? Think of these people who follow executives around, whispering important things into their ear, and making sure nothing falls through the cracks.

If you’ve watched The Fifth Element (go watch it, if you haven’t, it’s a great movie!), you know the scene: the president’s aide leans in and whispers something absurdly specific like “You have 19 more meetings after this one.” That’s essentially what Claude does for me now. Except I’m not a president. And thankfully, I have less meetings. I’m a freelance consultant living near a forest in Bavaria.

This post is a bit of a recap: how it happened, what the system actually looks like, three lessons I learned along the way, and, at the end, an unedited interview where I asked Claude seven questions about what it’s like to be my Chief of Staff, with some interesting insights. Don’t miss it!

Video: What I actually do with AI every day

| In AI
| 2 minute read

Here’s a video I just uploaded to YouTube, walking through 7+1 examples of how AI has woven itself into my daily life — from the mundane to the surprisingly useful. No demos, no hypotheticals, rather what an actual week with AI looks like for me.

How to stop engineering prompts and start delegating

| In AI
| 18 minute read

TL;DR: The best “prompt engineering” technique isn’t engineering at all—it’s delegation. Transfer intent, not instructions. For quick tasks, tell the AI what success looks like and why (the Intent Prompt). For complex work, equip it with context, deliverables, and decision principles so it can navigate on its own (the Delegation Brief). You already have these skills. This post helps you apply them to AI.

From scarce code to abundant builders

| In Career & Growth
| 7 minute read

According to media pundits, software stocks are “crashing”, and there’s a “SaaSpocalypse” going on. Recently, Noah Smith wrote about “The Fall of the Nerds,” painting a picture of software engineers as the new master weavers: skilled artisans about to be displaced by AI-powered looms. Meanwhile, I’m…

We’re still living in the cat pictures era of AI

| In AI
| 7 minute read

Most people use AI the way our parents used the Internet in 1995. They’d dial up their modem, check the weather forecast on Yahoo, maybe look up a recipe, and call it a day. The idea that this same technology would eventually let them video call their grandchildren, run a business, or access humani…

On constrained serendipity, learning by doing, and whether the system is the art. I’m chatting with Claude, kicking around ideas on building a tool that generates AI images, but without the prompting. I like to start these chats by brain-dumping ideas into it. In this case it’s about auto-generating…

Invite your heroes into your AI conversations

| In AI
| 7 minute read

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 while ago, I mentioned an executive who admitted they didn’t use AI tools themselves. In Admit You Don’t Know: Reverse Mentorship With An AI Sherpa, Jeremy Utley recently blogged about a similar observation, but turns it around by challenging leaders to admit they don’t know, then to do something about it.

His core insight is powerful: “Most leaders think credibility comes from always having the answer. In the AI era, it’s the opposite. Credibility comes from admitting you don’t know—and doing something about it.”

Acknowledging that execs and other senior people might struggle with justifying the time to spend learning, he offers two solutions:

  1. Find a junior mentor who is fluent in AI, and let them teach them. He calls it “reverse mentorship”, but I disagree on the “reverse” part: a mentor is someone who shares experience they have with a mentee who lacks that experience. The concepts of “junior” or “senior” are related to experience, not age. Just because a mentor is less senior in one dimension (like tenure, age, or business experience), doesn’t mean they may not be senior in another dimension (like AI experience).

  2. An “AI Sherpa”, an AI-experienced co-worker acting as a shadow who analyzes the day-to-day work of an executive, then builds custom AI experiences (i.e., with ChatGPT’s “Custom GPTs” feature or Claude’s artifacts), tailored to the exec’s workflow and specific needs.

What makes Jeremy’s approach particularly compelling is a real example he shares: Don from PCCP, LLC publicly asked for an AI mentor at a company conference, saying “I raised my hand and asked for a mentor, even though I run the firm.” When Don shared his positive experience the following week, several other senior leaders immediately stood up asking for AI mentors on the spot. One act of leadership humility sparked a movement. I wish the exec I observed had the humility to do something about their lack of AI experience!

I’m still not a fan of shortcuts, and the concept of an AI Sherpa sounds like an excuse for not doing the learning. But Jeremy positions it cleverly as making transformation “irrefusible” for resistant leaders—if they refuse world-class AI mentorship designed specifically for them, that reveals something about their commitment to change. It’s certainly better than doing nothing, and it removes the typical barriers that prevent executives from getting started.

The bottom line remains: you can’t require what you won’t do. And in the AI era, admitting “I don’t know” might be the most credible thing a leader can say.

Seth Godin on Udemy: Thriving in an AI future

Link| In AI
| 1 minute read

Just finishing this course by Seth Godin on Udemy, and it’s great!

Udemy: Thriving in an AI future

The best insights on AI don’t come from the technologists. They tend to be too deep inside the matter, often missing the human connection, the creativity angle, or the bigger picture.

And that’s exactly what you’ll get from this course.

Fun fact: Seth Godin used to work with SF authors like Isaac Asimov, Arthur C. Clarke and Ray Bradbury, building interactive computer games and early digital media projects in the 80s. He says he’s basically preparing himself for the advent of AI for decades, so he has some good insights here.

Disclosure: I got access to the course for free as part of a different project Seth is working on (more on that, later). I do think the price of € 69,99 (or whatever it is in your local currency) is worth it.

Any opportunity to learn from people like Seth Godin is priceless. Don’t miss the final Q&A sections, they contain lost of nuggets of wisdom!

Update (2025-09-19): Changed the generic post picture to a screenshot of Seth Godin from his course.

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!

I don’t use AI. I work with it.

Link| In AI
| 1 minute read

Great intro to the “why” and “how” of using AI in your everyday life by Stanford adjunct professor Jeremy Utley. His background is design, not tech, and thus, he has a very different, human-centric view on AI, which I find refreshing.

Using Claude to create a playlist for Exploding Kittens

Note| In Life
| 1 minute read

What happened was that last weekend, my family and I played Exploding Kittens: Good vs. Evil, which we were recently gifted. What a fun game! A random idea struck me: why not ask Claude to put together a playlist for us?

Hi Claude, we‘re about to play a few rounds of Exploding Kittens (“Good vs. Ev…

This time I coded it myself: using AI as a teacher

Note| In AI
| 7 minute read

If you’re a returning visitor, you might notice the header image on this blog looks more sharp and crisp—that’s because it is! ✨ After creating my own URL shortener, I wanted to modernize my header image. I built it back then in 2022 using p5.js, but the resolution wasn’t great. Now I wanted a more …

From Pelican to Zola: Refactoring my blog

| In Blogging
| 2 minute read

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…