shanev

You are discounting iteration. Today they are fragile and lightweight. Tomorrow they will have better actuators, pneumatic/McKibben muscles, etc.

I built modelrelay.ai that does this. Happy to give you an invite code if you want to play with it.

Congrats on the launch! It would be useful to have a matrix somewhere showing how this compares to Jina, Firecrawl, etc.

The GPT models, in my experience, have been much better for backend than the Claude models. They're much slower, but produce logic that is more clear, and code that is more maintainable. A pattern I use is, setup a Github issue with Claude plan mode, then have Codex execute it. Then come back to Claude to run custom code review plugins. Then, of course review it with my own eyes before merging the PR.

My only gripe is I wish they'd publish Codex CLI updates to homebrew the same time as npm :)

This is solvable at the level of an individual developer. Write your own benchmark for code problems that you've solved. Verify tests pass and that it satisfies your metrics like tok/s and TTFT. Create a harness that works with API keys or local models (if you're going that route).

Close. It won because of Github. Git was gaining over SVN slowly but it was Github that really propelled it into widespread use.

DAOs are fixing this in the crypto world. You contribute to the protocol and get paid by the DAO. Everything is transparent and open. If you do this enough and earn the respect of the dev team it could even turn into a full-time role.

> He worked hard to enable software reuse. No one was interested in his idea of trying to monitor component use during runtime to pay developers

People are experimenting doing this in blockchain smart contracts. It’s transparent and supports micropayments as well.

I was mulling over this exact issue the other day but couldn't find the words to express it. Thank you for this.

I thought it was about resque, the ruby queuing library, switching from redis to kafka.