It's tricky because dissenting doesn't necessarily mean you'd reach the opposite conclusion in every respect.
In this case, I really doubt even the most conservative justices believe "birthright citizenship means whatever an Executive Order says it does." At a minimum, we know they aren't signing on to the reasoning the 5 in the majority used. And then we can learn whatever they feel like saying in the dissent, but a dissent is just an essay with no force of law.
Every serious engineer I've seen try to use it ran away screaming, because of limitations in the sandbox.
I've also seen people set their coding agents up entirely within containers -- that may be the better way going forward, but it's an extra stop and a lot of extra plumbing to maintain.
> Just getting the code to run on your laptop took a week.
This one surprised me. Claude Code in the CLI has made standing up an app and debugging whatever random dependencies or docker BS a dream compared to the before times, when you'd have to learn the architecture while simultaneously troubleshooting whatever isn't working on your machine
Some business users spent ~30 minutes on an internal process, and we prototyped an "Agent" in Slack to take over. At first it didn't work, then it didn't work some more, eventually it ALMOST worked. Then one day, it worked, and the old business process died never to be revived.
Now it sits in a slack channel, and I watch it doing work, responding to ambiguity, and taking feedback/edits all day. It's unreal. It's literal magic. It saves a HUGE amount of time and gave us a pattern to do more.
This is the real deal. It's not easy to find problems with the right shape, and it's not easy to build agents that fit even when you do... but once it clicks, it clicks.
But IMO the most fruitful thing for an engineering org to do RIGHT NOW is learn the tools well enough to see where they can be best applied.
Claude Code and its ilk can turn "maybe one day" internal projects into live features after a single hour of work. You really, honestly, and truly are missing out if you're not looking for valuable things like that!
Could this be an experiment to show how likely LLMs are to lead to AGI, or at least intelligence well beyond our current level?
If you could only give it texts and info and concepts up to Year X, well before Discovery Y, could we then see if it could prompt its way to that discovery?
> Good code is code that can be understood by a junior engineer. Great code can be understood by a first year CS freshman. The best code is no code at all.
This a thousand times. Having empathy for future devs, maintenance, and bug fixes is so important.
In this case, I really doubt even the most conservative justices believe "birthright citizenship means whatever an Executive Order says it does." At a minimum, we know they aren't signing on to the reasoning the 5 in the majority used. And then we can learn whatever they feel like saying in the dissent, but a dissent is just an essay with no force of law.