I’ll take one of each, please.

I don’t care what you say, the Apple store circa 2001 is iconic and definitely has that “lickability” factor that Jobs loved so much about the original OS X’s Aqua UI.

When did code reviews become this weird?

Mastodon often feels to me more like Facebook for software developers

I wish. I’ve tried to curate mine as such.

My mastodon feed is awash in spam from authors hucking their LLM generated stories. Constantly. And random low viewer count streamers spamming hashtags every hour 24/7.

It’s crazy how much LinkedIn-like sociopathy is out there right now. Makes sense given the huge spike in new accounts we’ve had in the last month.

Not OP, but generally the arguments I’ve been told are:

Microsoft is an abomination (true).

“Don’t make me explicitly state types; it is too confusing!” Installs 20 libraries including fucking pad left to eek out basic functionality.

Strongly typed haters are right up there with curly brace haters.

From Ellen Ullman’s Close to the Machine:

"The project begins in the programmer’s mind with the beauty of a crystal. I remember the feel of a system at the early stages of programming, when the knowledge I am to represent in code seems lovely in its structuredness. For a time, the world is a calm, mathematical place. Human and machine seem attuned to a cut-diamond-like state of grace.

…

Then something happens. As the months of coding go on, the irregularities of human thinking start to emerge. You write some code, and suddenly there are dark, unspecified areas. All the pages of careful documents, and still, between the sentences, something is missing.

Human thinking can skip over a great deal, leap over small misunderstandings, can contain ifs and buts in untroubled corners of the mind. But the machine has no corners. Despite all the attempts to see the computer as a brain, the machine has no foreground or background. It cannot simultaneously do something and withhold for later something that remains unknown[1]. In the painstaking working out of the specification, line by code line, the programmer confronts all the hidden workings of human thinking.

Now begins a process of frustration.

[1] clarifies how multitasking typically works, which was usually just really fast switching at the time of the book.