Stickman Charles — Scratch Your Own Itch

2026/8/4 GMT-4

Hello, I'm Stickman Charles.

While reading Rework, one piece of advice stayed with me more than anything else:

Scratch your own itch.

The Curse of Sunk Costs

I'd known for a long time that startups create value by solving real problems. But knowing something and acting on it are rarely the same.

When I first started building EchoForge's EchoFamily product line—EchoCert, EchoUploader, EchoDash, and EchoID—I believed each product was solving a real problem.

Looking back, I'm not so sure.

Very few people actually need on-chain certificates, so EchoCert attracted almost no users.

Very few people need upload proofs without institutional authority behind them, so almost nobody used EchoUploader.

EchoDash and EchoID depended on those two products, so naturally, there wasn't much demand for them either.

Ironically, these components together were originally meant to become the foundation of EchoForgeDAO. (You can read more about that journey here: https://stickmancharles.com/journal/from-storyforgedao-to-echoforge.)

But I worried that launching a platform from scratch would be too difficult, so I split the idea into several smaller products instead, thinking that would reduce the barrier while giving me a chance to improve my engineering skills.

That part was true.

During that period I learned MeshSDK, Lucid Evolution, and many practical software engineering techniques.

But whenever someone asked whether these products were solving meaningful problems, I became uneasy.

Deep down, I didn't want to think about the answer.

Admitting it felt like admitting that all the work I'd already invested had been wasted.

Scratch Your Own Itch

Everything changed after a Cardano network upgrade.

I didn't notice the changes in time, and my services stopped working.

It eventually turned out to be a false alarm—the real issue was somewhere else—but the experience reminded me of the advice from Rework:

Scratch your own itch.

As a solo builder who isn't working full-time, my time is limited.

Besides building software, I study math and physics, read books, exercise, and write articles. I simply don't have the attention to constantly monitor changes across the Cardano tooling ecosystem.

So I thought:

What if there were a web app that monitored the major Cardano technology stacks for me?

It could save not only my own attention, but eventually other developers' as well.

The product came together quickly.

I called it EchoWatch.

Like my previous projects, I shared it in the communities I was already part of, without expecting much.

If it solved my own problem, I figured that was already enough.

Then, two days ago, something different happened.

A founder sent me a direct message asking whether I could add Pebble to EchoWatch because it was difficult for him to keep track of updates.

Before that moment, EchoForge had almost no users.

I had never received genuine product feedback.

In fact, it was entirely possible that I was the only person actually using my own products.

That message marked something different.

For the first time, EchoWatch had a real user.

Someone was relying on it to solve a real problem.

As of today, Pebble has officially been added to EchoWatch.

But more importantly, for the first time, I felt that I had genuinely solved a real user's need.

Keep thinking, and take care.

Stickman Charles 挠自己的痒处

2026/8/4 GMT-4

你好,我是Stickman Charles

在读《Rework》的时候,让我印象最深的就是“挠自己的痒处”这个建议。

沉没成本的诅咒 虽然我早就知道“创业需要解决人们的真实需求,这样才能创造价值。” 但是知道和做到永远是两码事。在刚开始做EchoForge旗下的EchoFamily(也就是EchoCert、EchoUploader、EchoDash、EchoID)这条产品线时,每个产品都可以说是在解决一个需求,但仔细一想,似乎并不是。很少有人会需要链上证书,因此EchoCert几乎没有用户。很少有人会使用没有权威性的上传证明,EchoUploader就没人使用。EchoDash和EchoID则依附于这两个产品,自然也没有人会需要。

一方面,这几个组件加起来其实就是EchoForgeDAO的雏形(详情可见https://stickmancharles.com/journal/from-storyforgedao-to-echoforge)但是我因为担心平台冷启动,所以不假思索的就把他们几个拆成了几个小组件,认为这样就可以缓解,顺带练练手。

最后,诚实地说,练练手倒是不假,我在此期间确实掌握了MeshSDK,Lucid Evolution以及一些常见的工程方法。但是一旦被问到这些产品真的能解决需求吗,我就有点不安,也不敢细想。总觉得一旦承认这一点,之前的努力就会前功尽弃。

挠自己的痒处 直到有一次,Cardano发生链升级,而我没能及时处理。导致整个服务停摆,虽然最后发现其实是虚惊一场,问题出在别处。但是这还是让我想起Rework里说的“挠自己的痒处”。

像我这样的Solo builder,还不是全职。平时我还得学数学,学物理,读书,运动,写文章... 很少有时间真正关注自己的技术栈是否有变动。我就想着,如果能做一个专门监控 Cardano 常见技术栈的 Web App,或许就可以节省一些我,以及未来users的宝贵注意力。

开发很快就完成了,我把它取名为EchoWatch。也按往常一样在自己的熟悉的几个圈子里推广了一下。本来没有抱太大期望,觉得自己能用就很好。

直到前天,一位Founder私信我,询问我能不能加上Pebble这个技术栈,因为平时很难了解到他的变更。

在此之前,EchoForge几乎没有用户,也没有收到任何反馈,甚至有可能只有我自己在使用。

但是那天,宣告着我迎来了一位真正的user,EchoWatch真正有机会向他提供帮助。

截止到现在,Pebble已经正式加入了EchoWatch的服务。

但是更重要的是,我真正解决了一次用户的真实需求。

保持思考,保重。