![]() There’s a lot going on here, so I’d better explain. One day, my inner software engineer kicked in again and I needed to do something about the situation. My workbench has been a disaster zone for years, all because I set it up somewhat hastily, then procrastinated improving it, then got used to the state of it, then gradually got less and less efficient over time because of it. I think shop people could benefit from doing a little more yak shaving.Īn example of this is shop organization. We don’t think in terms of the related tasks across disparate projects that we could be optimizing. We tend to procrastinate on doing things that would make us more efficient, because in the shop, “efficiency” feels like “getting this one thing done as quickly as possible”. Working in the shop, I think the opposite happens. You imagine doing this process hundreds of times, and thus all these tools are perfectly justified from a time return-on-investment standpoint. This comes from the innate obsession with efficiency that all software engineers seem to have. ![]() Pretty soon you’ve pushed so many sub-projects on to your stack that you lose track of what the original problem was that you’re trying to solve. Then, while building that tool, you realize part of this tool would be a lot easier to make if you had a different tool to assist. You’ll be working on a problem, and realize you could do this a lot more efficiently if you built a tool to use for part of the problem. This refers to a common rabbit hole that software engineers fall down. There’s an expression in software engineering- “yak shaving”. Sign up now to see it! It shows detailed construction steps for this entire project. This post has an exclusive companion video for Patrons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |