Hacker News Reader

Comment by Loic | Hacker News Reader

> What junior devs will do, I'm not so sure. They somehow have to jump to the top of the mountain, but the stairs are gone.

Exactly my thinking, nearly 50, more than 30 years of experience in early every kind of programming, like you do, I can easily architect/control/adjust the agent to help me produce great code with a very robust architecture. By I do that out of my experience, both in modelling (science) and programming, I wonder how the junior devs will be able to build experience if everything comes cooked by the agent. Time will tell us.

View on HN

I feel like we've been here before, and there was a time when if you're going to be an engineer, you needed to know core equations, take a lot of derivatives, perform mathematical analysis on paper, get results in an understandable form, and come up with solutions. That process may be analogous to what we used to think of as beginning with core data structures and algorithms, design patterns, architecture and infrastructure patterns, and analyzing them all together to create something nice. Yet today, much of the lower-level mathematics that were previously required no longer are. And although people are trained in their availability and where they are used, they form the backbone of systems that automate the vast majority of the engineering process.

It might be as simple as creating awareness about how everything works underneath and creating graduates that understand how these things should work in a similar vein.

Exactly right now, I am helping a big oil and gas company have a process simulation software to correctly converge on a big simulation. Full access to the source code, need to improve the Newton method in use with the right line search, validate the derivatives, etc.

I do think that for most of the people, you are right, you do not need to know a lot, but my philosophy was to always understand how the tool you use work (one level deeper), but now the tool is creating a new tool. How do you understand the tool which has been created by your Agent/AI tool?

I find this problem interesting, this is new to me and I will happily look at how our society and the engineering community evolve with these new capacities.

I don’t know how seniors will cope. You seem to have a solid understanding that you can make use of AI. But most seniors on HN struggle with basic tasks using AI. Juniors are likely to out pace them quickly. But potentially without the experience or understanding.

They cope just fine. If you’re thinking about stubborn ‘AI is just a statical parrot’ folks, IME it takes just one interaction where it clicks and nothing is the same afterwards. Perhaps we need GPT-5 or Gemini 3 for some of those people, but that’s what, a year out? Or a month?

Juniors need experience to know if the machine is going in the right direction or guide it. That experience is now nigh impossible to get, nobody has the time for apprentices now. It’ll take some brave management to pave a way forward, we don’t know what it’ll be exactly yet.

Really well said, it's a large amount of directing in additoin to anything else.

To continue this thought - what could have been different in the last 10-15 years to encourage junior developers to listen more where they might not have to those who were slightly ahead of them?

Reply on news.ycombinator.com