s/your point/this point/

> Citation needed.

You're responding to a thread that literally has 4 citations in support of your point, already. What more do you want?

Phone reception was not the issue in this case. They had printed the instructions and were working off paper copies. The issue was trusting the estimated journey time, which was waaaay off.

Any analogy that attempts to equate digital content with physical property is an automatic fail.

Block Google and bring back web rings, that's what I say.

The classic example being "draw a picture of a room without an elephant in it". https://medium.com/@avanib2826...

Erlang guarantees thread safety, doesn't it? At least, that's my understanding.

I think Ada does as well, but it's been a long time since I've used it and perhaps it requires certain coding constructs, rather than a general guarantee.

...says someone who doesn't understand the power and expressiveness of prototypal inheritance!


tbf It took me a while to grok it, but once you get it and start to use prototypal inheritance properly (instead of trying to fight it and force it to look like classic class-based inheritance) you'll find it a lot more rewarding.

Can I interest you in the 'hotdog' color theme?

Don't forget the original: 3 to 5, Leisure Suit Larry!

It may not be a bug in the LLM, but it *is* a bug in the robot.

I'm aware of that. However, I'm not sure this communication was either written for, nor aimed at mathematicians.

Found = Located by searching.

You could read it as meaning "discovered something no one else has discovered before", but that's adding an extra layer of interpretation on top of the literal reading.

That's not quite what code smell means. It comes from the common idiom that "something doesn't smell right" (https://www.englishidiom.com/glossary/something-doesnt-smell-right/) and in the context of code it refers to the feeling that an experienced developer gets when looking at a piece of code and can see that it 'looks wrong', without necessarily being immediately able to identify the specific problem. Possibly it ends up just being sloppy coding style, but often sloppy coding is an indicator of sloppy thinking, so there is a correlation, there.

Spotify is Swedish.