About the studio
Copperfinch started in 2024 as a shared folder of scripts between two system administrators who kept rewriting the same helpers on every machine. Eventually the folder became a set of proper projects, and the projects became this site.
We work remotely and asynchronously. There is no office, no roadmap meetings and no funding. Tools get written when we need them, polished when others start using them, and archived when neither is true anymore.
Principles
- One program, one job. Composition over configuration.
- No network access unless the tool's entire purpose is networking.
- Plain text in, plain text out. Exit codes mean something.
- Documentation ships with the binary, not behind a login.
The name comes from a copper-colored finch that used to visit a feeder outside the window where the first version of finchlog was written. It felt like a good omen for small, persistent things.