I’m sorry. And to show how much I regret my choice, I will right this wrong.
I have been described in an interview as a software unit testing zealot. But this former zealot has lost his way. So here he is, ready to rededicate himself to the church of test driven development.
This is the first test - trial by fire. We begin anew, (
$ git rm . -r && rm * -r), look for survivors, (
$ ls -all) and commit ourselves to our quest to write quality code (
$ git commit -m "Delete all untested code").
And from the ashes the phoenix rises.
Explain what you do and why you do it. When you do, you’ll understand it better yourself. There’s a very real possibility that you’re the only one who’ll ever read it anyway…
With rampant attention span poverty, spare a thought for those who cannot afford to read the long post.
Make a commitment as to how regularly we’ll do this. Let’s say two weeks. One little step in this tutorial every two weeks, surely that is feasible, right? Don’t nitpick! We can’t wait forever to release something because it has to be “just right.”
If you can get others excited in what you want to do, all the better. Present some session to those who are interested. Make it about two hours long, for those who have the stamina.
We reference our sources. We always reference our sources. When we reference our sources we don’t seem clever. We acknowledge those whose work we built off of and we aid the astute reader to learn more about something that interested them.