Live data from Hacker News

Ask HN: Am I getting old, or is working with AI juniors becoming a nightmare?

news.ycombinator.com

11–20 of 57 posts

Re: Ask HN: Am I getting old, or is working with AI juniors becoming a nightmare?

#11

There seems to be a disconnect, with some people claiming they don't write code any more, only specs, and me trying to get Copilot to fix a stupid sizing bug in our layout engine and it Not Getting It. Is this because the guys claiming success are working in popular, known, more limited areas like Javascript in web pages, and the people outside those, with more complex systems, don't get the same results ? I also not…

Maybe try claude. Also people are orchestrating AI for example with ralph. I think it is possible to write pretty decent, test driven, code with AI

Re: Ask HN: Am I getting old, or is working with AI juniors becoming a nightmare?

#14
Yes, absolutely, if you don't use AI in coding you will be a legacy developer sooner rather than later.

Everyone seriously doing it has a bunch of agents in a corporate like structure doing code reviews, the bad AI code is when someone is just using a single instance of Claude or Chat, but when you have 50 agents competing to write the best code from a single prompt, it hits differently.

Re: Ask HN: Am I getting old, or is working with AI juniors becoming a nightmare?

#16
post #15

Meta/Google/Anthropic report 75%+ of coding is now AI. For every engineer orchestrating AIs -- X will be let go -- but at what ratio 3:1? 5:1? 10:1? Seems like its at least 3.

Actually not worried about unemployment. This is an awesome development thing - called technological progress.

PS: Compare Assembly with Python - for sure the ration is more then 10x. Still we need much more devs compared to early days. For me the question is what the future software dev looks like (if the job still exists).

Re: Ask HN: Am I getting old, or is working with AI juniors becoming a nightmare?

#18
post #5

I think all of this has a dark future. And this can be argued based on how AI works. AI systems look at code on the internet that was written by humans. This is smart, clean code. And they learn from it. What they produce — unreadable spaghetti code — is the maximum they can squeeze out of the best code written by humans. In the near future, AI-generated code will flood the internet, and AI will start training on its…

We’ve had a looming crisis for decades of young people increasingly not understanding a lot of the fundamentals of mathematical logic. And I think treating LLMs (which are amazing tools) as “AI,” and having it play this type of role, is the final step towards a lot of unrecoverable self-destruction.

We need to remember that the core of what “logic” is can be understood by every human mind, and that it’s our individual responsibility to endeavor to build this understanding, not delegate or hand-wave it. For all of human history, delegating/hand-waving away basic logic that can be understood by actuarial/engineering types has never gone well in the long term.

Re: Ask HN: Am I getting old, or is working with AI juniors becoming a nightmare?

#19
> People coming from highly respected universities are doing everything with AI

Nowadays, everybody is doing everything with AI, young and old alike. It's very hard to justify not doing it. That being said, you can produce good code with AI, if you know what it should look like and spend the time to prompt and iterate.

Re: Ask HN: Am I getting old, or is working with AI juniors becoming a nightmare?

#20
MichaelRazum, you're hitting on something crucial many of us in the trenches are seeing. The "code is cheap" mentality, as you call it, leads to bloated, unreadable code. As baCist points out, if AI starts training on its own generated code, we're headed for a real problem with quality degradation.

I've found experienced developers leverage AI as a force multiplier because they can scrutinize the output, unlike juniors who often just paste and move on. The real skill is becoming an AI orchestrator, prompting effectively, and critically validating the output. Otherwise, if you're just a wrapper for AI, then yes, you become the "legacy developer" you mention because you're adding no critical thinking or value.

Post reply on HN