synthetic data · no client screens
Reconstruction with synthetic data · no client screens
Alongside the big builds I made small utilities: a single-file JSON Explorer for mapping data paths, and process maps for accounts payable.
Small, repeated guesswork was slowing every build.
Make tiny tools that remove the guesswork instead of documenting it.
A JSON Explorer and process maps the whole team uses.
Click through the four steps. In step 3, click any box to see what it does.
Have a similar mess? Tell me the step you hate.