> " This was my first ever project in Python, and in many ways, the start of my life as a programmer. The domino effect here is a little mind-boggling for me."

I can certainly relate to this. I started scripting for very obtuse reasons, and quickly started seeing things everywhere which I could apply a little code to and improve my life.

Is it possible you mean 'readings' from the monitor rather than 'lectures'?

If so that would be a very easy translation error to make. ('Readings' and 'lectures' can be synonyms, in the sense of someone knowledgable reading something out loud.) But it could just be me misunderstanding: sorry, if so.

"Let 'em whine until ninth" just didn't have the same ring to it.

I'd be more sympathetic to this response if the article didn't begin with:

> Yeah, you read the headline right. Ford has patented a system...

The fact is that it is not protected by a patent. That said, the fact that they are _trying_ to and investing in their attempts is indeed worth attention, as it indicates they think it's a good idea. Just without the sloppy reporting.

This comment was really helpful, and addressed many of my instinctive reactions too.

> "Conflict of interest All the authors declare that they have no conflict of interest."

Glad to see this in the original article. I had been wondering whether they were in the pocket of Big Crow.

I found your last paragraph entirely unambiguous at all three levels, which led me to disgree with your overall point. Before that I was with you!

The benefit of "The service is now ready. To check the service's status, ..."

Is when someone needs to amend this sentence later, e.g. inserting another point:

"The service is now ready. This means you can query the health endpoint. To check the service's status, ..."

It makes the writing less likely to become ambiguous.

Most documents I see in work will constantly have sentences added/removed as things change.

Many 'rules' including this one can be broken if you know the tradeoffs and can make the case-by-case choices correctly. But that was a poor example for motivating a behaviour.

The concept of 'gift' is inherent in the meaning of donation and has been understood that way for centuries: https://www.etymonline.com/word/donate#etymonline_v_31787

The listed features hardly seem like bloat!

> markdown import, templates, filename autocomplete, a Windows console version, numbered list items

And this is the problem with calling software bloated. Everyone has a different idea of what features are useful and what features just increase the size and complexity of the software without adding value.