Team
The people who research, build, write and check this site.
Acres Per Hour Calculator is built and kept accurate by a small team, not a single anonymous author. Every page on the site is the result of five jobs: someone researches the data, someone builds the calculator, someone writes the explanation, someone tests the result, and someone reviews it before it goes live. We publish as a named team, with a named reviewer on every page, so you know exactly who stands behind the numbers.
Sets the editorial and data standards for the site and reviews every change, the data, the formula and the page itself, before it is published. Michael is the named author and reviewer listed across the site and is accountable for everything on it. GitHub
The rest of the team
Photos for the rest of the team will be added as they become available. Until then, here is what each person actually does on this site.
Alex, Engineering
Builds and maintains the calculators and the tools behind them: the formulas, the input handling, and the interface you actually type into. When a calculator is updated or a new one is added, Alex builds it.
Jordan, Research
Researches the data and rules behind each calculator from official and primary sources: university and cooperative extension publications, government agencies, and manufacturer documentation. Where recommendations vary by region, Jordan’s research is why a page says so instead of guessing.
Chris, Content
Writes the pages that explain the data and how to use each calculator: the formula, a plain explanation, worked examples, and the questions people actually ask.
Eric, QA
Tests every tool against hand-worked examples before it is published, including edge cases such as blank, zero or invalid input, so a calculator does not just look right, it is right.
Madelynne, Corrections
Reviews reader-reported errors through our corrections process and keeps reference data current, checking each report against its original source before anything changes.
How their work shows up on the site
You can see this division of labor in practice: Jordan’s research is what you’re reading in the “Sources and further reading” section of a calculator page, Chris’s writing is the explanation and worked examples on that same page, Eric’s testing is why the calculator handles a blank or zero input without breaking, Alex’s code is the calculator itself, Michael’s review is the “Reviewed by” pill at the top, and Madelynne’s corrections process is what fixes it if any of that turns out to be wrong. The full, step-by-step version of this is in our methodology, and the testing bar each calculator has to clear is in our quality standards.