We wrote down how Bodongday works
Build small, fix often, and ask our users directly.
"So how do you actually work?" We have been asked this a few times, and the answer came out a little differently each time — so we wrote it down.
In four lines
- find what we want to use every day
- build it small
- use it ourselves first
- fix it beside our users
Then repeat. Getting through one full loop quickly mattered more than keeping the order.
Build it small
We do not start by filling in a feature list. Harudamda started from "three lines", Kkadak from a single question: "why did this go up today?" Everything else was added while we used it.
Use it ourselves first
If we do not reach for it every day, it does not ship. A feature its own makers stop opening is usually one our users stop opening too.
Fix it beside our users
Messages go straight to the person who built the thing, with nobody in between. It keeps a one-day fix from turning into a two-week meeting.
So this is the company
We work a 4.5-day week, remote work is each person's call, and the company provides the equipment. More than years of experience, we want to work with people who keep asking "why was this built this way?"