Comment by aabdi

well work wise its usually for adjacent tooling. It unblocks other things, but like actual prod code, i'm always a little skeptical.

For example we had this problem where we had to take in customer inputs for requests and calculate out the projected downstream TPS. This is fairly complex since we run a query parser/orchestrator.

This is expensive to write myself or to have engi's do it, but the scaling algorithms are all there and we have excel sheets for spreading out overall costs.

so then all was needed was basically write out a big spec of the reqs - give it the docs/parser code/excel sheets, then just have it span out the pieces as a sequential checklist. 1. CI/OPS 2. docs 3. test infra 4. incremental build out in phases to chain it all together.