News for hackers. Stuff that matters.
Re:Coding as a greybeard by jerf on Tuesday August 02, 2022 @09:46AM (#32318395)
"Ageism is real and some of the younglings treat me as someone whose knowledge is obsolete, only to be proven wrong."

This meme is slowly dying, but let me do my part here to kick it along to death faster.

Nothing here is intended to offend per se, because I consider everything I say here to be the natural order of things, and there's nothing wrong with it. Still, it's the truth.

I'm in my mid-40s now. I've hired a lot of juniors over the years. Never once have I hired someone new and gone "Oh my god, they know so much, my job is at risk and I'm going obsolete!"

No, what happen when I hire junior is that I look at where they are now, and where they need to be to be a fully functional member of the team, and kind of sigh and make a plan to try to get them there as quickly as possible, plotting a minimal path through the thicket of things necessary to be a functioning software engineer nowadays. Six months is generally a bare minimum time line for this. Sometimes it's more.

And that's just to get to functional. A well-rounded engineer that I can plausibly just pass a project to and see them largely get it done correctly and without blowing their own or my foot off? Years. Years. And I just mean that from a technical perspective... it's yet more before I feel comfortable inserting them into the political layers.

Again, not intended to be offensive. Everyone has to pass through this phase. Every mature programmer should expect to be mentoring like this; if you're in your 40s and haven't had to do this at all, take a careful look at your career, something's probably wrong. (I don't mean management; I mean mentorship.)

There was one intern a few years ago who turned my head in that he had parity with me on a couple of interesting and unusual skills, but still... it was parity at best, not amazingly better than me. And while he had some amazing building skills for an intern I could see the skillset was still very, very lopsided and he needed a lot of work on the question of what to do, rather than just the doing of things. It's OK. That's normal. I'm not even sure how to hypothesize someone coming out of college with amazing skills in knowing exactly what to do. From what I see even when 20-year-old startup founders get this right it's a combination of mentorship from investors and sheer luck. I despair of even imagining how to teach this skill from anything other than experience, beyond simply sensitizing a student to the fact that it is something they should be looking at as they grow as an engineer.

There was a brief window in the 1990s where the industry underwent a technological convulsion and switched away from expensive mainframes to commodity computers and the internet/web. In that brief window, which I was lucky enough to capture and ride, a fresh young whelpling who had spent the last couple of months fiddling with this newfound "web" thing could do some things that the mainframe folks couldn't. There were still plenty of lessons that could have been learned from the mainframe folks, but for whatever reason, be in the internet just not being there yet, an unbridgeable cultural gap between the hacker mindset and the IBM mindset, whatever reason, the communication and wisdom transfer just didn't happen. That hasn't happened since then and I see no prospect of it happening in the next 10 years, not because the next 10 years won't see change but because the people like me of that era have already ridden any number of waves since then and adapted and I don't see that sort of convulsive surprise happening again.

The idea that someone in their 50s just has to be old and out of date is not just silly but downright ludicrous. Getting to "well rounded" in 2022 is something that will require you until your mid-30s minimum anymore.

I think a lot of the ageism that still lives in the industry are people who are unskilled and unaware. They can't even perceive what it is they are missing, so they are incapable of recognizing the skill gap. Since a lot of the ageism probably resides in people who aren't even engineers, managers, recruiters, people who are for any number of reasons good and bad simply incapable of interacting with engineers and being able to assess their skill levels, it's a plausible guess.

Re:Coding as a greybeard by hamburglar on Tuesday August 02, 2022 @10:06AM (#32318621)
One thing I find with young and exuberant people and their assumptions about old greybeards such as myself is that they are somewhat immodest about their knowledge. I’ll readily own up to not being an expert on some new tech and they will act as though they possess all the new hotness until we get into the thick of a project and we discover that my “cursory” grasp of the new tech actually goes significantly deeper than theirs. Sure, you’ve done a few projects with technology X, but I’ve actually bothered to find out how it really works under the covers. Both are valuable, but I’m getting you out of a jam because I’m willing to walk up and down the stack and debug problems at any level, whereas you’re stuck in the hot abstraction of the day. You’re welcome.
Re:Coding as a greybeard by daltont on Tuesday August 02, 2022 @10:54AM (#32319310)
I'm 55 in the middle of the US and I am like "where are all the junior devs that are coming for my job?". Where I am, there is not enough of them.

I have one kid in college an another going into her senior year of high school. Seems like very few their peers are going into computer science. I know it is not for every body, but it is surprising how unpopular it is.

Re:Coding as a greybeard by tibbon on Tuesday August 02, 2022 @12:58PM (#32321268)
I'm 39 and have been doing things in this realm since my teens. C64 was my first computer and I still know how to POKE my way around them.

There's a lot of great programmers coming up, but I often find their depth of knowledge to be limited. They can get to elegant solutions, but when it comes to how it fits into a larger distributed system architecture, security, scalability or long term maintainability they seem to start falling short. I've watched a lot of less experienced engineers want to just hit the "reset" button nonstop during an AWS outage, for hopes that resetting the system will clear up the problem and not intuiting the likely causes and consequences.

They simply need more time to expand out their layers of knowledge and experience. It will happen over time! I do feel that I was born of an era when many of the layers were more obvious to interact with and less abstracted. It is easy for a developer to get many years into their career and never interact with assembly these days - such was far less likely in the early 80's unless you wanted to only run slow BASIC programs forever.

Re:Coding as a greybeard by giantg2 on Tuesday August 02, 2022 @11:52AM (#32320270)
If you're in the middle of the US, there's a good chance that there aren't that many local tech jobs, requiring moving to a big city (which many don't want). It's also possible that they can make similar money in a trade as they can at the local tech jobs. If they do pay the same, I'd probably recommend a trade over IT. I know I won't be pushing my kid to be a dev based on my own dissatisfaction with the industry.
Re:Coding as a greybeard by mixmastamyk on Tuesday August 02, 2022 @12:30PM (#32320841)
IT may be annoying but it doesn’t destroy your body like many trades. Maybe gives ya a gut, haha.
Re:Coding as a greybeard by akimball on Tuesday August 02, 2022 @03:48PM (#32323408)
Stress will kill you no matter what your profession. Physical exercise can save your life. I nearly died on one IT job, and nearly killed myself on another. I became an investor to escape the pressure to undertake such positions, and now only do things I enjoy. Enough action for flow, not enough for excessive stress - and do physically challenging recreations.
Re:Coding as a greybeard by daltont on Wednesday August 03, 2022 @09:56AM (#32331713)
I live in medium size metropolitan area (big enough to have a MLB and a NHL franchise). There are plenty of tech jobs.
Re:Coding as a greybeard by BXLE_1-1-BitIs1 on Tuesday August 02, 2022 @10:13PM (#32326845)
Why become a dev when you will be downsized between 45 and 55?

It only pays off when you win the startup lottery and can cash out.

Re:Coding as a greybeard by toyg on Tuesday August 02, 2022 @10:32AM (#32318984)
> I see no prospect of it happening in the next 10 years

It's happening right now: the field is being flooded by data-kids who reason in different terms. They are statisticians first and programmers later. Their models can do stuff that bit-pushers like me will always struggle with. 10-15 years from now they'll run everything, and you won't be able to code a helloworld without specifying a ML model.

Re:Coding as a greybeard by jerf on Tuesday August 02, 2022 @10:42AM (#32319135)
I'm dabbling in that world right now. Along with the fact that, well, I'm dabbling in that world right now... no. They're doing different thing. You won't have ML models creating UI code (and I mean, actual UI code to draw widgets, not just assembling UIs) or any number of other tasks. They're doing new things. And we have plenty of time to learn, just like I haven't been left behind by any number of other things. It won't be like the web.

(In fact I've been generally unimpressed by the people I've seen so far. The ML math is complicated, but there's a whole lot of "just fire this at that without understanding why" in the actual practitioners. I've found I have a better understanding of what is and is not possible and why than they seem to rather often. This comes back to my extended education background, though; my training is old but less obsolete than you may think, a lot of modern ML stuff isn't some totally new thing just invented yesterday, but a couple of slight tweaks to established stuff that worked really well combined with finally having the CPU firepower to use it.)

Re:Coding as a greybeard by YeGoblynQueenne on Tuesday August 02, 2022 @11:25AM (#32319774)
That has to be said again. Basically all of deep learning, which is what people mainly mean today when they say "ML", is at least 20 years old. Other data science techniques? Even older. The big spurt seen recently is mainly the result of a) faster hardware and b) larger datasets [1]. At some point the "low-hanging fruit" achievable by scaling up and crunching down MOAR DATA will be all taken and then soemone will need to do all the hard work of figuring out new techniques, or at least building bigger computers. Who's going to do that? All the people who are "passionate about machine learning" and are experts in Tensorflow and PyTorch? I wouldn't bet my money on that. Thirty years from now the people leading the field will be people with thirty years of experience in thinking real hard about real hard problems. As they usually are [2].

__________________

[1] My standard reference for this is a guy called Geoff Hinton. Some people in machine learning may have heard the name. Quoting:

AMT: Ok, so you have been working on neural networks for decades but it has only exploded in its application potential in the last few years, why is that?

Geoffrey Hinton: I think it’s mainly because of the amount of computation and the amount of data now around but it’s also partly because there have been some technical improvements in the algorithms. Particularly in the algorithms for doing unsupervised learning where you’re not told what the right answer is but the main thing is the computation and the amount of data.

http://techjaw.com/2015/06/07/geoffrey-hinton-deep-learning-...

[2] Check out the birth dates of the current generation of deep learning luminaries. Geoff Hinton: 1947. Yoshua Bengio: 1964. Yann LeCun: 1960. Jurgen Schmidhuber: 1963. It goes on. Go ahead and tell those guys they're greybeards who don't get what the kids today are doing.

Re:Coding as a greybeard by hamburglar on Tuesday August 02, 2022 @10:55AM (#32319325)
Anyone who has gone through the extreme pixel-level iteration process of honing a UI at a company that really cares about UX knows we are very, very far off from letting AI do it.
Re:Coding as a greybeard by maerF0x0 on Tuesday August 02, 2022 @11:25AM (#32319775)
> you won't be able to code a helloworld without specifying a ML model.

I think the current ML world will have an overfitting reckoning. ML can optimize situations that are very normative, but struggles to create good solutions to situations in which the best outcomes are fairly distribute (but still specific best actions in certain scenarios).

ML cannot tell you what data or choices even matter in life, it can only help optimize those things once we've decided that. This is where age comes in as there's a correlation to, perhaps causal by, age on wisdom.

Re:Coding as a greybeard by telotortium on Tuesday August 02, 2022 @10:26PM (#32326931)
> I think the current ML world will have an overfitting reckoning.

It seems like current ML (at least large-language models and transformers) will actually run out of publicly-accessible data to train on - the current models have scraped the majority of the useful text and image data on the public Internet, and it's not clear that we'll gain access to orders of magnitude more data, which according to the Chinchilla paper is the bottleneck on transformer performance: https://news.ycombinator.com/item?id=32321522

Re:Coding as a greybeard by UncleOxidant on Tuesday August 02, 2022 @12:34PM (#32320905)
In my experience many of those "statisticians first and programmers later" "data-kids" aren't great at programming. Yes, they can build models, but when they need to build code around that model it's often pretty awful in my experience having worked with some of them. They still need us oldsters to help them out of the messes they make.
Re:Coding as a greybeard by sidlls on Tuesday August 02, 2022 @10:43AM (#32319140)
That is not a good thing. Nor do I think it’s completely true anyway. I have the advantage of a strong analytical background (PhD physics) and over a decade of experience in software development. The “data kids” struggle with the parts that actually make their jobs possible (engineering) and that part is not undergoing any kind of paradigm shift at this time.
Re:Coding as a greybeard by AnimalMuppet on Tuesday August 02, 2022 @12:01PM (#32320420)
For one of the young guys, you seem to have a pretty good perspective on this.

;-)

(I'm 60. And you're right.)