I've been hearing this term probably since TFA was published, but it's only been recently, ~15 years into my career that I realized how much I'm guilty of this. It's so easy to get caught up in that PR for that upstream dependency so your code is a bit prettier.
I've also noticed that the low-level yak shaving I tend towards becomes much less tempting if I focus on decoupling what I'm writing. As long as a function/module I'm not super happy with is nicely isolated/decoupled, who cares? I can easily swap it out later if it becomes an issue.
Comments
I've been hearing this term probably since TFA was published, but it's only been recently, ~15 years into my career that I realized how much I'm guilty of this. It's so easy to get caught up in that PR for that upstream dependency so your code is a bit prettier.
I've also noticed that the low-level yak shaving I tend towards becomes much less tempting if I focus on decoupling what I'm writing. As long as a function/module I'm not super happy with is nicely isolated/decoupled, who cares? I can easily swap it out later if it becomes an issue.