The modern makers’ machine does not want you to create heavy things. It runs on the internet—powered by social media, fueled by mass appeal, and addicted to speed. It thrives on spikes, scrolls, and screenshots. It resists weight and avoids friction. It does not care for patience, deliberation, or anything but production. It doesn’t care what you create, only that you keep creating. Make more. Make faster. Make lighter. Make something that can be consumed in a breath and discarded just as quickly. Heavy things take time. And here, time is a tax.

even the most successful Substackers—those who’ve turned newsletters into brands and businesses—eventually want to stop stacking things. They want to make one really, really good thing. One truly heavy thing. A book. A manifesto. A movie. A media company. A momument.

At any given time, you’re either pre–heavy thing or post–heavy thing. You’ve either made something weighty already, or you haven’t. Pre–heavy thing people are still searching, experimenting, iterating. Post–heavy thing people have crossed the threshold. They’ve made something substantial—something that commands respect, inspires others, and becomes a foundation to build on. And it shows. They move with confidence and calm. (But this feeling doesn’t always last forever.)

No one wants to stay in light mode forever. Sooner or later, everyone gravitates toward heavy mode—toward making something with weight. Your life’s work will be heavy. Finding the balance of light and heavy is the game.4 Note: heavy doesn’t have to mean “big.” Heavy can be small, niche, hard to scale. What I’m talking about is more like density. It’s about what is defining, meaningful, durable.

Telling everyone they’re a creator has only fostered a new strain of imposter syndrome. Being called a creator doesn’t make you one or make you feel like one; creating something with weight does. When you’ve made something heavy—something that stands on its own—you don’t need validation. You just know, because you feel its weight in your hands.

It’s not that most people can’t make heavy things. It’s that they don’t notice they aren’t. Lightness has its virtues—it pulls us in, subtly, innocently, whispering, 'Just do things.' The machine rewards movement, so we keep going, collecting badges. One day, we look up and realize we’ve been running in place.

Why does it feel bad to stop posting after weeks of consistency? Because the force of your work instantly drops to zero. It was all motion, no mass—momentum without weight. 99% dopamine, near-zero serotonin, and no trace of oxytocin. This is the contemporary creator’s dilemma—the contemporary generation’s dilemma.

We spend our lives crafting weighted blankets for ourselves—something heavy enough to anchor our ambition and quiet our minds.

Online, by nature, weight is harder to find, harder to hold on to, and only getting harder in a world where it feels like anyone can make anything.

I've noticed that most devs, anyway, are either front-loaded or back-loaded."Front-loaded" means that the part of a project they really enjoy is the beginning part, design work, etc. Once those problems are largely worked out, the project becomes less interesting to them. A common refrain from this personality is "the rest is just implementation details"."Back-loaded" is the opposite of that. They hate the initial work of a project and prefer to do the implementation details, after the road is mapped out.Both sorts of devs are critical. Could it be that you're a front-loaded sort? If so, maybe the thing to do is to bring in someone who's back-loaded and work on the projects together?

Even if it's just a personal project, think about the time and money you'll need to invest, and the benefits and value it will provide. Think on why you should prioritize this over other tasks or existing projects. Most importantly, sleep on it. Get away from it and do something else. Spend at least a couple of days on and off planning it. Outline and prioritize features and tasks. Decide on the most important ones and define the MVP. If, after this planning process, you still feel motivated to pursue the project, go ahead!

Quick win is to ask yourself: What have I learned from this project? And make that the result of the project.

Find a job/role/gig where you think of the solutions and let other people implement them. Just always remember that it is no longer your project. You might have thought of something, but without the efforts of others it will never amount to anything, ever. So as long as you can respect the work of others and your own limitations in doing what they do you will do fine.

Find more challenging problems. I usually do this by trying to expand something that spiked my interest to make it more generically applicable or asking myself if the problem is actually worth a solution ('faster horses') and if the underlying problem is not more interesting (mobility).

it helps to promise other people something: Present your findings, write a paper, make a POC by an agreed upon deadline. Now you have to be empatic enough to want to meet their deadline and thus create what you promised with all the works that comes with it. That is your result. You also have to be selfish enough to tell people that is where you end your involvement, because it no longer interests you, regardless of the plans they have pursuing this further