I am kind of saddened by technology in general that we need LLMs to deal with it in the first place.

It used to be that you compiled an executable, copied it onto the target computer and it worked. Then came servers, where you had to open some ports, set up some init scripts, maybe a db connection string.

This has evolved into a fractal of awfulness of a myriad of options and problems, each of which more elaborate and specifically limited than what came before, so you can't really use any one of them, but a combination, which is bound to interact weirdly, giving you some unique problems.

LLMs are great at solving these kinds of problems, but these problems should not exist in the first place, and they just waste everyone's time.

When it comes to actual meaningful product questions (and not just 'how/where does this code run'), LLMs are basically next to hopeless.

Since LLMs are very good with dealing with the BS, I hope they'll be useful in making people recognize and do away with BS altogether, and we can go back to the simple olden days.

Software's always been painful to run and use.

>It used to be that you compiled an executable, copied it onto the target computer and it worked.

Java had been marketed last century as a 'write once, run anywhere' language. Tells you a lot about how portable executables in other languages were.

Just branch to the first instruction, and let it take it from there. The shackles exist but in your mind.