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.

I've been enjoying using Jest to run my tests, using the workflow where it re-runs the files on any change. I wonder if it has the fuzzing/synthesis problem of running bad code though? I worry about writing `delete(".")` and it not waiting for me to finish `delete("./cache")`.

I've seen computer games that give you gameplay tips on loading screens. Perhaps compilers could do same thing? Whilst you're waiting for the compile to complete, you could say "now in version X, new syntax Y!"