tags
If you were doing computer engineering for undergrad studies, this feeling was probably popular: You’d study all night preparing for an exam, and you’d go over -almost- everything, except that one chapter you think is not important, only to go and find out the next day this chapter was all that matters.
This feeling of <insert psychological effect/term> turns out to be more popular than I thought.
- In software, people ALWAYS care about the missing feature, not about the other 100 ones that are perfectly-working
- In meetings, people always care about this ___, not about the ___
- In training, it’s always about ___ reps__, not about ____
- In writing, readers pay attention to your __, not your__
- It’s always about the missing part. And why is it missing?
- If your work is almost done, it’s exactly the same as “not done” - No one cares about what you’ve put in until you pull it off to the very end. If you don’t do this; if you don’t follow your work through to the very end, it really doesn’t matter whether you think you have put in a great deal of thought, sweat, or effort
- It’s the same in life, if you don’t follow through to the success of the very thing you’ve been working on, it’s exactly the same as never working a day on it - This is hard to explain but easy to feel
- <insert ref to sunk cost fallacy> - our brains are naturally programmed to think so highly of <insert sunk cost synonym> (efforts we did or work we did on things) - but that’s why it’s a fallacy
- in the most direct way: no one cares about your work if it’s almost done. people only care at the end line, and at this point, it’s either you’ve done something special or not. it’s always been like that, whether we get to acknowledge it or not. this applies on even the smallest of tasks, not just the big ones. it applies to the workout, the presentation, the race, the important meeting, the nagging deadline, ____. but no one judges -nor should they judge- by the ‘potential’ of success. it’s either success or failure, no imbetween.