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.

> If you work on PLs long enough, you will develop a finely honed skill at creating bizarre programs like this that are technically valid but likely to trip up an implementation written by someone with a less perverse imagination than you.

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.