You have to stop thinking about it as a computer and think about it as a human.
If, in the context of cooperating together, you say "should I go ahead?" and they just say "no" with nothing else, most people would not interpret that as "don't go ahead". They would interpret that as an unusual break in the rhythm of work.
If you wanted them to not do it, you would say something more like "no no, wait, don't do it yet, I want to do this other thing first".
A plain "no" is not one of the expected answers, so when you encounter it, you're more likely to try to read between the lines rather than take it at face value. It might read more like sarcasm.
Now, if you encountered an LLM that did not understand sarcasm, would you see that as a bug or a feature?
I would not understand the last two sentences. Sidle? Tromp? I don't think I've seen these words enough times for them to register in my mind.
"Strode", I would probably understand after a few seconds of squeezing my brain. I mean, I sort of know "stride", but not as an action someone would take. Rather as the number of bytes a row of pixels takes in a pixel buffer. I would have to extrapolate what the original "daily English" equivalent must have been.
- Hosting a website is not so easy for the average person, even the tech savvy person, specially if you try to learn it now using the way large websites are developed.
- Static site blogs lack interactivity: people can't comment on your blog. You have to post a link to Twitter or HN (here!) and interact with people over there.
- Static site blogs also don't usually let people "subscribe" by email or whatnot, so unless people bookmark your website or follow you on Twitter, they are not going to find your content.
P.S. this is a problem area I'm trying to work on, at least on the technical front.
Nice story but the places I've seen that make use of services, there's never a "1 server -> 1 team". It's more like 20 services distributed among 3 teams, and some services are "shared" by all teams
twitter: hasen_judi