>>105836505
how does that ensure not "losing important knowledge or skills"
i've listened to a jon blow talk and i came to the conclusion that he's a terminal midwit who is oblivious that he's not as smart as he thinks he is, and not everyone is actually dumber than him. he constantly overcomplicates processes by trying to insert his own input into it due to some form of OCD and narcissism, but fails to understand that his own input isn't actually all that important.
like his braid talk had him explain that he tried several retarded but "optimized" solutions how to do the time travel mechanic until he finally settled on the "dumb" way to do it, which actually worked (but he still didn't like it). at that point he should have had some sort of epiphany that actually doing things the easiest and fastest way is usually the best way, because the main limiting factor in any kind of software dev is time, and obsessing over minutia just makes you annoying to work with. and the reason people don't reinvent the wheel is not because they can't fathom how a wheel might work, but rather because we already have the wheel.
i feel like any decent programmer learns these lessons in their first couple of years. but lo and behold he did not learn that lesson and here we are, still watching him make some shitty indie game and probably trying to make some UI component script run better instead of leaving a comment like "this is bad code lol" like everyone else does. i think jon blow is like the embodiment of the "second year programmer syndrome" in many ways, always thinking he knows best because he simply doesn't know enough, except he's like 50 years old
