Tooling

The tooling beat is where Stack Quarterly’s recurring landscape pieces live. Each issue tries to ship at least one tooling piece — either a survey of what working teams are using (the “twelve frontier teams” pieces), a focused recommendation list (the “eight open-source tools” pieces), or a deep practitioner read on a specific library or framework.

We do not run tooling-by-the-numbers. We do not publish percentages we cannot reproduce. Tooling coverage on this site is qualitative when the numbers do not exist, and specific about the version and the use case when we do recommend a tool. We do not recommend tools we have not personally run or seen a working practitioner run in front of us.

If you are a tool author and you think we are wrong about a recommendation, corrections@ is the right address. Vendor PR pitches for tooling coverage are not effective; the right path to coverage is “get the tool into the hands of working practitioners and let the writeups follow.”