Obviously novel problems require novel solutions, but the vast majority of software solutions are remixes of existing methods. I don’t know your work so I may be wrong in this specific case, but there are a vanishingly small number of people pushing forward the envelope of human knowledge on a day-to-day basis.
My company (and others in the same sector) depends on certain proprietary enterprise software that has literally no publicly available API documentation online, anywhere.
There is barely anything that qualifies as documentation that they are willing to provide under NDA for lock-in reasons/laziness (ERPish sort of thing narrowly designed for the specific sector, and more or less in a duopoly).
The difficulty in developing solutions is 95% understanding business processes/requirements. I suspect this kind of thing becomes more common the further you get from a "software company” into specific industry niches.
The reason for this is Rivian and Tesla bet big on software defined platforms… ie every piece of hardware talks to a small number of central computers instead of many independent systems. This gives them a huge leg up in developing software than can actually take all the available input and use it to control all aspects of the vehicle.
Downside is all the buttons are on a screen. But I’ve grudgingly decided it’s worth it for software upgrades.
The current Gen 1s will start beeping at you if they can’t see the lines. If you don’t take over quickly it will start slowing down and beeping very insistently.
Not only is Rivian betting on an integrated platform being important for their own cars long term, they’ve also essentially sold that portion of their business to VW. They are investing in the software platform for a lot more cars than just the rivian branded ones.
A lot of commenters are focusing on the legalities and likelihood of backpay, which is relevant but I tend to agree with you… it’ll get paid because it’s in the interest of both parties to pay their employees what they’re owed.
We’re staring down the barrel of two missed paychecks though. If you're living paycheck to paycheck you’re getting desperate. If you’re living with about 1 month of emergency buffer… that buffer is one paycheck away from gone. It’s a cash flow issue
And the republicans could just vote to change the rules of the senate.
The out of power party gets a little veto power here. The republicans know the day will come they want that, so they won’t change the rules even though they have the power to do so (theoretically… there are republicans that will never compromise on this). Unfortunately they can’t get on the same page with their lame duck leader
My interpretation of the parent comment was that they were loading specific curl calls into context so that Claude could properly exercise the endpoints after making changes.
Why aren’t more folks using Codex cloud? Simon’s post mentions it, but the vast majority of comments are talking about parallel agents locally or getting distracted while agents are running.
Personally I’ve found that where AI agents aren’t up to the task, I better just write the code. For everything else, more parallelism is good. I can keep myself fully productive if many tasks are being worked on in parallel, and it’s very cheap to throw out the failures. Far preferable imo to watching an agent mess with my own machine.
Could be that it's a bit harder to get started with?
You have to configure your "environment" for it correctly - with a script that installs the dependencies etc before the container starts running. That's not an entirely obvious process.
Good point. The environments I’ve set up have been pretty easy but I’ll admit that at first I was very annoyed that it couldn’t just use a pre-existing GitHub action workflow.
Edit: environment setup was also buggy when the product launched and still is from time to time. So, now that I have it set up I use it constantly, but they do need to make getting up and running a more delightful experience.
Also, Codex Cloud and similar services require you to give fully access to your repository, which might trigger some concerns. If you can run it locally, you still have the control, same development environment, and same permissions.
It doesn’t have access to your repo when the agent is running (unless you give it internet access and credentials). The code is checked out into the sandbox before it’s let loose.
