Communists were also not thinking "hahaha how evil we are, let's do GULAGs!" they wanted happiness for everyone, but look where it went.
The thing is - it always goes there.
The only docs that explain what code does are a carbon copy of the code.
I've saw that "no-code, write docs, write spec" movie so many times, and it always ends as a flop in the box office.
It will never work. Code is the documentation.
The difference between Code -> IR -> binary is that the transition is deterministic.
Doc -> Code is non-deterministic asf. And will never be.
The only reason it works and we have senior, middle, junior engineers is the fact that assumptions on that path that senior engineers make are better than the ones junior engineers make.
LLMs cannot make any assumptions though, as they have zero real world knowledge and thus zero common sense.
> We observed that participants who had access to the AI
assistant were more likely to introduce security vulnerabilities for
the majority of programming tasks, yet were also more likely to rate
their insecure answers as secure compared to those in our control
group.
It takes >50 seconds to generate these schemas for some pretty simple use-cases with large enums, for example.
Imagine that latency added to each request...
Not really, it's just like counting: awk, grep, sed, uniq, tail, etc.
"CloudOS" is in it's early days right now.
You need to be careful on what tool or library you pick.
In my experience all questions I've had for AWS were:
1. Their bugs, which won't be fixed in near future anyway.
2. Their transient failures, that will be fixed anyway soon.
So there's zero value in ever contacting AWS support.
