Been using Devin for a few months now, for Typescript and Python.
I've never seen it check-in uncompilable code, but watching the Devin console I can see it building and using the code to ensure commits are not complete garbage. When it has checked-in compilable and almost right but slightly wrong code, automatically running lint and tests (it doesn't always run them before checking in) from ci triggers it to push a fix on its own.
Feedback loops are nice, but they can be expensive, and time consuming (oh look at me complain that it takes Devin a whopping 15 minutes to complete a task) so I can definitely see the value in type constraints.
The way I've heard the CAP theorem used practically at a high level is to frame the question as follows:
What happens in the case of a (logical) network partition? - an AP system continues taking requests and provides eventual consistency, while a CP system waits for the partition to go away, or says come back later.
10 bucks says the lesson learned will be "remember kids, always set -u (and other good ideas, like set -e, set -o pipefail, and personally I like set -o posix but you'll need to give up process substitution for that)."
One unique advantage Palantir would have over Facebook is that if you get the itch to travel, Palantir casts a much wider net throughout the world (assuming you'd be willing to work as a forward deployed engineer, which in Palantir's case is genuinely not a sales role).
Some people want to see healthy EPS growth, and as you point out some patient investors are willing to buy the "reinvesting in accelerated growth" thesis.
But everyone is getting tired of AMZN's lack of transparency. Increasingly, buying AMZN is akin to buying the "Bezos is the next Jobs" meme on faith.
I've never seen it check-in uncompilable code, but watching the Devin console I can see it building and using the code to ensure commits are not complete garbage. When it has checked-in compilable and almost right but slightly wrong code, automatically running lint and tests (it doesn't always run them before checking in) from ci triggers it to push a fix on its own.
Feedback loops are nice, but they can be expensive, and time consuming (oh look at me complain that it takes Devin a whopping 15 minutes to complete a task) so I can definitely see the value in type constraints.