Live data from Hacker News

A Research Preview of Codex

openai.com

381–390 of 487 posts

Re: A Research Preview of Codex

#381

Earlier quoted context omitted.

If you aren't hiring junior engineers to do these kinds of things, where do you think the senior engineers you need in the future will come from? My kid recently graduated from a very good school with a degree in computer science and what she's told me about the job market is scary. It seems that, relatively speaking, there's a lot of postings for senior engineers and very little for new grads. My employer has hired…

Hiring of juniors is basically dead these days and it has been like this for about 10 years and I hate it. I remember when I was a junior in 2014 there were actually startups who would hire cohorts of juniors (like 10 at a time, fresh out of CS degree sort of folks with almost no applied coding experience) and then train them up to senior for a few years, and then a small number will stay and the rest will go elsewhe…

> Hiring of juniors is basically dead these days and it has been like this for about 10 years and I hate it

We still have a large funnel of interns that end up becoming junior devs, and then progressing normally. I don't know the exact ratio of interns that end up actually getting hired as full-time employees, it's definitely low, but I think this is more of a function of most of them not actually being any good.

Re: A Research Preview of Codex

#382

Some engineers on my team at Assembled and I have been a part of the alpha test of Codex, and I'll say it's been quite impressive. We’ve long used local agents like Cursor and Claude Code, so we didn’t expect too much. But Codex shines in a few areas: Parallel task execution: You can batch dozens of small edits (refactors, tests, boilerplate) and run them concurrently without context juggling. It's super nice to run…

If you aren't hiring junior engineers to do these kinds of things, where do you think the senior engineers you need in the future will come from? My kid recently graduated from a very good school with a degree in computer science and what she's told me about the job market is scary. It seems that, relatively speaking, there's a lot of postings for senior engineers and very little for new grads. My employer has hired…

> If you aren't hiring junior engineers to do these kinds of things, where do you think the senior engineers you need in the future will come from?

Hasn't this been a common refrain whenever someone found a way to automate any menial task in any job?

Re: A Research Preview of Codex

#383
post #227
post #222

Earlier quoted context omitted.

I recently read an article about the US having a relatively weak occupational training. To contrast, CH and GER are known to have very robust and regulated apprenticeship programs. Meaning you start working at a much earlier age (16) and go to vocational school at the same time for about 4 years. This path is then supported with all kinds of educational stepping stones later down the line. There are many software dev…

I know about this system, but I am not convinced it can work in such a dynamic field as software. When tools change all the time, you need strong fundamentals to stay afloat - which is what universities provide. Vocational training focusing on immediate fit for the market is great for companies that want to extract maximal immediate value from labour for minimal cost, but longer term is not good for engineers themsel…

I actually think it work fairly well, if it wasn't regulated.

Eg a company like Google (or similar) could probably offer you better on the job vocational training than going to uni would do to teach anyone programming.

Re: A Research Preview of Codex

#384
post #371

Earlier quoted context omitted.

Hiring of juniors is basically dead these days and it has been like this for about 10 years and I hate it. I remember when I was a junior in 2014 there were actually startups who would hire cohorts of juniors (like 10 at a time, fresh out of CS degree sort of folks with almost no applied coding experience) and then train them up to senior for a few years, and then a small number will stay and the rest will go elsewhe…

The place where I work at hires an ungodly amount of juniors and fresh-grads (because a lot of them drop out and quit before they do any meaningful work). We're talking people that are completely unproductive and unusable for any sort of commercial project. We then spend at-least a year or two giving them a salary whilst they do toy projects and get trained. Literally doing what I remember doing in 1st/2nd year colle…

Why does your company even hire those people? They seem like a net negative as far as your profit-and-loss is concerned?

I mean even compared to just not hiring any juniors.

Re: A Research Preview of Codex

#385
post #156

Earlier quoted context omitted.

This is a bit of a game theory problem. "Training senior engineers" is an expensive and thankless task: you bear essentially all the cost, and most of the total benefit accrues to others as a positive externality. Griping at companies that they should undertake to provide this positive externality isn't really a constructive solution. I think some people are betting on the fact that AI can replace junior devs in 2-5…

This hyper-fixation on replacing engineers in writing code is hilarious, and dangerous, to me. Many people, even in tech companies, have no idea how software is built, maintained, and run. I think instead we should focus on getting rid of managers and product owners.

> I think instead we should focus on getting rid of managers and product owners.

Who says companies aren't doing that with AI (and technology in general) already?

Re: A Research Preview of Codex

#386

Earlier quoted context omitted.

With Agentic RL training and sufficient data, AI operating at the level of average senior engineers should become plausible in a couple to a few years. Top-tier engineers who integrate a deep understanding of business and user needs into technical design will likely be safe until we get full-fledged AGI.

On the other hand I’m pretry sure you will need senior engineers not only for designing but debugging. You don’t want to hit a wall when your Agentic coder hits a bug that it just won’t fix.

Why do you expect AIs to learn programming, but not debugging?

Re: A Research Preview of Codex

#387

Earlier quoted context omitted.

That sounds like a dangerous bet.

I’m curious about other aspects of this: - leverage of countries who can host such AI over countries who can’t, will there be a point when countries can’t allow themselves not to have access to „emergency” talent in case they can’t use AI? Recent „choose european”, tariffs show that much of the high end stuff is concentrated in US and China. - outages happen, does the company stop because the cloud is not working? -…

Not being able to use AI would be entirely self-inflicted at the country level.

You can get around most of your objections by using a model with open weights that you run on-premises.

Re: A Research Preview of Codex

#388
post #186

Earlier quoted context omitted.

That sounds like a dangerous bet.

As I see it, it's actually the only safe bet. Case 1: you keep training engineers. Case 1.1: AGI soon, you don't need juniors or seniors besides a very few. You cost yourself a ton of money that competitors can reinvest into R&D, use to undercut your prices, or return to keep their investors happy. Case 1.2: No AGI. Wages rise, a lot. You must remain in line with that to avoid losing those engineers you trained. Case…

> The only way out of this, you can probably see, is some sort of external co-ordination, as is the case with most of these situations.

You lack imagination. You can eg just charge juniors for the training.

Either directly (which won't really work, because juniors almost by definition don't have a lot of money), or via a bond that they have to pay back iff they jump ship before a set number of years.

Have a look at how airlines and airline pilots pay for their expensive education.

Re: A Research Preview of Codex

#389
post #301
post #186

Earlier quoted context omitted.

As I see it, it's actually the only safe bet. Case 1: you keep training engineers. Case 1.1: AGI soon, you don't need juniors or seniors besides a very few. You cost yourself a ton of money that competitors can reinvest into R&D, use to undercut your prices, or return to keep their investors happy. Case 1.2: No AGI. Wages rise, a lot. You must remain in line with that to avoid losing those engineers you trained. Case…

> Case 1.2: No AGI. Wages rise, a lot. You must remain in line with that to avoid losing those engineers you trained. No you don't. Most engineers are shy, conflict-averse, and hate change. You can keep underpaying them and most of them will stay.

Yes, but only up to a point.

Re: A Research Preview of Codex

#390
post #385

Earlier quoted context omitted.

This hyper-fixation on replacing engineers in writing code is hilarious, and dangerous, to me. Many people, even in tech companies, have no idea how software is built, maintained, and run. I think instead we should focus on getting rid of managers and product owners.

> I think instead we should focus on getting rid of managers and product owners. Who says companies aren't doing that with AI (and technology in general) already?

Who says they are doing that?

The _instead_ was a key word in my comment. I didn’t say, or imply, they weren’t working on replacing other roles with AI.

Post reply on HN