I treat AI like a really new junior dev. it rarely does what I want the first time. however I've started making it give me plans as documents and then have it implement from the document. like, design a database schema with uml diagrams and then write the migrations and such. create the openapi spec before creating the API. it works decently well while also making sure there is good documentation for future me.
Discussion
I use it similarly. I often use it to probe ideas and make outlines before I begin working. Like I have an app idea. I'll give it my requirements and ask like what kind of data structures COULD I use and what should I actually use for this and why. And tell me the reason I would and wouldn't use the other types. then I make an informed decision on how to proceed myself. Without AI I would be doing the same thing except I'd have to read a lot more documentation.
this is pretty much what I do too. glad to hear I'm not crazy! what about languages? do you think it does better writing JavaScript vs golang, for example?
It's pretty good at most languages I find. the smaller you can make the task, the better results you'll get. I find myself mostly saying, "no, don't add that dependency" or "this code is redundant" when it's wrong. It's barely ever a syntactic failure. Generally speaking though, I find the more adoption the language has, the better the ai is with that language. So it's probably a lot better with javascript and python than it is with golang. But with good direction, it's just fine with go. But you can do lower level things with go, so you have to actually understand data structures and algorithms before you implement something that just doesn't work well for the intended purpose.
Questions? Suggestions? You can find me on signal for quick response:https://signal.me/#eu/9tZRWI5zBR2OOWfO138D16oBl78C1KOSZ9dbjPN:_4CvRqKkBAu1PFqOlzsQsELeC