←back to thread

A Research Preview of Codex

(openai.com)
370 points meetpateltech | 2 comments | 16 May 25 15:02 UTC | HN request time: 0.673s | source
Show context
skovati ◴[16 May 25 16:01 UTC] No.44007027[source]▶
I'm curious how many ICs are truly excited about these advancements in coding agents. It seems to me the general trend is we become more like PMs managing agents and reviewing PRs, all for the sake of productivity gains.

I imagine many engineers are like myself in that they got into programming because they liked tinkering and hacking and implementation details, all of which are likely to be abstracted over in this new era of prompting.

replies(10): >>44007084 #>>44007089 #>>44007094 #>>44007178 #>>44007221 #>>44007237 #>>44007252 #>>44007274 #>>44008114 #>>44010090 #
awestroke ◴[16 May 25 16:06 UTC] No.44007084[source]▶
At the end of the day, it's your job to deliver value. If a tool allows you to deliver more faster, without sacrificing quality, it's your responsibility to use that tool. You'll just have to make sure you can fully take responsibility for the end deliverables. And these tools are not only useful for writing the final code
replies(3): >>44007247 #>>44009556 #>>44009962 #
1. enjoylife ◴[16 May 25 16:21 UTC] No.44007247[source]▶
> these tools are not only useful for writing the final code

This sparked a thought in how a large part of the job is often the work needed to demonstrate impact. I think this aspect is often overlooked by some of the good engineers not yet taking advantage of the AI tooling. LLM loops may not yet be good enough to produce shippable code by themselves, but they sure are capable to help reduce the overhead of these up and out communicative tasks.

replies(1): >>44007366 #
2. tough ◴[16 May 25 16:33 UTC] No.44007366[source]▶
you mean like hacking a first POC with AI to sell a product/feature internally to get buy-in from the rest of the team before actually shipping production version of it?