The artifact as a mark of craft, not a shame report

Why a shared Faultmap should make a builder look good, and how we designed it that way.

Balagei G Nagarajan3 min read

A report that lists everything wrong with your work is a thing you hide. We did not want to build that.

Designed to be Shared

A Faultmap is meant to be shared. An agency attaches it to a proposal. A builder drops it in a pull request. An automation lead walks into a review with it. In every case it makes the person look more careful, not less.

Craft is Contagious

So we designed it as a clean, readable artifact with one link, not a wall of findings. The breaks are named plainly, the fixes are concrete, and the test suite is ready to run. It reads like the work of someone who checked before they built.

Craft is contagious. When the careful version is also the shareable version, more people choose it.


Share

Join the discussion

Have a take, a war story, or a question? Sign in with GitHub to comment and react. Comments are powered by GitHub Discussions, ad-free and yours to moderate.

Continue Reading

Every article here documents a failure mode we've seen in production. Faultmap finds them before you ship.