daodaobing — indie developer

I build tools.
I write about them.

Indie developer. I ship small, sharp software from a quiet corner of the internet — and explain how I built it.

← say hi

An indie dev
beside you.

I work alone, in public, on tools I want to use myself — and write about the parts I find hard so others don't have to relearn them.

RSS-first

Everything I publish has a feed. No tracking, no algorithm.

OSS maintainer

I keep small libraries running. Issues welcome.

Side projects

One shipped per quarter. Each one is small and finished.

Writing

Long-form notes on what I learned, posted on my site.

Talks

A few per year, mostly at small meetups and conferences.

Mentoring

Light office hours once a month. Email to book.

Ask without opening a chat.

Most of my work this quarter is on Nomi — a focused tool I'm building in the open from Hangzhou. The interesting part isn't the code; it's figuring out what to leave out.

Small surface, sharp defaults, no configuration knobs. The kind of tool I want to use myself, and write about as I go.

Nomi

A small, focused tool I'm building in the open. Sharp defaults, no configuration knobs, the kind I want to use myself.

In progress · Indie hacking

See what I'm working on →
Screenshot of Nomi ← newest
Screenshot of Project 2

Project 2

A weekend project that turned into Y. It runs on a Raspberry Pi in my closet.

Self-hosted · Go

See the source →

Project 3

A long-running experiment in Z. I keep rewriting the same parser and learning the same lesson.

Rust · Open source

Browse the repo →
Screenshot of Project 3
public
github.com/daodaobing

I work in the open.

Every project I build is on GitHub. Every decision is in a public repo — the bad ones, the false starts, the cut features. If you're hiring or collaborating, you'll see how I think before we talk.

See my GitHub →
"His code reads like documentation." — A teammate "He ships things other people talk about." — A collaborator "He answered my GitHub issue in 4 hours." — An OSS user "Best tech writing I've read this year." — A reader "He turned down a meeting to fix a typo. Legend." — A friend "Working with him is unreasonably calm." — A client
"His code reads like documentation." — A teammate "He ships things other people talk about." — A collaborator "He answered my GitHub issue in 4 hours." — An OSS user "Best tech writing I've read this year." — A reader "He turned down a meeting to fix a typo. Legend." — A friend "Working with him is unreasonably calm." — A client
daodaobing

Available for collab

Currently open to: small freelance builds, OSS contributions, the occasional talk.

Ask & answered

Are you available for freelance?

Yes, ~1 slot per quarter.

What stack do you use?

Whatever fits. TS, Go, Rust, Python. I pick, not fight.

Do you do consulting?

Hourly yes; retainer no.

Where are you based?

Remote, Beijing (UTC+8).

Do you speak at conferences?

Occasionally. Invite me.

How do you price side projects?

Free if it's for me. Paid if it's for you.

Can I use your code?

Yes, MIT/Apache 2.0 unless noted.

Do you mentor?

Lightly. Office hours once a month, link in footer.

remote · indie · open to work

Let's build something.

One email is all it takes. I read everything.