For me this happens when I'm starting something I've never done before. Like I wanted to refurbish an old bike. The project was 10 years in the waiting, as I was overwhelmed by where to start, what tools do I need and then I just pushed it aside. Then I started to study how do I remove the crankset, and found out that there are like gazillion different types, and got overwhelmed again. But then there was a discount on a toolset that covers most parts and their types, bought it, watched RU-vid videos, asked a couple of times for help from a local bike shop, and I got the project done in less than a week, and in a couple of ways, the bike is now better than it was when it was new (higher quality parts).
OMG so spot on! Ijust downloaded this so that I can show it to my boss to explain to her why I haven't finished the project she gave me months ago because I've never come up with a way to express it thats not gonna get me fired. Thanks so much, only came across your vids yesterday and you've already helped ❤
Ironically this is often quite useful for software development, because thinking of all the worst cases and edge cases is the hardest part of programming well. So when I finally write something it's very functional... It probably doesn't compile at first try because my typing is sloppy, but the fundamental logic is sound 😅
Yes! I'm usually That Person in the team saying "wait, there's this possibility, our solution might be flawed if we don't take this corner case into account". Of course, the downside is sometimes getting stuck with a completely hypothetical problem.
@@fintux fortunately in most applications, as long as you have thought about an error scenario, it's usually perfectly fine to just detect a bad case and pop an error message. (One of the few exceptions I can think of is flight control systems where stopping is not an option, but I'm fortunately not making anything that critical 😅)
