3 ms·
He's saying that these "kids" are capable of more than others give them credit for, and that experience is "really overrated". And he's right, if his claims ar
by mikestew 11y ago
He's saying that these "kids" are capable of more than others give them credit for, and that experience is "really overrated".
And he's right, if his claims are prefaced with "can be". Kids "can be" capable of more than the credit given. No one is a whiz kid just because they're young. In fact, most aren't. Most are wet-behind-the-ears welps that can do go work with a little guidance. Experience "can be" really overrated. As I told a former manager of mine who was tasked with managing my test team because he'd done it before, "just because you've done something doesn't mean you did it well". [0] And twenty years of doing CRUD in COBOL with no source control probably won't give you a huge leg up in a Django shop talking to a MongoDB data store using git to keep it all sane.
[0] (Lest you think me rude, this was after the umpteenth jillion time he'd remind me that he'd "managed test teams before", and role he proved time and again he didn't have the first clue about.)
- kafkaesq 11y agoAnd twenty years of doing CRUD in COBOL with no source control Just curious, are bringing up the 20 years of COBOL with no source control because that was your manager's background? Or is that your impression is of what the typical older tech worker has under their belt?
- mikestew 11y agoEDIT: apparently I didn't answer the question asked. Too deep to reply, so I blew away this one and rewrote it. I brought it up because "experience" in and of itself doesn't mean anything. 20 years of COBOL and practices from that era only means you were paid to do "work on a computer", and probably is not an indicator that you're going to walk into that Django/git/agile shop and set the world on fire. Just as some tire of the stereotype of the older tech worker, I tire of the assumption that "experience" automatically means someone has something to bring to the table. Bring me a resume of someone who has been doing primarily FoxPro for the last twenty years, and watch how fast I can dash to the shredder. Bring me another resume with experience writing apps in Turbo Pascal, and later moving to Delphi, with a brief stop in FoxPro during its heyday before moving on to .NET and mobile work, and watch how fast I type that email begging them to come in for an interview.
- kafkaesq 11y agoThat still doesn't answer why you brought it up. EDIT: The above line was in response to an earlier version of the parent comment, which was, itself, subsequently edited into oblivion.
- kafkaesq 11y agoOne of the things I do like about the older programmers I know -- making a fairly safe generalization here -- is the comparatively evolved early warning radar systems they have against the more insidious manifestations of kool-aid that have become amazingly popular in the industry in the past few years. "Agile" being one of the most common instances. And this idea that your startup is "setting the world on fire" being another.
- brightsize 11y agoThis has to be about the jillionth time, here in HN comments to ageism-related stories, that I've seen it either asserted, implied, or tangentially-suggested that older developers have most likely spent their prior years working mostly in COBOL or with similar outdated technologies. Their experience will almost certainly be at megacorps ("culture" mismatch!) and they've been avoiding new technologies and approaches because they're either pleased with COBOL or content to sit fat and happy and collect a paycheck like drones. They can safely be assumed to be stagnating because an older person is after all unlikely to care about their craft after some point in their careers. The assertion/implication/suggestion is absurd and only perpetuates the stereotype that competence and relevance and value are inversely correlated with age. I'm not exactly young, have very little experience working at megacorps, and have a lot of experience working at startups and at very small companies. I do consulting (no, not COBOL, not at megacorps), am constantly learning, and do a lot of coding for fun, both on side-projects and in the course of volunteer hacking. I don't have any reason to believe, none, that I'm not representative of most technical workers my age. No reason, that is, other than reading suggestions to the contrary here on HN. Edit: grammar, content
- mikestew 11y agoYeesh, the old folk are a touchy bunch, eh? I don't just pull this stuff out of my ass, you know. And, no, I didn't assert, imply, or suggest anything. But people that have been using the same development environment for over a decade are a thing. I can point you to mailing lists full of such developers, most of whom hope their preferred technology stack can keep them going to retirement. And those people can go on and on about their experience, but no one will care. If that doesn't apply to you, or the developers you know, umm...have a cookie? The assertion/implication/suggestion is absurd The only thing absurd in this thread is the assumption I'm lumping all the oldsters in one bucket, when what I was really implying was, "20 years of maintaining the same COBOL app is really one year of experience done 20 times." Oh, BTW, the odds overwhelmingly favor that I'm older than you are. Not that it should matter.
- kafkaesq 11y agoAn innuendo is an insinuation or intimation about a person or thing, especially of a denigrating or a derogatory nature. It can also be a remark or question, typically disparaging (also called insinuation), that works obliquely by allusion. In the latter sense the intention is often to insult or accuse someone in such a way that one's words, taken literally, are innocent. https://en.wikipedia.org/wiki/Innuendo https://en.wikipedia.org/wiki/Innuendo