Nice.

Cool, you can say bad things about Trump.

Now say something bad about Xi Jinping. You can't do it. You are a slave, not human.

The problem with living in an authoritarian state, it's impossible to take an economics class based in science.

If you had learned about economics, you might have learned about "dividends" and "regulations based on rule of law."

Inflation is great for making people feel rich.

Makes me want to play that alien flute.

Tea. Earl Grey. Hot.

You literally can now, that was one of the first things changed by Elon.

Go to Twitter and click on the "Following" tab. It even remains selected between visits, so you don't have to see the AI shovelware unless you click on the other tab.

The enshittification continues. Ruin things in the name of profit.

The uncomfortable truth is that a significant portion of the population prefers the enshittified feed, otherwise it wouldn't be profitable.

The Reddit algorithm is really weird anyway. It is an illogical mix of "recent" and "popular" that sometimes includes things that are neither recent, nor popular.

For programmers, you need to be able to get the computer to do what you want it to do (with code).That is the baseline. There are other things that can be learned, but without that baseline, I'm going to need to review literally every line of the candidate's code (if they get hired), and I'd rather not do that.

Apple usually won't offer something until it's figured out enough to be done right, while others will rush hokey implementations early to be first.

It depends on what I'm trying to determine. If I'm trying to determine if they can use AI, then yes I will let them use it.

If I'm trying to determine if they can think (or control the computer), probably not. If they are having trouble, one of the interviewers can pretend to be AI and give answers. In the past I've had one of the interviewers pretend to be auto-complete, since the candidate depended on that, and I care if they can logic, not if they've memorized all the function names.

I have to use Wayland, you insensitive clod!

On the other hand, you the future Social Security recipient, will get increasingly taxed because you made the U.S. unwelcoming for immigrants and migrants. What precisely is it that you object to? Them coming here and working their tails off, raising families, paying taxes, etc., essentially acting like good citizens.

But maybe we're fucking Christian Nation, able to look a poor migrant in the eye and tell them to enjoy the Love of Jesus Christ on their own because they won't be getting any of it from you.

I wouldn't say clients never have clue about requirements. They do have some clues but are unable to express them using the right language and sufficient detail.

Once in a previous life I did process controls. I was given a pipe expander, think a piston with a mushroom head that can expand; the head is slid into a pipe, expanded, and then slid further, expanded....until the pipe had all its joints tested by the expander. I did the controls (motor, sensors, etc.). What I got from our salesman was "deficient", he clearly only knew we could sell such controls. We had meeting the customer's engineers. One fellow there seemed to be the lead.

After pages of notes on what we were to supply, I told him I would write up an operation document and send it to him. He was free to change it in any way he felt necessary. In our next meeting, he had a few corrections but admitted it was well written. My observation was it takes two to tango. If you are producing something blind without customer buy-in on what the thingy is supposed to do, then you will get the impression the customer doesn't have any requirements clue, when in fact you do not have any requirements clue and you produced a widget blindly.

It is not enough to get a requirements document from the customer, you must write the requirements document you require and then ask them to analyze it and makes changes as they see fit. If they shovel in extra crap in that first round, you now have the ammunition to tell them that was not what they originally asked for and you must have another meeting with them. Once they get the idea that these meetings will continue with no actual work being done on their widget, they'll get the idea they should stop asking for extra crap, especially if your side puts extra dollar amounts to that extra crap.

Also, getting the customer to agree on the operation of the widget gets them to think in the level of detail you require and to think about their new widget will operate in edge cases. They become reluctant to ask for changes after that because they have signed up for the operation (so to speak).

I give a coding interview to determine, "Can this candidate get the computer to do what they want?" Coding problems are a quick way of determining that. Of course, I could give them a month long task and see if they can complete that, but no one will tolerate that.

If a person can't manage to give reasonable, logical instructions to a computer, the LLM isn't going to help.