3 ms·

I agree with this guy fully (having been professionally bitten by exactly what he describes and also having to innovate a way around it) but casually dismissing

by tomc1985 5y ago

I agree with this guy fully (having been professionally bitten by exactly what he describes and also having to innovate a way around it) but casually dismissing old-timers and old-school ways of doing thing reeks of ageism and needs to be stopped. Grow up, folks. In fact this entire culture of lambasting old stuff would be better off being taken out back and shot.

geekbird 5y ago
Here, here. I had one person advocate for a new, shiny piece of software by telling me that what we were using was "too old", because it was from 2012. This was the sum of his technical argument. No actual pros and cons, just an assertion that what we were using was "too old". The conversation took place in 2019. It was not a date dependent issue. Worse, what he was calling "too old" I didn't actually get to start using until 2014. I've been doing systems stuff since 1999. He essentially called my entire career obsolete because 90% of what I know was invented before 2019.
- tomc1985 5y ago
  And to think, these are the clowns starting companies and training the next generation. "I don't want to learn how to do this, and it's sOoOoOo hAaAaArd, I'll make my own product!" Cue my eyes rolling full circle
jheriko 5y ago
i got a similar impression, although i thought of it rather than being "anti-old-school" as less flattering "naive oss/linux mentality".... and a bunch of thoughts cursing how much this hurts progress. the mention of specific ages and the tone of it was way off the mark... the arguments don't really hold much weight either - frustrations rather than roadblocks. even after reading the article, which i expected to find interestingly informative... and did... i'm not sure there is any sense to be found in the rationale beyond the developer wanting an easier life. thats never a great line to follow in software development imo... its pretty much the opposite of the whole intent.
- tomc1985 5y ago
  There are a bunch of legit arguments in favor of retiring ISOs; he even touches on some of them (obsolescence)… but your users are your users, whether they’re snot-nosed kids or dusty old farts or whatever. All users matter!

geekbird 5y ago

Here, here. I had one person advocate for a new, shiny piece of software by telling me that what we were using was "too old", because it was from 2012. This was the sum of his technical argument. No actual pros and cons, just an assertion that what we were using was "too old". The conversation took place in 2019. It was not a date dependent issue. Worse, what he was calling "too old" I didn't actually get to start using until 2014. I've been doing systems stuff since 1999. He essentially called my entire career obsolete because 90% of what I know was invented before 2019.

tomc1985 5y ago
And to think, these are the clowns starting companies and training the next generation. "I don't want to learn how to do this, and it's sOoOoOo hAaAaArd, I'll make my own product!" Cue my eyes rolling full circle

jheriko 5y ago

i got a similar impression, although i thought of it rather than being "anti-old-school" as less flattering "naive oss/linux mentality".... and a bunch of thoughts cursing how much this hurts progress. the mention of specific ages and the tone of it was way off the mark... the arguments don't really hold much weight either - frustrations rather than roadblocks. even after reading the article, which i expected to find interestingly informative... and did... i'm not sure there is any sense to be found in the rationale beyond the developer wanting an easier life. thats never a great line to follow in software development imo... its pretty much the opposite of the whole intent.

tomc1985 5y ago
There are a bunch of legit arguments in favor of retiring ISOs; he even touches on some of them (obsolescence)… but your users are your users, whether they’re snot-nosed kids or dusty old farts or whatever. All users matter!