AuDHD is ASS sometimes omg
Any conversation
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
Economist Lant Pritchett describes shifts in ideas as silly, controversial, progressive, then obvious.
Also:
"Radio has no future. X-rays are clearly a hoax. The aeroplane is scientifically impossible." - Lord Kelvin
". No wireless. Less space than a nomad. Lame." - CmdrTaco
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.




