45 points | by ghuntley 2 days ago
9 comments
"Back pressure" is already a term widely used in computing for something entirely different: https://schmidscience.com/what-does-back-pressure-in-compute...
I have the same argument with “crypto”
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.
If you give Claude examples of good and bad property tests, and explain why, it gets much better than it was out of the box.
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.
Teaching them skills for running API and e2e tests and how to filter those tests so it can check if what it did works quickly.
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”.
"Back pressure" is already a term widely used in computing for something entirely different: https://schmidscience.com/what-does-back-pressure-in-compute...
I have the same argument with “crypto”
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.
If you give Claude examples of good and bad property tests, and explain why, it gets much better than it was out of the box.
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.
Teaching them skills for running API and e2e tests and how to filter those tests so it can check if what it did works quickly.
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”.