When someone says "you should use the cloud", I'm never sure if they mean:
1: use a virtual server rather than running your own hardware, or
2: use hosted services rather than running your own e.g. database
2 is often surprisingly expensive IME.
miniblog.
Related Posts
I've had good results by prompting an LLM "review your changes" in the same session when I don't like the initial output.
I'm surprised this is effective: I would think it's redundant when you're running with a high effort setting.
I frequently find myself running:
$ slowish
$ slowish | jq
$ slowish | jq | grep
I feel there must be a better way to build up pipelines incrementally without re-running.
I could save each output to a file, but it's more verbose, and most of these tools have nicer output when stdout is a TTY.
Has anyone built a great solution to 'run all my unit tests automatically'?
It's straightforward to write a while loop in bash, but handling timeouts, syntax errors etc well is hard.
Running on save would be good, although I wonder if you could run fast tests on each keystroke.