9,258 karma · joined August 18, 2007
All ten outputs might be valid. All ten will almost certainly be different -- though even that is not guaranteed.
The OP referred to the notion of there being no manual; we have to figure out how to use the tool ourselves.
A traditional programming tool manual would explain that you can provide input X and expect output Y. Do this, and that will happen. It is not so clear-cut with AI tools, because they are -- by default, in popular configurations -- nondeterministic.
What are the productivity gains? Obviously, it must vary. The quality of the tool output varies based on numerous criteria, including what programming language is being used and what problem is trying to be solved. The fact that person A gets a 10x productivity increase on their project does not mean that person B will also get a 10x productivity increase on their project, no matter how well they use the tool.
But again, tool usage itself is variable. Person A themselves might get a 10x boost one time, and 8x another time, and 4x another time, and 2x another time.
I think that's very important.
Never mind six months; with AI, "you" can "build" something small and useful that works in six minutes. But "you" almost certainly didn't learn anything, and I think it's quite questionable if "you" "built" something.
I have found AI to be a great tool for learning, but I see it -- me, personally -- as a very slippery slope into not learning at all. It is so easy, so trivial, to produce a (seemingly accurate) answer to just about any question whatsoever, no matter how mundane or obscure, that I can really barely engage my own thinking at all.
On one hand, with the goal of obtaining an answer to a question quickly, it's awesome.
On the other hand, I feel like I have learned almost nothing at all. I got precisely, pinpointed down, the exact answer to the question I asked. Going through more traditional means of learning -- looking things up in books, searching web sites, reading tutorials, etc. -- I end up with my answer, but I also end up with more context, and a deeper+broader understanding of the overall problem space.
Can I get that with AI? You bet. And probably even better, in some respects. But I have to deliberately choose to. It's way too easy to just grab the exact answer I wanted and be on my way.
I feel like that is both good and bad. I don't want to be too dismissive of the good, but I also feel like it would be unwise to ignore the bad.
Whoa hey though, isn't this just exactly like books? Didn't, like, Plato and all them Greek cats centuries ago say that writing things down would ruin our brains, and what I'm claiming here is 100% the same thing? I don't think so. I see it as a matter of scale. It's a similar effect -- you probably do lose something (whether if it's valuable or not is debatable) when you choose to rely on written words rather than memorize. But it's tiny. With our modern AI tools, there is potential to lose out on much more. You can -- you don't have to, but you can -- do way more coasting, mentally. You can pretty much coast nonstop now.
Whereas this system appears to emphasize a programmatic description of the music.
Of course, with MIDI, there's that underlying programmatic description, and you could use various means to work with MIDI in a more programming-style if you wanted, but I for one have mostly generated music either through playing an instrument, or sometimes through exporting music notation files (Sibelius, Dorico, etc.) to MIDI files.
To me, the idea of programming the timing and duration and intensity and so forth of a note from scratch seems like it would be harder and less enjoyable to do than to just play the note on a keyboard -- even if I turned around and applied some MIDI transforms to clean it up. But for someone who doesn't play music much, and is good with programming, this coding approach might prove easier.
Individual results may vary, but it seems credible that thoroughly learning and using an editor like Vim or Emacs could yield a 2x productivity boost. For the most part, this has never really been pushed. If a programmer wanted to use Nano (or Notepad!), some may have found that odd, but nobody really cared. Use whatever editor you like. Even if it means leaving a 2x productivity boost on the table!
Why is it being pushed so hard that AI coding tools in particular must be used?
Yet programmers who have used Nano were not (at least not significantly) scoffed at or ridiculed. It was their choice of tool, and they were getting work done.
It seems unclear how much more productive AI coding tools can make a programmer; some people claim 10x, some claim it actually makes you slower. But let us suppose it is on average the same 2x productivity increase as Vim.
Why then was using Vim not heralded from every rooftop the same as using AI?
It doesn't matter if you're using AI or not, just like it never mattered if you were using C or Java or Lisp, or using Emacs or Visual Studio, or using a debugger or printf's, or using Git or SVN or Rational ClearCase.
What really matters is in the end is, what you bring to market, and what your audience thinks of your product.
So use all the AI you want. Or don't use it. Or use it half the time. Or use it for the hard stuff, but not the easy stuff. Or use it for the easy stuff, but not the hard stuff. Whatever! You can succeed in the market with AI-generated product; you can fail in the market with AI-generated product. You can succeed in the market with human-generated product; you can fail in the market with human-generated product.
The point being just that, yeah, there are some jobs that need people present all the time. Sad but true. If you feel you are being singled out in some unjust way, discussing it with management or HR or whomever seems appropriate. If you just somehow got picked at random, it would be reasonable to ask to switch -- maybe you can volunteer for the next holiday -- but a lot of people expect Christmas off, regardless of personal beliefs, so there might not be anyone willing to trade. :-)
I could answer that nobody is forced to be a programmer. Most of us cannot manage to get any money for standing on the street and making faces. But we are not, as a result, condemned to spend our lives standing on the street making faces, and starving. We do something else.
Why can't AI add the polish and features also?
And then, it seems to be a real issue amongst some people to ask, "why should I learn X, when LLMs already know it?" Not unlike, "why should I learn to divide, when we have calculators?" but on a grander scale.
Or is it because LLMs know everything that is in books, so people don't feel compelled to learn any more themselves?
If all AI was suddenly wiped off the face of the earth, humans would rebuild it, and would carry on fine in the meantime.
One AI researcher decades ago said something to the effect of: researchers in biology look at living organisms and wonder how they live; researchers in physics look at the cosmos and wonder what all is out there; researchers in artificial intelligence look at computer systems and wonder how they can be made to wonder such things.