Live data from Hacker News

A Research Preview of Codex

openai.com

411–420 of 487 posts

Re: A Research Preview of Codex

#411
I spend maybe $20 a month on Claude code, $200 a month is hard to swallow.

I don't understand why OAI puts their alpha release products under a $200 a month plan instead of just charging for tokens.

Re: A Research Preview of Codex

#412

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…

I don't think it's been dead for 10 years. I'd place it at maybe 3? I teach at a mid-ranked university and the majority of my fresh out of college students were getting good-to-great entry level offers just a few years ago. The top 5-10% were getting well into six figure offers from FAANG or similar companies. But the entry level job market really tanked in mid 2022 when all the big tech companies did rounds of layof…

This was pretty much the height of the “bootcamp” era, and while some were still great at teaching solid programming skills, many people who were mediocre coders saw it as a quick way to make money off those who don’t know better. In my opinion, companies started noting more and more that they were hiring people who can barely code in a real software environment but had focused training on resume padding and interview prep, and that many of the college graduates weren’t any better off, so they ramped up to far more rigorous testing, live coding projects, and more and more rounds of interviews just to weed out all the people who had been taught how to BS their way into a tech job. Now the interview process has become so cumbersome that it is more worthwhile to filter out nearly every applicant immediately.

Re: A Research Preview of Codex

#413
I've been experimenting with providers offering similar functionality for the last year and it is really vastly superior experience this codex like approach than cursor, devin etc

Re: A Research Preview of Codex

#414
post #12

Is anyone using any of these tools to write non boilerplate code? I'm very interested. In my experience ChatGPT and Gemini are absolutely terrible at these types of things. They are constantly wrong. I know I'm not saying anything new, but I'm waiting to personally experience an LLM that does something useful with any of the code I give it. These tools aren't useless. They're great as search engines and pointing me i…

What you're missing is how to use the tools properly. With solid documentation, good project management practices, a well-organized code structure and tests, any junior engineer should be able to read up on your codebase, write linted code following your codebase style, verify it via tests and write you a report of what was done, challenges faced etc. State of the art coding agents will do that at superhuman speeds.

If you haven't set things up properly (important info lives only in people’s heads / meetings, tasks dont have clear acceptance criteria, ...) then you aren't ready for Junior Developers yet. You need to wait until your Coding Agents are at Senior level.

Re: A Research Preview of Codex

#415

Earlier quoted context omitted.

> But at the same time, to be fair, this was a way easier task in the early 00s The best junior I've hired was a big contributor to an open source library we were starting to use. I think there's still lots of opportunity for honing your skill, and showing it off, outside of schools.

> The best junior I've hired was a big contributor to an open source library we were starting to use. From my experience no one cares. You're lucky if recruiter even looks at your CV, not to mention your GitHub profile.

As a candidate, you highlight it yourself!

Re: A Research Preview of Codex

#416

Earlier quoted context omitted.

++ Kind of my whole thesis with Graphite. As more code gets AI-generated, the weight shifts to review, testing, and integration. Even as someone helping build AI code reviewers, we'll _need_ humans stamping forever - for many reasons, but fundamentally for accountability. A computer can never be held accountable https://constelisvoss.com/pages/a-computer-can-never-be-held...

> A computer can never be held accountable I think the issue is not about humans being entirely replaced. Instead, the issue is that if AI replaces enough number of knowledge workers while there's no new or expanded market to absorb the workforce, the new balance of supply and demand will mean that many of us will have suppressed pay or worse, losing our jobs forever.

That is true regardless of whether there is or isn't a "new or expanded market to absorb the workforce".

It's a crucial insight that's usually missed or eluded in discussions about automation and workforce - unless you're literally at the beginning of your career, losing your career to automation screws you over big time, forever. At best, you'll have to downsize your entire lifestyle, and that of your family, to be commensurate with your now entry-level pay. If you're halfway through the career that suddenly ended, you won't recover.

All the new jobs and markets are for the kids. Mind you, not your kids - your kids are going to be disadvantaged by their household being suddenly thrown into financial insecurity or downright poverty, and may not even get a chance to start a good career path with their peers.

That, not "anti technology sentiment", is why Luddites smashed the looms. Those were people who got rug-pulled by business decisions and thrown into poverty, along with their families and communities.

Re: A Research Preview of Codex

#417
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…

do most people know country codes to the degree that they know CH is Switzerland? as feedback, i found this added an unnecessary extra layer of opacity to this comment

Whoops, definitely read that as China until your comment.

Re: A Research Preview of Codex

#418

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…

I would like to take this moment to point out that in NY it is ~illegal for me to hire an unpaid intern and train them by for example saying: - this is codex, here is a bunch of tickets - enter each ticket into codex, then review each change and understand what it did. if you think what it did is good, open a PR - twice a day we will meet and i will review all the codex PRs with you and explain what is and isn't working

etc.

This would not save me time. It would be paying it forward. And I cannot do this.

Re: A Research Preview of Codex

#419
post #223

Earlier quoted context omitted.

If you mean create as in literally, sure. But not in being creative. AI can't solve novel problems yet. The person you're replying to obviously means being creative not literally creating something.

What is the qualifier for this? Didn't one of the models recently create a "novel" algorithm for a math problem? I'm not sure this holds water anymore.

"After a couple of million suggestions and a few dozen repetitions of the overall process"

How much of it is brute force?

Re: A Research Preview of Codex

#420

Earlier quoted context omitted.

If you mean create as in literally, sure. But not in being creative. AI can't solve novel problems yet. The person you're replying to obviously means being creative not literally creating something.

You can't say AI is creating something new but that it isn't being creative with clearly explaining why you think that's the case. AI is creating novel solution to problems humans haven't cracked in centuries. I don't see anything more creative than this.

> AI is creating novel solution to problems humans haven't cracked in centuries

Really?

Post reply on HN