Theory reuse > code reuse almost every time.
Any conversation
spiral
for(y=-5;y<5;y++){
s=""
for(x=-10;x<10;x++){
r=Math.hypot(x/2,y);a=Math.atan2(y,x/2);s+=" .:*#โ"[((r+a*2)%5+5)%5|0]
}
console.log(s)
}::.........:::***##
.. ...::**##
######## ..::**#
###********# ..::*#
#**:::...::*# ..:**#
. ##**::. ..::**##
##**:.. #*::***##
##**:.. ######
. ##**::... ...
. ##***:::......:::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.
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.
again. Was in the middle of some timeline experiments, sorry if it appears weird rn. www.githubstatus.com



