Markdown really sucks, I'll grant you that it's useful, there's no doubt about that but the lack of a standard, and the fact that no two markdown convertors do the same thing is terrible.
In this article I argue that monolithic GitHub projects, inflexible organizational structures and sequential programming languages all lead to bad software architectures.
For program that have to be maintained the opposite to the last scenario is true. The inputs to the program and the program itself must be beautiful and well-documented.
If a web site powered by PHP fails to work because it can't connect to a SQL database I don't want to know - really, I don't want to know, I am totally uninterested in this.
It should provide a heck of a lot of information, which should be put into a permanent log file, and from which it should be possible to do a post-mortem debugging of the program to see what went wrong.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.