Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Research Preview of Codex

openai.com

Post reply on HN
Print view View original

191–200 of 487 posts

Re: A Research Preview of Codex

#191

Post by jchanimal »

dorian-graph wrote: post #188
_bin_ wrote: 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.

The real judge will be survivorship bias and as a betting man, I might think product owners are the ones with the entrepreneurial spirit to make it to the other side.

Re: A Research Preview of Codex

#192

Post by lispisok »

hintymad wrote: post #179
johnjwang wrote: post #80

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…

It looks we are in this interesting cycle: millions of engineers contribute to open-source on github. The best of our minds use the code to develop powerful models to replace exactly these engineers. In fact, the more code a group contributes to github, the easier it is for the companies to replace this group. Case in point, frontend engineers are impacted most so far. Does this mean people will be less incentivized…

As much as I support community developed software and "free as in freedom", "Open Source" got completely perverted into tricking people to work for free for huge financial benefits for others. Your comment is just one example of that.

For that reason all my silly little side projects are now in private repos. I dont care the chance somebody builds a business around them is slim to none. Dont think putting a license will protect you either. You'd have to know somebody is violating your license before you can even think about doing anything and that's basically impossible if it gets ripped into a private codebase and isnt obvious externally.

Re: A Research Preview of Codex

#193

Post by nkko »

ilaksh wrote: post #148
sudohalt wrote: post #120

When it runs the code I assume it does so via a docker container, does anyone know how it is configured? Assuming the user hasn't specified an AGENTS.md file or a Dockerfile in the repo. Does it generate it via LLM based on the repo, and what it thinks is needed? Does it use static analysis (package.json, requirements txt, etc)? Do they just have a super generic Dockerfile that can handle most envs? Combination of di…

I think they mentioned it was a similar environment to what it trains on, so maybe they have a default Dockerfile. Of course containers can also install additional packages or at least python packages.

Yes, and one test failed as it missed pydantic dependency

Re: A Research Preview of Codex

#194

Post by criddell »

voidspark wrote: post #176
criddell wrote: post #112

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…

This is exactly the problem. The top level executives are setting up to retire with billions in the bank, while the workers develop their own replacements before they retire with millions in the bank. Senior developers will be mostly obsolete too. I have mentored junior developers and found it to be a rewarding part of the job. My colleagues mostly ignore juniors, provide no real guidance, couldn't care less. I see t…

> I have mentored junior developers and found it to be a rewarding part of the job.

That's really awesome. I hope my daughter finds a job somewhere that values professional development. I'd hate for her to quit the industry before she sees just how interesting and rewarding it can be.

I didn't have many mentors when starting out, but the ones I had were so unbelievably helpful both professionally and personally. If I didn't have their advice and encouragement, I don't think I'd still be doing what I'm doing.

Re: A Research Preview of Codex

#195

Post by rowanG077 »

Daishiman wrote: post #185
hintymad wrote: post #179

Earlier quoted context omitted.

It looks we are in this interesting cycle: millions of engineers contribute to open-source on github. The best of our minds use the code to develop powerful models to replace exactly these engineers. In fact, the more code a group contributes to github, the easier it is for the companies to replace this group. Case in point, frontend engineers are impacted most so far. Does this mean people will be less incentivized…

> P.S., I think the current trend is a wakeup call to us software engineers. We thought we were doing highly creative work, but in reality we spend a lot of time doing the basic job of knowledge workers: retrieving knowledge and interpolating some basic and highly predictable variations. Unfortunately, the current AI is really good at replacing this type of work. Most of the waking hours of most creative work have th…

I disagree. AI have shown to most capable in what we consider creative jobs. Music creation, voice acting, text/story writing, art creation, video creation and more.

Re: A Research Preview of Codex

#196

Post by oytis »

voidspark wrote: post #176
criddell wrote: post #112

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…

This is exactly the problem. The top level executives are setting up to retire with billions in the bank, while the workers develop their own replacements before they retire with millions in the bank. Senior developers will be mostly obsolete too. I have mentored junior developers and found it to be a rewarding part of the job. My colleagues mostly ignore juniors, provide no real guidance, couldn't care less. I see t…

> I have mentored junior developers and found it to be a rewarding part of the job.

Can totally relate. Unfortunately the trend for all-senior teams and companies has started long before ChatGPT, so the opportunities have been quite scarce, at least in a professional environment.

Re: A Research Preview of Codex

#197

Post by ionwake »

Im sorry if Im being silly, but I have paid for the Pro version, $200 a month, everytime I click on Try Codex, it takes me to a pricing page with the "Team Plan" https://chatgpt.com/codex#pricing.

Is this still rolling out? I dont need the team plan too do I?

I have been using openAI products for years now and I am keen to try but I have no idea what I am doing wrong.

Re: A Research Preview of Codex

#198

Post by layer8 »

nmca wrote: post #154
kleiba wrote: post #33

Just curious: is your company happy sharing their code-base with an AI provider? Or are you using a local installation?

It is a cost benefit trade off, as with all things. Benefits look pretty good.

The cost of sharing your code is unknown, though.

Re: A Research Preview of Codex

#199

Post by mr_north_london »

ionwake wrote: post #197

Im sorry if Im being silly, but I have paid for the Pro version, $200 a month, everytime I click on Try Codex, it takes me to a pricing page with the "Team Plan" https://chatgpt.com/codex#pricing . Is this still rolling out? I dont need the team plan too do I? I have been using openAI products for years now and I am keen to try but I have no idea what I am doing wrong.

It's still rolling out

Re: A Research Preview of Codex

#200

Post by jdee »

ionwake wrote: post #197

Im sorry if Im being silly, but I have paid for the Pro version, $200 a month, everytime I click on Try Codex, it takes me to a pricing page with the "Team Plan" https://chatgpt.com/codex#pricing . Is this still rolling out? I dont need the team plan too do I? I have been using openAI products for years now and I am keen to try but I have no idea what I am doing wrong.

im the same, and it appeared for me 2 mins ago. looks like its still rolling out
Post reply on HN