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

Harness engineering: Leveraging Codex in an agent-first world

openai.com

Post reply on HN
Print view View original

211–220 of 222 posts

Re: Harness engineering: Leveraging Codex in an agent-first world

#211

Post by pramodbiligiri »

swyx wrote: post #208
pramodbiligiri wrote: post #148

Earlier quoted context omitted.

(OP here) The truth is much simpler. I mailed the mods and they bumped it up in the second chance pool [1] :) 1. https://news.ycombinator.com/item?id=26998309

ha ok but why do that for a post you didnt write?

Because I thought this is a good blog and more people should get to know. Found it by chance in some other thread: https://news.ycombinator.com/item?id=48414452.

Did the same with this Cloudflare one the other day: https://news.ycombinator.com/item?id=48276152

Re: Harness engineering: Leveraging Codex in an agent-first world

#212

Post by advertum »

LOC was never really the point, if anything it's often the opposite. Being able to say the same thing more concisely makes code cheaper to maintain and easier to understand. (Not always: sometimes people are concise just for its own sake, and that's worse.) Either way, that whole debate feels like the past now.

As for metrics based on how much was produced or spent, like companies measuring developer performance by tokens used, that's a dead end regardless. Performance should be measured by outcomes: incident/failure rate, SLA, user numbers and feedback, revenue, that kind of thing.

Re: Harness engineering: Leveraging Codex in an agent-first world

#213

Post by ndegwaduncan »

shepherdjerred wrote: post #34

This mirrors exactly what I have been doing. - Give Claude/Codex a way to verify its own work (browser, smoke tests, e2e tests, high-fidelity local environment) - Keep all context (issue tracking, docs, ideas, plans, worklogs) in-repo ( https://github.com/shepherdjerred/monorepo/tree/main/package... ) - Give Claude/Codex access to observability (Grafana, Prometheus, Tempo, PagerDuty) - Have Claude/Codex follow good e…

[dead]

Re: Harness engineering: Leveraging Codex in an agent-first world

#214

Post by everforward »

torben-friis wrote: post #181
everforward wrote: post #169

Earlier quoted context omitted.

Seconded on smaller files. I feel like I tend to get better responses faster. A notable flaw here is that I’ve not tried large vs small files in a large codebase. Most of my experimentation there has been on personal projects where even a small file contains a significant part of the project. I could see degradation when it has to load 5 files to figure out how something works. Total LOC (tokens, really, literal line…

>Eg last I checked Anthropics one-shot performance on Clojure was about the same as Python or Go despite almost certainly being less represented in training data. The combination of density and simple primitives might be easier for an LLM to wrangle, ameliorating the impact of a less popular language. There might be tons of confounding factors there. One that comes to mind is the quality of of data, it might perfectl…

Oh there absolutely are, I don’t mean to imply any certainty in that attribution.

Quality of data is totally one. Immutability may be another (it’s easier to reason about if you don’t have to track mutations to a variable). Another interesting one is Clojures emphasis on composability using basic primitives that are sort of hard to grok initially but unlock really cool stuff.

You can do some incredible stuff with recursive map and arrow functions in a few dozen characters.

Re: Harness engineering: Leveraging Codex in an agent-first world

#215

Post by dredmorbius »

swyx wrote: post #208
pramodbiligiri wrote: post #148

Earlier quoted context omitted.

(OP here) The truth is much simpler. I mailed the mods and they bumped it up in the second chance pool [1] :) 1. https://news.ycombinator.com/item?id=26998309

ha ok but why do that for a post you didnt write?

I do this somewhat frequently myself.

Why? Because good stuff often falls through the cracks, and I like to see people discuss substantive material rather than just the "easy" submissions which tend to attract quick votes. This is one of the best ways to have a positive impact on the HN submission queue. And mods appreciate the suggestions (they can't keep up with the firehose either, and are well aware of the HN submission queue's weaknesses).

See: https://news.ycombinator.com/item?id=46018486>, https://news.ycombinator.com/item?id=26998308>.

Re: Harness engineering: Leveraging Codex in an agent-first world

#216

Post by bicepjai »

bko wrote: post #2

> We had weeks to ship what ended up being a million lines of code... Five months later, the repository contains on the order of a million lines of code across application logic, infrastructure, tooling, documentation, and internal developer utilities. Over that period, roughly 1,500 pull requests have been opened and merged with a small team of just three engineers driving Codex. This translates to an average throug…

It’s sad we back at measuring code quality with lines of code

Re: Harness engineering: Leveraging Codex in an agent-first world

#218

Post by [deleted] »

drivebyhooting wrote: post #200
kmetan wrote: post #195

Earlier quoted context omitted.

Instead of reading articles like this one end to end, I ask AI to read them in detail and prepare a new harness for me. The important part is not to do this in a single prompt, but to first create a detailed plan and let the model think deeply about each aspect. This approach lets me build the new harness without the missing didactic information you mentioned. Basically, I am moving from “I build products without wri…

I love this idea! Thanks

[deleted]

Re: Harness engineering: Leveraging Codex in an agent-first world

#219

Post by frankieg33 »

kmetan wrote: post #195
drivebyhooting wrote: post #62

I wish these breathless blog posts would actually try to be more didactic. For example, actually doing a walkthrough of how to set up these allegedly super powered workflows and concrete demonstrations. I’m not an AI skeptic. Rather I’d don’t want to miss out on any actual super powers.

Instead of reading articles like this one end to end, I ask AI to read them in detail and prepare a new harness for me. The important part is not to do this in a single prompt, but to first create a detailed plan and let the model think deeply about each aspect. This approach lets me build the new harness without the missing didactic information you mentioned. Basically, I am moving from “I build products without wri…

I will use chatgpt chat to do the same thing, but I like the idea of using basically a fork of the claude code session to splinter off and watch the system from the outside with the same amount of context
Post reply on HN