Abundance mindset (not LinkedIn cringe) - by Tyler Adams
CodeFaster is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.
We made a new one because it’s much much faster. Finding one requires searching codebases, extraction, and maybe, even, dealing with people. It also could requiring verifying that there’s no pollution issues with reusing the old one.
The scarcity mindset is toxic for fast coding. If you suspect you have it, you must root it out, remove it, and develop the abundance mindset. Unfortunately, “abundance mindset” has become LinkedIn cringe these days, so, please my reader, bear with me, I promise this isn’t a Tony Robbins scam seminar.
Let’s go over the “negative sides” quickly of both the “scarcity mindset” and “abundance minset” and why they’re both not really that bad.
In programming, a scarcity mindset leads to the Y2k bugs and Pokemon’s Missingno Glitches. 2 digits for years. Storing the user’s Name in wild pokemon data to conserve memory, but if that’s all you got, it’s fine because you shipped something working. Pokemon was a great game. We had digital banking in 1995 on 8MB of RAM.
