Rendered at 20:47:11 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
chaoticmass 18 minutes ago [-]
When I was in highschool I started writing a game in Qbasic. Along the way, I wanted it to have a console (like Quake) where you could enter commands and modify the game as you were running it. This lead me to create a scripting engine in Qbasic, and long story short, I’ve been on a yak shaving epic quest now for almost 30 years now. No game, but I have a hybrid C / Lua game engine/general purpose application platform. Still tinkering and still no end in sight. I’m having fun though!
monocultured 2 hours ago [-]
I was taken by Christopher Priests book The Extremes and sat down to write a blog post about what compelled me so much about it, and wanted to add some gifs to it. In particular the "deja vu" scene from The Matrix, but I couldn't find it, and I no longer have an old version of Photoshop around to create the gif myself, and three weeks (and many tokens later) I'm finishing up an xcode MacOS native app that is dedicated to generating gifs. I've still not written the blog post.
beAbU 2 hours ago [-]
Call it a pivot and away you go!
Stewart Butterfield shaved the shit out of two yaks at his video games company, which eventually became Flickr and Slack.
danielrmay 3 hours ago [-]
Yak-shaving-shaming puts limits on the creativity of talented engineers by constraining them to existing patterns and practices or building on top of abstractions, and practically, that results in engineers and teams with less breadth. In an applied software world that's exploded in framework and library complexity in recent years, I think there are always going to be yaks in dire need of a shave.
argee 2 minutes ago [-]
[delayed]
dance2die 2 minutes ago [-]
Living like Leornado Da Vinci.
thimabi 3 hours ago [-]
I always liked yak shaving, but avoided it because I knew it came with costs and tradeoffs. More recently, with the help of AI, I’ve been doing lots of it, as the costs and tradeoffs have greatly diminished. In fact, I’ve learned that building my own tools and frameworks, when done properly, comes with huge performance benefits and helps me understand the problems I’m trying to solve much more deeply. There has never been a better time for yak shaving!
mordymoop 2 hours ago [-]
Personally, I find it difficult to competently reason about a system unless I've built my own version of that system. So if you make a practice of building your own versions of things, you end up with a more robust mental library of how stuff works. For this reason, I've never seen yak shaving as a waste of time. The yak shaving was at least 50% about loading the abstractions into my brain fully.
chorizo 25 minutes ago [-]
Downside: Code is not mature; can have edge cases, bugs and security issues. Likely limited config options without hardcoding features
Upside: Only the features you actually need. Likely fewer dependencies. You know exactly what your yak looks like under the fur.
tombert 3 hours ago [-]
Tangential but it's a story that I find funny.
At a previous job, my coworkers coined the term "Thomasing" [1], referring to me, as "the act of having a question explained so thoroughly, detailed, and long-winded that the asker has lost interest in the question that they were asking".
I thought it was pretty funny, because that does basically describe me in a nutshell.
[1] Lovingly, it was a good, fairly-tight-knit group, they weren't being jerks. We all did lighthearted ribbing.
(Non short video format - https://youtu.be/AbSehcT19u0 ... When in the office I had a QR code of that so people could scan it and understand what I was working on)
jbonatakis 3 hours ago [-]
I’ll never not watch this when it’s posted
pyrolistical 18 minutes ago [-]
I’ve been yak shaving the interfaces not the implementation.
I used ai to convert c headers into in nice zig code. Then I link to the library.
It’s cheap to use zig translate-c to convert c headers but the output isn’t nice.
You can give ai c++ source which usually has more documentation than the compromised flat c header. It allows you to do a better zig port. Zig greatly cuts down the noise in c headers as everything needs to have long prefix for namespacing. But in zig we can just nest things properly.
We can introduce intermediate layers to use proper tagged unions and distinguish ?T, *T, [*]T
dan_sbl 4 hours ago [-]
This feels like what is really splitting the programming community right now- those that have typically enjoyed the journey, and those that just want to be at the destination as soon as possible.
vidarh 4 hours ago [-]
They are different things. There are projects where I deeply care about the code, and projects where I deeply care about the end result. And a whole lot in between, or that are entirely throwaway.
But I use AI also for some of the ones where I deeply care about the code, now. E.g. my terminal is in Ruby, and it worked well enough, but over the last couple of days I had Claude put together a test harness and burn down a number of sharp corners and refactor the code. It's not perfect still, but it's cleaner than it was because I didn't have time to do enough yak shaving myself. I do care about that codebase, because I have other things I want to use it for, and not having to do it all manually gave me enough time to get it to a far better state.
I feel like a lot of the split comes from people who are a whole lot less overcommitted. If you have way too many projects, you pick and choose which projects you want to lovingly care for and which ones you just want to advance the functionality of as fast as possible. Sometimes those are one and the same at different times.
Bukhmanizer 3 hours ago [-]
I’d argue most businesses have had their start through yak shaving.
I’ve found that the overuse of AI papers over a lot of problems. Then if things start failing people have no idea where or what to start fixing. I’m very much a destination person, but I’ve been on enough rides which crashed and burned to be cautious about it.
_def 3 hours ago [-]
In my experience it's not as simple and depends on a whole lot of circumstances: generally I am interested to learn and to build. Give me pressure through dysfunctional processes, understaffed teams, unrealistic standards, too strong peer opinions- etc - and I'll happily reach for the shortest path.
gavmor 3 hours ago [-]
Riding horseback saves time over walking but it's harder to smell the roses along the way. Nevertheless, millions now ride horses recreationally.
add-sub-mul-div 4 hours ago [-]
It makes me of the difference between the indie developer who labored over Stardew Valley vs. (for example) Square Enix putting out a farming sim because their committee of suits decided they wanted revenue from that genre.
pydry 4 hours ago [-]
i think what's really splitting it might actually be differing levels of slop tolerance.
jihadjihad 2 hours ago [-]
OT, but the image in TFA is not of a yak, but Highland cattle [0].
The fact that programmers can be nerd sniped into yak shaving some random libraries is the only thing that keeps Open Source running.
spelunker 4 hours ago [-]
I can do a LOT more yak shaving on personal projects now. I still haven't managed to finish anything though.
cryptonector 58 minutes ago [-]
This so much.
yakkomajuri 2 hours ago [-]
I love this. My very own static site generator, Teeny [1], is going on five years now. It's 350 lines of hand-written JS and has powered all my blogs and personal websites for years. It currently powers https://yakko.dev.
I added plugins this year which made it really powerful and allows me to keep the core small.
Markdown to html was a fun project. I wrote a tool like pandoc, with far fewer features, for school about 10 years ago.
I needed pandoc, but the internet and electricity were both out, so I built my own in a race against my dying ebay laptop battery.
oooyay 1 hours ago [-]
As in most things I think it's a mixture of quantity and set and setting.
I enjoy a yak, but right sizing my yak is pretty important to my enjoyment of it. Maybe the yak doesn't get a full shave but gets a trendy hair cut, and that's okay.
I leave my yaks at home when I go to other engineers decision meetings, project kickoffs, or RFCs.
caycep 3 hours ago [-]
Gen Z calls this "side questing" now...
wccrawford 2 hours ago [-]
I can't blame them. I instantly know what they mean when they use that phrase, but I have to think just a little bit to remember what "yak shaving" means. It's a cute name, but it's not intuitive at all. You have to learn it.
bigfishrunning 4 hours ago [-]
Good article, I even remember the Yak Shaving Day episode of Ren and Stimpy but never made the connection with the slang term
jemiluv8 3 hours ago [-]
Glad you gave yak-shaving a proper definition. I was always annoyed at my boss for insisting on a particular arrangement of import statements in typescript files. For him, it was a way of telling us to be more mindful of the code we typed. But mostly I’d have preferred a simple eslint config with autofix on save. This kinda yak shaving is no fun - trust me
dblohm7 1 hours ago [-]
Yak shaving is only fun when you don't have managers who don't care about the circumstances breathing down your neck.
jeltz 1 hours ago [-]
That is true for software engineering in general. If you have a manager like that nothing is fun. And the products you build are likely to be bad.
zem 2 hours ago [-]
the version I learnt the phrase from had the end of the chain as
- oh we should paint it
- we need a paintbrush
- I hear yak hair makes the best paintbrushes
- here I am, shaving a yak
made more sense than the examples given in the op
rzzzt 16 minutes ago [-]
Internet Search Thing now tells me sable (for soft brushes) and hog hair (for wire-like brushes) is the best hair for this purpose. Oxen occasionally show up. Yaks nowhere to be found.
Coincidentally, this is also the first time I'm hearing about sable.
clscott 30 minutes ago [-]
So yak shaving comes after bike shedding?
kazinator 2 hours ago [-]
> Both stories came after the term yak shaving was coined
They are yakocryphal. A real yakrilege to spread such nonsense.
4 hours ago [-]
wizardforhire 51 minutes ago [-]
Maybe the most beautiful examples of the joy and importance of yak shaving that I’ve ever come across is inheritance machining on youtube. [1]
But truthfully part of the process of creating in general is yak shaving… as is so often said “trust the process”.
Arguably, the entire concept of tech debt is owed to the lack of yak shaving.
Stewart Butterfield shaved the shit out of two yaks at his video games company, which eventually became Flickr and Slack.
Upside: Only the features you actually need. Likely fewer dependencies. You know exactly what your yak looks like under the fur.
At a previous job, my coworkers coined the term "Thomasing" [1], referring to me, as "the act of having a question explained so thoroughly, detailed, and long-winded that the asker has lost interest in the question that they were asking".
I thought it was pretty funny, because that does basically describe me in a nutshell.
[1] Lovingly, it was a good, fairly-tight-knit group, they weren't being jerks. We all did lighthearted ribbing.
https://youtube.com/shorts/kSJgLA1frS4?is=2RA7C0EDEe7Mg8Fp
I used ai to convert c headers into in nice zig code. Then I link to the library.
It’s cheap to use zig translate-c to convert c headers but the output isn’t nice.
You can give ai c++ source which usually has more documentation than the compromised flat c header. It allows you to do a better zig port. Zig greatly cuts down the noise in c headers as everything needs to have long prefix for namespacing. But in zig we can just nest things properly.
We can introduce intermediate layers to use proper tagged unions and distinguish ?T, *T, [*]T
But I use AI also for some of the ones where I deeply care about the code, now. E.g. my terminal is in Ruby, and it worked well enough, but over the last couple of days I had Claude put together a test harness and burn down a number of sharp corners and refactor the code. It's not perfect still, but it's cleaner than it was because I didn't have time to do enough yak shaving myself. I do care about that codebase, because I have other things I want to use it for, and not having to do it all manually gave me enough time to get it to a far better state.
I feel like a lot of the split comes from people who are a whole lot less overcommitted. If you have way too many projects, you pick and choose which projects you want to lovingly care for and which ones you just want to advance the functionality of as fast as possible. Sometimes those are one and the same at different times.
I’ve found that the overuse of AI papers over a lot of problems. Then if things start failing people have no idea where or what to start fixing. I’m very much a destination person, but I’ve been on enough rides which crashed and burned to be cautious about it.
Yaks [1] have a shoulder hump you can't miss.
0: https://en.wikipedia.org/wiki/Highland_cattle
1: https://en.wikipedia.org/wiki/Yak
I added plugins this year which made it really powerful and allows me to keep the core small.
[1] https://github.com/yakkomajuri/teeny
I needed pandoc, but the internet and electricity were both out, so I built my own in a race against my dying ebay laptop battery.
I enjoy a yak, but right sizing my yak is pretty important to my enjoyment of it. Maybe the yak doesn't get a full shave but gets a trendy hair cut, and that's okay.
I leave my yaks at home when I go to other engineers decision meetings, project kickoffs, or RFCs.
- oh we should paint it
- we need a paintbrush
- I hear yak hair makes the best paintbrushes
- here I am, shaving a yak
made more sense than the examples given in the op
Coincidentally, this is also the first time I'm hearing about sable.
They are yakocryphal. A real yakrilege to spread such nonsense.
But truthfully part of the process of creating in general is yak shaving… as is so often said “trust the process”.
Arguably, the entire concept of tech debt is owed to the lack of yak shaving.
[1] https://youtube.com/@InheritanceMachining
https://www.ulaandlia.com/collections/mongolian-baby-yak-woo...
Oh wait, you meant figuratively!