Val March

I build software the way I keep a private journal, without an audience in mind, without performance. Because the work either holds up or it doesn't.

I design, build, and ship products from a single desk; no team, no committee, no distance between the decision and the code. That closeness is not a limitation. It's the whole point.

The software I build has one test: does it get out of the user's way? Not "is it impressive?" Not "does it scale to a million users?" Just: does it do what the person came to do, without asking anything unnecessary in return? If yes, it ships. If not, it doesn't.

If something here resonates, reach out.