fwee

Hi HN! I built Canban (https://canban.dev) so I could manage human context on a Kanban board. If you've try vibe coding, you know how exhausting switching across terminals gets.

My workflow: I discuss the feature with an agent on a card, then I drag the card into develop, the card follows a github-action-like workflow to automatically dispatch agents in a Git worktree and land changes through a local merge queue, with all feature context and progress tracked on the kanban board. Under the hood it pairs `libghostty-vt` with `herdr-core`, so it runs and detects most mainstream agent CLIs.

Tech stack:

- Rust

- longbridge/nsh for macOS UI

- libghostty-vt for terminal

- herdr-core for agents

Indeed, making an engine is a guaranteed reward. You put in time, make an engine that can draw something, and you succeed, receiving a dopamine reward. But making a game is really risky; a programmer may put in a lot of time and hope, then still fail. I think lots of programmers don't want to take the risk of failure.

Thanks for correcting. Compared to the original, the documentation is just replaced with some keywords. It needs more works to do to make it a useful tutorial.

Rails is not for API,why not use eventmachine?

Should we learn some 'new' and 'fast' language, then code slow service?