[deleted]
A Research Preview of Codex
231–240 of 487 posts
Re: A Research Preview of Codex
#232Earlier 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 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…
I think it'll be great if you're working in software not for a software company.
Re: A Research Preview of Codex
#233Some 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…
Same, mine is about to graduate with a CS masters from a great school. Couldn't get any internships, and is now incredibly negative about ever being able to find work, which doesn't help. We're pretty much looking at minimum wage jobs doing tech support for NGOs at this point (and the current wave of funding cuts from Federal government for those kind of orgs is certainly not going to help with that).
Re: A Research Preview of Codex
#234Earlier 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.
As a dev, if you try taking away my product owners I will fight you. Who am I going to ask for requirements and sign-offs, the CEO?
Re: A Research Preview of Codex
#235Earlier quoted context omitted.
In my experience, it still does take quite a bit of time (minutes) to run a task on these agentic LLMs (especially with the latest reasoning models), and in Cursor / Cline / other code editor versions of AI, it's enough time for you to get distracted, lose context, and start working on another task. So the benefit is really that during this "down" time, you can do multiple useful things in parallel. Previously, our e…
In my experience in Cursor with Claude 3.5 and Gemini 2.5, if an agent has run for more than a minute it has usually lost the plot. Maybe model use in Codex is a new breed?
It depends what level you ask them to work on, but I agree, all of my agent coding is active and completed in usually <15 seconds.
Re: A Research Preview of Codex
#236Re: A Research Preview of Codex
#237Earlier 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…
> 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.
Re: A Research Preview of Codex
#238Just curious: is your company happy sharing their code-base with an AI provider? Or are you using a local installation?
For 99% of companies, their code is worthless to anyone but them.
Re: A Research Preview of Codex
#239Earlier quoted context omitted.
Post realizing CC can operate same code base, same file tree on different terminals instances, it's been a significant unlock for us. Most devs have 3 running concurrently. 1. master task list + checks for completion on tasks. 2. operating on current task + documentation. 3. side quests, bugs, additional context. rinse and repeat once task done, update #1 and cycle again. Add in another CC window if need more tasks c…
do you have then instance 2 and 3 listening to instance 1 with just a prompt? or how does this work?
to answer my own questions , it is actually laid out in chapter 6 of https://www.anthropic.com/engineering/claude-code-best-pract...
Re: A Research Preview of Codex
#240Earlier 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? Unfortunately this is not how companies think. I read somewhere more than 20 years ago about outsourcing and manufacturing offshoring. The author basically asked the same: if we move out the so-called low-end jobs, where do we think we will get the senior engineers? Yet c…
ahh, the classic “i shall please my investors next quarter while ignoring reality, so i can disappoint my shareholders in 10 years”. lol. As you say, happens all the time. Also doesn’t make sense because so few people are buying individual stocks anyway. Goal should be to consistently outperform over the long term. Wall street tends to be very myopic. Thinking long term is a hard concept for the bean counters at thes…
What then ends up happening is that companies how fall behind in R&D eventually lose market share and get replaced by more agile competitors.
But this does not happen in industry verticals that are protected by regulation (banks) or national interest (Boring).