Two plus two

Over the last few months I’ve been trying to explain to myself why I feel I shoudn’t be using LLMs. That reminds me how some 15 years ago I was doing the same about search engines. (I’m using them from time to time, however it’s important for me to outline the borders: where I could rely on them, and where I wouldn’t want to. More on this in another post, it’d be interesting to see in retrospective.)

I settled on two arguments:

  • They degrade our own mind
  • They’re bad for the environment (as if the climate problems weren’t gross already)

As the mind degradation progresses, the environment effects will worsen, because we will need LLMs for even simpler tasks, and thus consume more power, water and whatever else they’re hungry for.


I often see people comparing the advent of LLMs to the industrial revolution with its advent of machines for manufacturing, and it’s indeed tempting to do so. But there’re two reasons why I think comparison is incorrect and misleading:

  • Using machines for manufacturing frees people from doing the same specific routine over and over again. Instead of spending time doing routine, we started inventing mechanisms, technology, algorithms and software to automate that routine, learning along the way. This is certainly good. It does not thwart craftsmanship because hand-made stuff is still valued, and producing things by hand at volume is very different from the art of craftsmanship anyway. Now, LLMs lure us into delegating this creative engineering activity to the machine. And we’re back at routine, no learning. Full cycle. (No, “reviewing” does not count, because to be able to do a useful review, you should be doing stuff on you own).
  • A machine does precisely what it’s engineered / programmed to do, and that’s truly automation. We have control over it. Well, I do not possess immediate total control over a device built by some engineer in some corporation, but at least I know that somebody has that control. I could have it, too, if I absolutely needed โ€“ by learning that area, by becoming an employee of that corporation, or by other relevant means. There’s absolutely no control in the case of LLMs. Even if you own the data, even if you trained the model yourself (heh), even then you cannot tell for sure how it does this and that. Its functioning is indeterminate. Sometimes it succeeds, sometimes it fails. You cannot track its decision-making and fine-tune it.

Posted in writings | Tagged | Leave a comment

Hockney! ๐Ÿ’”

Posted in art | Leave a comment

Modern tech hate-list

In random order:

  • Video auto-play. I even disable media auto-download in messengers, and you throw those moving pictures at me!
  • Well, the most dreaded thing is zoom-in in Safari on iOS, for two reasons. First, it randomly jumps at some point, right when I look into the detail I was zooming to look into. Second, on some (many!) sites it just crashes the page, just that.
  • Recommendations. No-no, thanks.

To be continued, I guess.

Posted in Uncategorized | Tagged | Leave a comment

Attitude

I think that “AI slop” is not only generated stuff, but also most of the human talk on the topic. If you want a drop of sanity in this ocean – be sure to check Ed Zitron, he has great podcast and videos, like this one.

And yes, I was tempted to spell the title as AIttitude, but this word-play already looks like a bad taste.

Posted in Uncategorized | Tagged | Leave a comment

Fun fact of the day

macOS just silently ignores network proxy settings when VPN is on. Too bad.

Posted in Uncategorized | Tagged | Leave a comment

A novelist programmer

(This was written sometime in 2014)

It’s not hard to see analogy between a writer and a computer programmer. Both have a concept which they materialize in their work. Design and architecture are plot. Phrases are statements. Chapters are modules. Syntax is the rules which make the text readable (both by humans and machines). It’s not hard to observe analogies between a reader and a computer programmer, too. Although it’s not common to just read the program code for pleasure, it’s rather common to read it for knowledge.

Let’s imagine a book with a complex plot. It has a lot of intricacies, it’s long and twisted. The same could be said about a complex program. Writers of both need to understand the concepts behind them deeply. A thorough investigation is needed to gain deep understanding of their views and intentions. This requires time, experience and good memory. One has to “dive” into the book or program and stay for a long time there.

While it’s not very practical to modify the existing book, modifying a program is often desired and/or needed. This is where the processes differ, but the distinction is not harmful for our discussion. The distinction is natural — a book is a finished product or art object which expresses someone’s thoughts and opinions, while the program is basically a tool which is expected to be improved after its creation. This difference should be reflected in the works themselves. A book can be of any structure, while the program should be readable and understandable โ€“ that is, easy to maintain.

By now, we were talking about what we called “complex” narrations. But there can be a collection of short novels, possibly united by means of some literature techniques. A reader is generally not expected to read through all the book from the first page to the last, but rather she could open it at any page and start reading. The novels could be treated as parts of some bigger entity, but nevertheless they are somewhat independent of each other. Returning to the programming, it should be easy to understand isolated modules, and after that a programmer is ready to change whatever she wants. Such modifications could be called “short-term tasks”, which do not require the understanding of the whole system.

It’s different with “long-term tasks”. In case of complicated work one has to follow all the turns of the author’s thought and create a detailed “map” in their head. This often makes the reading interesting, but absolutely does not suit when the goal is practical — that is, not an entertainment. Digging into such work will be time-consuming and sometimes just boring. But it is required. Contrast this with learning a system step-by-step, by gathering knowledge of different parts and then integrating them in the head and thus seeeing how they are interconnected and interact with each other. The progress can be seen immediately. Of course, to make a big change (like altering the concept of a whole book) one still has to learn everything, but that is just an increase in scale. Small changes can be done instantly.

That is, we can say that a good program is similar to a collection of short novels or to a good-structured educational material.

Posted in writings | Leave a comment