Verstreuen [ver-ˈstrɔɪ̯-ən]

verb (German)

1. to scatter; to spread widely.

2. (versehentlich) to spill, often by accident.

Verstreuen is my weekly ritual - revisiting notes to find the ideas worth carrying into next week.

_{Forwarded this email? Subscribe here for more}

🗃️ This Week’s Highlights

This week's notes come from 23 new additions to the Zettelkasten - here’s the three that stood out most to share with you:

🟨 Your ideas don’t suck - you’re just waiting to edit

🟦 Building is no longer a differentiator

🟥 You might be optimizing yourself into a corner

I used to treat editing as cleanup. Make the thing, then fix it. Creation first, improvement second.

That order makes sense if you already know what you’re making. But more often than not, I don't. The process of creating reveals new, more interesting, paths I couldn't have seen before I started.

The first version is an answer to a question. What happens if I say it this way? The draft doesn't fall short of the idea - it's how the idea takes shape.

Every mark changes what comes next. The next stroke is only possible because of the last one. A painting isn't hidden somewhere, waiting to be uncovered - it emerges out of a back-and-forth between the artist and the canvas.

Each act provides new information there's no moment where the fog lifts and its finally finished. There's only a series of versions, each one changing little by little inching towards the vision.

The final version isn't where I finally discover what the thing was supposed to be. It's where I stop asking questions.

Because editing isn't a stage of creation. It is creation.

📎 Takeaway: The draft isn't a flawed copy of an idea. It's how you find out what the idea is.

—🗃️—

When making becomes cheap and accessible, the advantage no longer comes from simply being able to make something.

I spent years learning React but now I can create applications using frameworks I've never touched before. I can describe what I want, and an agent can generate the code, the interface, and the infrastructure needed to turn that idea into a working application.

The distance between an idea and working prototype is nearly zero.

The code was never the moat - It only looked like one because, for decades, so few people could produce it. The scarcity of execution made it feel like the advantage.

Photography has an interesting parallel here - when phones began producing technically excellent images automatically, the technical skill of operating a camera became less important as a differentiator. and yet the world didn't fill with better photographs. It simply filled with more of them.

What separated a photograph worth keeping from ten thousand identical sunsets was never the exposure. It was the eye behind it - knowing where to point the camera, knowing when not to take the shot, and knowing what moment actually mattered.

The tool removed friction from the process, but it didn't remove the need for judgment.

Vibe coding creates the same shift for software. The ability to build the obvious idea is no longer the advantage when everyone can build it. The question moves earlier in the process: which ideas are worth pursuing in the first place.

And this is where being extreme matters. When the cost of creation falls, the safest ideas become the easiest ones to replicate. The advantage moves toward the people willing to follow their own taste far enough to create something that couldn't have come from anyone else.

📎 Takeaway: When the cost of building goes to zero, the skill is no longer execution. It is unusual conviction about what to build.

—🗃️—

I tend to think a little too logically for my own good. The right move feels like the one that makes things better right now. Take the step that goes up, get to the top.

But this approach doesn’t tell me if the top is a mountain, or just a hill.

Simulated annealing is an interesting approach that challenges this instinct. It suggests that the path to a better solution isn’t strictly uphill. Early in the process, the system is given permission to move away - sometimes drastically - from what looks like the best option, because staying there might mean never discovering something better.

In other words, the system is allowed to get worse before it gets better.
That part is easy to understand conceptually and uncomfortable to apply.

Because in practice, moving away from a defined path feels like a mistake.

The better option is clearer. It’s measurable. It comes with immediate feedback. Exploration is difficult, less certain, less efficient, and harder to justify in the moment.

But the ease of measuring progress can hide the fact that you’re measuring the wrong thing.

Climbing faster doesn’t matter much if you’re on the wrong hill.

And the only way to learn that is by being willing to leave.

📎 Takeaway: The best position is rarely reached by always taking the best next step. Sometimes the only way up is through a deliberate jump.

—🗃️—

Closing Thoughts

Making is how you think.

The work isn’t doing more - it’s starting sooner, choosing with conviction, and being willing to leave when something no longer takes you where you need to go.

Where you aim matters more than how fast you get there.

Most weeks aren’t about finding new ideas - they’re about recognizing which ones are worth keeping.

Until next week
-GH

Thanks for reading Verstreuen! 👋