Hacker News new | ask | show | jobs
by slovenlich 5 days ago
Does not really feel accurate to how yak shaving was to me.

Yak shaving, as I experienced it - is when nothing works unless you do something else first, and something else needs it too.

I need to fix a bug, but I have to reproduce it first. I cannot reproduce it, because there is an entire other bug that prevents me from doing it. So I have to take the other route. But the other route does not work because the infrastructure is busted, and there's a problem on the server. To get the server to work, I need to contact John. But I need to do it through the ticket filing system and it is not behaving well today, so I need to find a workaround first. And after getting the ticket filing system to work I'm finding that John is not on the job today, because he took PTO. But some say Jim might help me. Jim is just some guy, he is in the other depratment, and I cannot get to him through the ticket system. And so I send an email to Jim, but Jim is not responding. And I need to find him physically in the building. So I need to know where his desk is. And there's an entire other system to find where Jim's desk is and I don't have the authorization to use it. So apply for the authorization and wait a bit. And then I learn where Jim's desk is, and then I go there and it is empty.

2 comments

That's not yak shaving that's just how working on a complex system that has technical debt is.
This is exactly yak shaving as well.

The Urban Dictionary [1] defines it as: "Any seemingly pointless activity which is actually necessary to solve a problem which solves a problem which, several levels of recursion later, solves the real problem you're working on."

So it is a perfect fit for what you described.

[1] https://www.urbandictionary.com/define.php?term=yak+shaving