Engineering

Numbers

What is measured

Bundle weight, from the production build output of each app. These are real, reproducible by running npm run build in the repo, and they are gzipped transfer sizes.

AppHTMLCSSJSTotal gzipped
ADR1.2 kB3.5 kB75.4 kBabout 80 kB
Premortem1.2 kB3.7 kB74.8 kBabout 80 kB
OKR1.2 kB3.7 kB75.7 kBabout 81 kB
Journey1.1 kB3.5 kB76.4 kBabout 81 kB
Persona1.2 kB3.7 kB75.4 kBabout 80 kB
SQLpad1.2 kB3.8 kB75.8 kBabout 81 kB, plus a 41 kB worker chunk
AB1.2 kB3.4 kB76.0 kBabout 81 kB
Bayes1.2 kB3.6 kB73.2 kBabout 78 kB
Rubric1.2 kB3.7 kB76.3 kBabout 81 kB
Skillfile1.2 kB3.3 kB75.8 kBabout 80 kB

Three same-origin requests each, plus the Google Fonts stylesheet and its font files. About 73 kB of the JS in every one of them is React and React DOM; the app itself is the remaining few kilobytes, which is worth knowing before anyone congratulates me on the totals.

SQLpad is the exception worth calling out: its 658 kB WebAssembly file is fetched lazily when the first table loads, not on page load, so the first paint does not pay for it.

What is not measured

Not written yet, waiting on N-1

Lighthouse scores for every surface. I have not run Lighthouse. The house rule is that this environment does not spin up headless browser tooling to check pages, so the numbers have to come from a real run on a real device, and they have not been taken yet.

Checked 2026-09-21.

Putting a green 100 on this page without having run the audit would be the single easiest thing on this whole site to fake and the single easiest thing to catch, which is a good reason not to start.

What a real measurement will have to say

  1. Which device and connection profile. A desktop score and a mid-range phone on 4G are different claims.
  2. The date, and the deployed commit.
  3. All four categories, including the one that scored worst.
  4. Whether the run was against production or a local preview.

The repos

The ten apps above are all in the bryancalabro GitHub org with their tests visible:

V-3 recorded

Source control is GitHub, in the bryancalabro org. calabrodesign and its sibling repos live there, and pull requests and Actions run against it. Data held: repo contents, commit history, Actions logs.

Source: the calabrodesign git remote and .github/workflows/. Last verified 2026-09-21.

Each one runs lint, the contrast check, its tests and the build on every pull request.