This is the way. 20 years ago, I got rid of an old Sony CRT that literally weighed as much as I did, and have had nothing but projectors since. Lots of complaints from the rest of the family around “it’s not bright enough”, and “it’s too complicated”, but hey ho.
I had a dive instructor who recommended snorting a bit of seawater if your nose was blocked and you couldn’t equalise. I’m not sure that’s good advice given the general contents of the sea, but it certainly worked :)
So I’m normally a command line fan and have used git there. But I’m also using sublimerge and honestly I find it fantastic for untangling a bunch of changes that need to be in several commits; being able to quickly scroll through all the changed files, expand & collapse the diffs, select files, hunks, and lines directly in the gui for staging, etc. I can’t see that being any faster / easier on the command line.
User Gary Koepnick asked the AI which person spreads the most information on Twitter/X—and the service did not hesitate in pointing a finger at its creator.
I’m a software engineer and I built a trebuchet during lockdown to launch Easter eggs at the neighbours’ gardens since we weren’t allowed to go see them.
Function/Method names, on the other hand, should be written so as to make the most sense to the humans reading and writing the code
Of course—that’s why we have such classics as stristr(), strpbrk(), and stripos(). Pretty obvious what the differences are there.
But to your point, the ‘intuitive’ counterpart to ‘zeroth’ is the item with index zero. What we have is a mishmash of accurate and colloquial terms for the same thing.
Most humans wouldd never write the word first followed by (). It absolutely should have been zeroth(), and would not cause any confusion amongst anyone who needed to write it.
doesn’t realise that Gemini is a GPT
Comments anyway.