miniblog.

Implementation chicken: When there's an obvious feature gap in an ecosystem and everyone is waiting for someone else to write it. I see this most frequently with OSS toolchains. Basic functionality in new programming languages is another common scenario.

Should code completion offer private methods/fields? If the user chooses a private method, you can offer a quickfix to change its visibility. It's clutter though. I frequently find myself wanting fields that I haven't exposed yet, and frustrated that the IDE hides them.

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.