"Back pressure" is already a term widely used in computing for something entirely different: https://schmidscience.com/what-does-back-pressure-in-compute...

With Visual Studio and Copilot I like the fact that runs a comment and then can read the output back and then automatically continues based on the error message let's say there's a compilation error or a failed test case, It reads it and then feeds that back into the system automatically. Once the plan is satisfied, it marks it as completed

This use of the term “back pressure” is pretty confusing in a computer science context.

This jumps to proof assistants and barely mentions fuzzing. I've found that with a bit of guidance, Claude is pretty good at suggesting interesting properties to test and writing property tests to verify that invariants hold.

Beyond Linting and Shell Exec (gh, Playwright etc), what other additional tools did you find useful for your tasks, HN?!

Most of my feedback that can be automated is done either by this or by fuzzing. Would love to hear about other optimisations y'all have found.

I thought you are talking about back pressure pipes in my housing complex.

I’ve been wondering why I can’t use it to generate electricity.

Others have pointed out the incongruity of back pressure here, I would have loved “feedback”.