From what I understand it cannot be used to perform work on contracts where the DoW is on the other side. [1]
In practice I would suspect companies with such contracts would play it safe by outright banning the use of Anthtropic products, even if they could technically be used for work on contracts with other parties.
> But I hope we can agree that you can't spec out something you have no clue how to build
Eh, of course you can. You can specify anything as long as you know what you want it to do. This is like systems engineering 101 and people do it successfully all the time.
Cool project, but I'm a bit curious hearing how the rest of the project feels about this?
I'm not sure how I'd feel if I woke up and found a system I worked on had been translated into an another language I'm not neccessarily familiar with. And I'm not sure I'd want to fix an non-idiomatic "mess" just because it's been translated into a language I'm familiar with either (although I suspect they'll have no problem attracting rust developers).
Are they though? I don't know what I expected, but to me they looked like nothing. Maybe they'd be more impressive if I'd read the transcripts but whatever.
This isn't my experience. Requirements tend to settle over time (unless they're stupidly written). Users tend to like things to stay the same, with perhaps some improvement to performance here and there.
But if anything, all development is the search for the search for the requirements. Some just value writing them down.
Early Facebook was inferior to local social networks in many ways. The real killer feature was convincing people to de-anonymize themselves on the internet.