They're also bad at that though, because if you don't know that stuff then you don't know if what it's telling you is right or wrong.
The reason it goes down a “really bad path” is that it’s basically glorified autocomplete. It doesn’t know anything.
Not quite true - GitHub Copilot in VS for example can be given access to your entire repo/project/etc and it then "knows" how things tie together and work together, so it can get more context for its suggestions and created code.
I've found it to be great at writing unit tests too.
I use github copilot in VS and it's fantastic. It just throws up suggestions for code completions and entire functions etc, and is easily ignored if you just want to do it yourself, but in my experience it's very good.
Like you said, using it to get the meat and bones of an application from scratch is fantastic. I've used it to make some awesome little command line programs for some of my less technical co-workers to use for frequent tasks, and then even got it to make a nice GUI over the top of it. Takes like 10% of the time it would have taken me to do it - you just need to know how to use it, like with any other tool.
Sounds like you just need to find a better way to use AI in your workflows.
Github Copilot in Visual Studio for example is fantastic and offers suggestions including entire functions that often do exactly what you wanted it to do, because it has the context of all of your code (if you give it that, of course).
"Using something that you're not experienced with and haven't yet worked out how to best integrate into your workflow slows some people down"
Wow, what an insight! More at 8!
As I said on this article when it was posted to another instance:
AI is a tool to use. Like with all tools, there are right ways and wrong ways and inefficient ways and all other ways to use them. You can’t say that they slow people down as a whole just because some people get slowed down.
Just like Stack Overflow then haha. It's usually either
"I copied this persons code exactly, why doesn't it work in my completely different codebase?"
or
"I copied this persons code exactly and it works in mine! I don't want to touch it in case I break it cause I don't get it"
haha
If you already know what you’re doing, AI generating code is redundant.
Nah, it can be really useful for people who do know what they're doing as it can be used to generate the "charlie work" (IASIP reference if you don't know) things like unit tests and documentation and things like that pretty damn well.
Sorry but a study of 16 developers isn't a big enough sample to get any meaningful data, especially given the massive range of skills and levels of development.
I'm a developer and I use AI - not much, but when I think it can help based on the suggestions that it gives me since it's integrated into visual studio. It doesn't slow me down, it speeds me up. It could slow you down if you rely on it to do everything, but in that case you're just a bad or lazy developer.
AI is a tool to use. Like with all tools, there are right ways and wrong ways and inefficient ways and all other ways to use them. You can't say that they slow people down as a whole just because they slow some people down.
and b. this data is easy to rebuild over time.
You say that, but some shows and movies are getting very hard to find these days. I lost one show to an external HDD that died, and I have never been able to find it again :(. That's part of the reason I recently went to a DAS in my setup instead of a NAS - backblaze backs the entire 40TB DAS up for ~$90 a year!
You got them all in uncompressed 8K or something!? How on earth does it take up that much space?
Ok so you definitely don't understand how DLSS works lol.
DLSS has to be implemented by the developers of the game. They literally have to use the DLSS APIs in their game code. DLSS requires things like the player input and motion vectors for all scenes, materials, and objects that are in the frame. It adds time to the rendering pipeline. The more powerful your GPU the less rendering time it adds.
We're getting way off track now anyway, so to go back to the start: DLSS Super Resolution is amazing because it lets you get a framerate bump with either little-to-no visibile change to IQ, to a very noticeable degradation of IQ depending on how much of a framerate bump you get. It is one of the most significant advancements in gaming this century IMO.
On my PC with a 4070 Super, I can play COD BO6 at a near locked 120fps on my 4K 120hz VRR tv at "4K" using DLSS, whereas my PC definitely cannot do that without DLSS. It looks like native 4K, and believe me I've taken many screenshots and compared them at 300% zoom lol.
They're tools that can help a junior engineer and a senior engineer with their job.
Given a database, AI can probably write a data access layer in whatever language you want quicker than a junior developer could.