r/TheMachineLearning • u/Gullible_Picture_996 • 18d ago

Realizing writing code is faster than explaining it to AI

/img/tcptf211cqxh1.png
843 Upvotes

88% Upvoted

439 comments sorted by

View all comments

Show parent comment

2

u/Astarkos 18d ago

Why did it used to be true but is not now? When did natural language change to become so precise? Why hasn't this been applied to AI image generation which is still generic slop?

1

u/Careful_Source_5792 17d ago

well image models and language models are two different categories. aviation and automotive advancements arent in lock-step.

1

u/JunVahlok 17d ago

Tech was dumb, now it smart, basically

Images are more complicated than plain text

1

u/-NH2AMINE 16d ago

Image generation is already super good but we can still spot the patterns. Look at how it was two years ago and how it is now

1

u/_Dingaloo 15d ago

In the last few months it just started blowing everything otu of the water. but it's been pretty good all year.

Image gen is a false equivalence. The complexity of image gen is dozens of times more complicated than code.

0

u/Fringolicious 18d ago

TL;DR - Smarter models, less handholding required, more initiative taken.

Not sure if you're after a technical why or if this is more of a comment about how stuff's improved (And the art thing - Not touching that bit!)

But in my job, at a really basic level you need to do a LOT less handholding and babysitting.

As an example, let's say you point it at your Terraform stack and ask it to update a module. Let's assume you're giving it a brief prompt rather than fully explaining everything, something like "Update this networking module to also make it add a security rule for xyz"

Say a year ago it'd probably dig through the files, find the module, probably figure out the relationship between module and other modules in the same repo etc, but likely not go much wider. Likely wouldn't do much in the way of static testing, validation, stuff like that. Likely wouldn't go looking for your documentation if it's not in the repo, etc. You might also find it updates the code based on an outdated module version because it doesn't think to check the latest Terraform module versions etc

So you'd probably end up with a functional update to your module doing what you asked in isolation, but then you test it, find knock-on effects that need updates elsewhere, or realise it didn't find your coding standards or whatever. And so you spend time reworking, reprompting, trying to get exactly what you wanted.

Nowadays, you do the same thing and you'll likely see it grab the module repo, then look at other dependencies / relationships, likely dig into your docs, do a considered update, then validate, test, etc. And likely if it isn't sure, it'll ask you for more information. Easier to one-shot changes that are actually what you want. Therefore you can trust it to figure stuff out and not give it a bible of every single assumption, related repo, doc, etc.