4 ms·
I'm not a developer but I believe it applies in a lot of other areas. I've been slowly rebuilding the Bronco II my dad left me when he passed away earlier this
by morganvachon 10y ago
I'm not a developer but I believe it applies in a lot of other areas. I've been slowly rebuilding the Bronco II my dad left me when he passed away earlier this year, and I've found that if I come across an issue that I have to figure out and I'm hot and tired and sore from working on it all day, I am better off stopping there for the day and tackling that issue first thing the next day that I work on it. Otherwise I'll spend hours trying to do something in a boneheaded way that I will end up figuring out in 10 minutes the next attempt.
A recent example: I couldn't find the right combination of extensions and adapters to get a certain bolt off the transmission bellhousing from below the car, and I couldn't even touch the bolt from above. I spent half a day just getting a socket on there, then couldn't get my wrench to turn it. A couple days later I tackled it again and immediately realized I could remove the lower intake manifold (since I was replacing that part anyway) and get to it from the top. Twenty minutes later that bolt was out. My tired brain couldn't think that far ahead but when I was refreshed it was the first thing I thought of.