Developer Tools

Developer tools are the category where the audience is also the builder, which makes it both the easiest place to launch and the hardest place to impress. Everyone reading has strong opinions about their editor, their shell, and how their tests should run. The tools that land are usually the ones that remove a specific, recurring irritation rather than proposing a new way to work.

The launches gathered here cover the full arc of building software: environment setup, editors and extensions, linting and type checking, testing and CI, deployment and preview environments, observability, and the long tail of small utilities that quietly save an hour a week. Some are single binaries you drop on your path. Others are hosted platforms with a free tier. A significant number are open source, and for those the repository tells you more than the landing page — commit frequency, issue response times, and whether the maintainer answers questions kindly are all better predictors of whether a tool will still be around next year than any feature comparison.

The recurring tension in this category is between tools that meet you where you are and tools that ask you to move. A linter that reads your existing configuration and improves on it will be adopted. A linter that requires rewriting every config file will be starred and forgotten. The same applies to CI: pipelines that drop into an existing setup get tried, while platforms that require migrating everything get bookmarked for a quieter month that never arrives. When you are evaluating something here, the honest question is not whether it is better, but whether it is better by enough to justify the switching cost.

Local-first has become a genuine movement in this category rather than a marketing line. Tools that run entirely on your machine — no account, no telemetry, no network round trip — are increasingly the default expectation for anything touching source code. This is partly privacy and partly latency: a review that takes four seconds on your laptop beats one that takes forty in a queue. It is also partly about longevity. A binary you have downloaded keeps working after the company behind it is acquired.

Pricing tends to follow a familiar shape: free for individuals, paid per seat for teams, with the interesting decisions hidden in what counts as a seat and whether CI runners count as users. Read that part carefully. The tools that get recommended repeatedly are usually the ones with pricing that stays sane as a team grows from three people to thirty.

For makers launching here, this audience rewards specificity and punishes vagueness harder than any other. Show the command. Show the output. Show the diff. A twenty-second terminal recording will do more than a page of copy, and a link to the source will do more than either. The fastest way to lose this crowd is to describe a developer tool entirely in the language of business outcomes.