👑 The Coroniad 👑

“What I programmed on my corona holiday”

2 min readApr 19, 2020

[UPDATE: where’s the rest of the series? Relax — I have not been idle! I realized that I needed a half a dozen little tools to help me productionize tiny Python libraries easier, so I stopped and wrote them — doks, versy, simp, myers, tdir, wolk and ascript (in progress right now!) It’s probably going to take me a few more weeks to finish them all up, and then I’ll restart this series, probably under a new name as we’re sick to death, pun intended, of COVID-19.]

Suddenly everything stopped.

When the panic subsided and the thumb-twiddling was about to start, I realized that I had accumulated over the years a lot of neat little programmer’s tools, mostly in Python, each doing one small but essential thing really well.

I thought, “Let’s polish each tool shiny-bright, and push ’em out to people, once a week, until I run out. And maybe I can write an article about each one that explains not just why these tools are interesting, but the reason I wanted to do it in the first place, how I went about making it, the problems I ran into, the good parts and the bad parts.”

Why don’t more people do this? The history is all there! Git saves almost every step we make when building a piece of software, but I just never see developers showing how they build things, just the end results.

I’d be fascinated to read about how other people build software, and it’s my guess that beginner and intermediate programmers would be really interested to see how a perfectionist who has been programming for over 40 years would do it.

And so this limited series. Have fun!