Live data from Hacker News

Auto-research with codex: How I achieved a 232x Faster Kernel

sankalp.bearblog.dev

101–104 of 104 posts

Re: Auto-research with codex: How I achieved a 232x Faster Kernel

#101
post #100
post #95

Earlier quoted context omitted.

OpenAI is run by its employees and their culture is far healthier. Unlike Anthropic, they don't have a CEO that actively encourages their employees to be dishonest.

They have lost 12 executives in the past year. https://www.cnbc.com/2026/08/14/open-ai-ipo-red-flag.html

oh: https://www.morningstar.com/news/marketwatch/20260527189/sam...

Re: Auto-research with codex: How I achieved a 232x Faster Kernel

#102
post #59

Earlier quoted context omitted.

> Maybe it was a downgraded session, who knows. Off-topic, but imagine us collectively being okay with (or powerless to do anything about) this sentiment about any other software service provided like two years ago. How the times have changed…

Were other services so historically resource-constrained?

Good point, but to be honest, I interpreted the original comment, and worded mine with that in mind as well, to be more a critique of the “model downgrade (from frontier) due to a cybersecurity-related request” rather than a general compute shortage issue.

Re: Auto-research with codex: How I achieved a 232x Faster Kernel

#103

In the last couple of days I wanted to try out the new definitive DeepSeek v4 releases. I gave it the repository of a semi-abandoned video compression codec and I told it to perform the usual benchmark -> profile -> verify -> research -> improve loop. I specifically chose this codec because the authors include a verifier for the bitstream to make sure you don't break stuff if you want to try your own implementation.…

It's very much how I've been using claude code in the past 5 month: brainstorm -> generate specs (constraints) -> generate exact plan -> implementation + review -> test / validate. The last stage is the most crucial one, and it's the most difficult to get it right for a complex solution (it's tough to cover every variation). But so far, it's been working great..
Post reply on HN