They usually do. (The considerate and/or non-confrontational ones. There are always idiots, and people have the tendency to remember negative outliers and project their behavior on the group as a whole, which is unfortunate.) However, slowing down isn't the whole story. Riding a non-motorized bicycle is much easier if the rider can keep moving, however slowly, so it would be considerate in turn for the pedestrian to step aside and let the cyclist pass, if possible. A distracted pedestrian can be warned by a bell.

Separately, delivery riders as a category have an incentive to ride as quickly as possible, which is a recipe for conflict. Removing that incentive means removing or completely reimagining the service. I don't think that anybody has a solution or mitigation at present.

Depends. If one is aware of the meaning of section numbers, that "(5)" is very obviously suggesting that there is a file format named "crontab" which is documented. It's also pretty reasonable to suppose that the command and the file format of the same name are related.

A novice might miss the convention and the connection. Man pages are not quite novice material.

It would certainly help, but no economically feasible amount of auditing and best practices could lead to having a warranty on that software. My thesis is that our current understanding of software is fundamentally weaker than that of practical applications of electricity, so it makes no sense to present analogies between the two.

For an analogy to work, its underlying elements should have a relation to the target. Your analogy is not in the same universe. For electrical work, there is a baseline of materials and practices which is known to produce acceptable results if adhered to. For software, there isn't. (Don't tell me about the Space Shuttle. Consumer software doesn't cost tens of millions and isn't written with dedicated teams over the decades.)

It looks neat when you illustrate it with stacked boxes or concentric circles, but real-world problems quickly show the ugly seams. For example, how do you handle encryption? There are arguments (and solutions!) for every layer, each with its own tradeoffs. But it can't be neatly slotted into the layered structure once and for all. Then you have things like session persistence, network mobility, you name it.

Data formats have other sets of tradeoffs pulling them in different directions, but I don't think that layered design would come near to solving any of them.

Well, if you look up the histories of the time zones in the respective countries ("Time in Poland" and "Time in Spain" on Wikipedia, I have no reason to doubt their accuracy) you'll see that both settled on CET, with or without daylight savings, long before the EU was even an idea.

Which is nuance that will get overlooked or waved away by upper management who see the cost of hiring developers, know that developers "write code", and can compare the developer salary with a Claude/Codex/whatever subscription. If the correction comes, it will be late and at the expense of rank and file, as usual. (And don't be naive: if an LLM subscription can let you employ fewer developers, that subscription plus offshore developers will enable even more cost saving. The name of the game is cost saving, and has been for a long time.)

Of all the things, a "save-the-children prolegomena to the Prometheus myth" certainly wasn't on my bingo card today. So thank you for that, but I'm not aware of any reports of fire-keeping in the way you've described. Societies and religions do have sacred traditions related to fire (like Zoroastrians) but that doesn't come with restrictions on practical use AFAIK.

[1] https://web.archive.org/web/20260220083443/https://www.theat...

It's still possible to configure OpenLDAP via the slapd.conf file. The old roadmap called for ditching configuration file support in 2.5 IIRC, but it proved hugely unpopular so the file works to this day. The new configuration style is mainly useful for live updating of access rules and indexing.

That it does, but it doesn't leave much lubricant behind, which you need for a properly functioning chain. As you know, you want something that will get between the pins and rollers and stay there, minus the grime that would turn it into grinding paste. Which is probably why some people swear by wax, but that sounds like a giant hassle.

Why? There were other talented people who produced masterful works at an early age. From the same time as this there's a Dürer self-portrait, also aged 12-13:

https://en.wikipedia.org/wiki/Self-Portrait_at_the_Age_of_13

> We don't have any really reliable records from that time.

Uh, no. There's no documented attribution of that painting to Michelangelo; that doesn't mean that other things weren't reliably recorded.

Knowing the code and knowing how to make the code, or the interface to the code, comprehensible to another user, are different things. Just like with UIs, and the fact that an expert is not necessarily the best teacher.

Anyhow, the age of monumental feats of technical writing is past. Too expensive, and the subject is too volatile for the most part. Economics dictate that we'll have to deal with the cheapest possible docs. We already do.

That might work until an LLM encounters a question it's programmed to regard as suspicious for whatever reason. I recently wanted to exercise an SMTP server I've been configuring, and wanted to do it by an expect script, which I don't do regularly. Instead of digging through the docs, I asked Google's Gemini (whatever's the current free version) to write a bare bones script for an SMTP conversation.

It flatly refused.

The explanation was along the lines "it could be used for spamming, so I can't do that, Dave." I understand the motivation, and can even sympathize a bit, but what are the options for someone who has a legitimate need for an answer? I know how to get one by other means; what's the end game when it's LLMs all the way down? I certainly don't wish to live in such a world.

-L: skip preprocessing the input file. When opening rotated log files with the names like logfile.1, logfile.2... the default preprocessor on some distros will recognize them as man page source and helpfully pipe through nroff. If the file is largish this introduces an annoying pause. Using -L skips all that.

Ctrl-R as the first character of a search string will search for that literal string, not the regular expression. Nice if you have regex metacharacters in the search string and don't want to bother with escaping (and don't need the regex facilities, of course.)