That page's source has MS Word 9 metadata embedded in it. Part of this metadata is an <author> attribute. The name of that author is the same as the director for this film on imdb.
For that scenario to be possible, general AI needs to be developed first.
A huge (and awful) part of software engineering is figuring out what exactly the stakeholders want you to build or fix. Sometimes, they themselves don't even know.
Dealing with ambiguos jira tickets, poorly reported bugs, non-existent requirements, missing or outdated documentation; these are the "common problems" in building software. Current AI technology isn't even close to being able to sort these types of problems today, and it won't be until a monumental breakthrough in the field is achieved.
Generating art is "easy" in the sense that art can't be wrong or right, it just is.
Generating the backend of a streaming platform? I'd like to live long enough to see it.
A month from now a new vaccine-escaping variant could emerge from some squirrel in Haiti that's a billion times more transmissible than Omicron and a thousand times more lethal than Delta.
The fact that this particular variant isn't an absolute catastrophe doesn't mean that a new devastating variant isn't around the corner.
>Whereas when you're reading code for correctness, you're just following the logic that's already there. If it works, it works. How could it possibly take longer than the whole creative process of coming up with it...?
That's exactly the problem. If you "just follow the logic" you can miss important details or edge cases that you would be forced to deal with by coding it yourself.
I wouldn't mind using something like this for mundane tasks, but I would be very careful with these tools while developing high performance code intended to run on specific hardware.
Asking for stuff requires no talent, vision, discipline or effort whatsoever. Pretty much anyone can do it. If you don't actually deliver, you don't actually matter.