Yak Shaving is: doing seemingly-unrelated tasks to get some real task done.
The name has obscure roots and doesn’t matter; the key is that it makes you think, “Why would you do that?”
How do you start a new project? Perhaps you start with an empty project and copy/paste relevant content. Or maybe you start…
(This post describes the first yak category. You might choose to start with the Taxonomy of Yak Shaving intro.)
(This post continues from the Royal Yak, and concludes the series A Taxonomy of Yaks.)
When we improve how we work, we make tasks faster. We make progress smoother. This is magnified when we improve how all our team members work, or our whole community. Now and then, though…
(continued from Attack Yak; series begins with Taxonomy of Yak Shaving) Sometimes you’re coding along, writing tests as little experiments “this should fail because I haven’t implemented the parser for it yet” — and it fails in a way you didn’t expect. And then you start digging and the parsing…
(continued from Imperial Yaks; part of A Taxonomy of Yak Shaving series)
(continued from Trim Yaks; part of the Taxonomy of Yak Shaving series)
When you learn to code, you acquire a superpower: automation. We turn the computer into a machine to do our (very specific) bidding. We get paid to automate what other people want. We can and should use this superpower for ourselves too!
Collaboration is hard. There are the essential difficulties of dealing with people, and then there are incidental challenges in the tools we use. Communicating with people, while clicking into to Travis to see the build…