Misunderstanding is where I’d put the dividing line between style and grammar, or at least useful grammar.
I didn’t know anyone cares how I pluralise emails though; I’ll be making sure to include the ‘s’ from now on though, maybe I can use it to literally get some nob-heads to reveal their true nature.
Marathon is a pretty old tech mode of travel - not sure we really need robots to take on heritage tasks.
Let me know when they’re faster than the train from Beijing to Nanjing.
Over most distances that most tortoises actually want to travel, I suspect they’re not much slower than a jet.
Tortoises hate being asked to open their shells by airport security.
Do you notice people misunderstanding you? That’s how you’d know.
If you are not getting feedback from your readers, then fair enough, you’ll never know; but in that case, how do you even know anyone is reading your writing?
I tend to think my grammar its like a tree falling in the woods, the few squirrels that notice it can probably find another tree to harass.
training dataset
Yep. I’m sure its fine in small competent teams with a workflow that they’re comfortable with.
But any large organisation I’ve worked in involves clueless middle managers and teams with some people who really should move on. Agile seems to make incompetence of managers less obvious, and makes them less accountable. Seems to remove control over both the workflow, cost base and the quality of product/service.
It also gives them this great universal technique for problem solving. “We found that Task X is not being done right” . OK we’ll write a job title “X doer”. Appoint person who doesn’t really know what X is, but neither does the interviewer. Make this person go to ‘stand ups’ and assign them some jiras. 3 months later, they wonder why X is still not being done and why their new hire left already.
The root cause for sure is incompetent management not the methods. But their project method seems to protect them and impair actual improvement.
I think I noticed it widespread in the mid 2010s. Maybe around the same time that DIY and various hobby/handicrafts became just “making”.
I still remember when I bought a tool off someone and was chatting about what i was going to do with it and they declared out of the blue: “I am a maker!”. I just had to end the conversation as quickly and politely as possible. I don’t know what the point of that statement was, but it made them sound a bit unhinged.
That said I’m sure the term coding was in use before, but more like a sub-activity that ‘computer programmers’ or ‘software engineers’ might do as part of their job. Maybe ‘coder’ and ‘coding’ became more popular with the spread of the term ‘agile’ into the bullshitting-consultant / middle-management cultures; I think that’s when some people started using that term as an excuse for skipping ‘design’ and ‘engineering’ parts of any complex project.
Yes, I reckon that mutual sensitivity between parties is more important than any rules.