Keep Going Till It's Fun

There's no real answer, obviously. With templ (not the famous one) I added the few features I really wanted (git integration, piping from the tool back into itself, the ability to list what variables I should define) and it was obviously done at that point. Andrew's unfinished, though, and while it works I don't really want to tackle the next two Big Features because they seem hard.

Honestly, though, when I actually write a post here, Andrew's fun to use. I love that I'm writing HTML, not markdown or some other intermediary form. It's a simple thing, but I adore it.

So why should I add more features? In my heart, I know Andrew can be more fun to use.

I've always seen PlayTechnique, my budding little contracting biz, as a place for me to follow whimsy and have fun, not as a Serious Venture. The thing that exhausts me at $DAYJOB is how tiresome it is coordinating work to help improve the company. I love the work, I love the outcome, but gosh darn is it exhausting getting the projects right.

The name PlayTechnique is literally about the idea that skills are fun to develop, and Play could be considered a skill, just like handstands or parkour or lifting weights or writing stories. Improving my technique at my skills makes them more rewarding, more enjoyable, more fun. Improving my technique at Play should be the same way; the more Play Techniques I have, the more fun it is to Play.

So how long should I be adding features for? Until Andrew is fun to use, that's how long.

How long should you add new features to a github workflow? Until your chore is gone and now you're having fun in your project.

How many tools does your Kubernetes cluster need? All of the ones that make it fun and enjoyable, and no more.

If there's one manifesto I should write for PlayTechnique