- author starts with saying he's a beginner. But somehow, this gives him better insights than others, because 'fresh pair of eyes', and 'resistance to new things'
- then he says (about the industry in general) 'To me it seems really slow to adopt new concepts.' (wtf?)
- except then he says 'Programmers should really take a leaf from the Mathematics & Sciences'. Because they move faster than programming, he must mean? To paraphrase Babbage badly - 'I am unable to comprehend the sort of confusion that could lead to such a statement'.
- then he says that the 'the primary source of innovation in the it industry is from open source projects'. (yeah, sorry to be that guy, but imma need to put some 'citation needed' on that one)
- and then, somehow, this leads to a justification on why he wants to learn about some javascript framework (because of course - 'learning' as a programmer is about getting used to the idiosyncrasies of the umpteenth 'framework' that does the exact same thing as the other ones before it, except in a way that is shitty in another way. O excuse me, 'having it under your belt'.)
- but of course, if experienced people call out the futility of it, they are idiots! Because he started off this whole thing with 'I’ve experienced a strange culture of the better a programmer becomes at a subject the less they feel the need to learn.'!) So ignore people who've been there because they're just old geezers who don't know anything anyway!
What ticked me off enough to waste 10 minutes of my life on writing the above, was the claim that software should be more like proper engineering and science - and then going on to claim that the way to do this is by jumping from one navel-gazing fad framework to the next even faster! Lol this attitude would be laughed out of a proper engineering firm so fast it wouldn't have time to take its jacket off.
And of course, everybody is free to post whatever they want on the internet, so why do I care; but cultish nonsense like this does actually harm newcomers who think it somehow represents truth, and who might waste years of their career on chasing technical details while in the mean time neglecting (or not even realizing the existence of) what truly matters for progression as a software engineer: the bigger picture within the business, evergreen CS fundamentals, complementary technology, etc.
Now if you'll excuse me, my local senior center's workshop 'Dealing with age-induced grumpiness: an introduction for those who see 40 looming!' starts in half an hour...