Consumed or Creating? Rebooting Cybernetks After a Quiet Month

It’s been almost a month since my last update and I wish I could say I’ve been deep in game dev or shipping experiments. Truth is, I’ve been stuck in consumer mode.

It crept in slowly. At first, I told myself I was “researching”: studying art references, watching game dev streams, tweaking productivity systems, improving my notes. All productive things, right?

But then I noticed:
No commits.
No posts.
No levels built.
No logs shipped.

I wasn’t producing. I was consuming. And worse, I was calling it progress.

The Pull of Consumption

There’s a weird comfort in consumption. Tutorials spark ideas. Devlogs give motivation. Systems feel like control. But here’s the catch:

Consumption gives dopamine. Creation gives resistance.

Making stuff is messy. Your ideas look better in your head. Your code breaks. Your art looks off.

But that’s where the growth is. The output. The craft. The work.

The Knowledge Debt Problem

The more you consume without producing, the deeper the gap gets. A kind of knowledge debt. You know about 100 things but haven’t applied 10. It feels like you’re levelling up, but your portfolio stays the same.

That’s where I’ve been this past month and I’m tired of it.

Rebooting the System

This post is my pivot point. I’ve been occupied with client work,  helping out my wife in her businesses and helping out my kids’s school. While all of that matters, Cybernetks still needs space to breathe. Even if it’s just 30 minutes a night.

So here’s the new rule I’m going back to:

Produce first. Consume later.

Ship a post. Push some code. Build one thing. Then scroll, binge, or watch.

One Small Commitment

I’m not trying to force a massive comeback. Just a small reboot.
Today, I’m shipping this post before I scroll anything.
Tomorrow? I’ll build something even if it’s tiny.

Time to boot back up.

Catch you in the next log!