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.
Any conversation
I started bloggingโฆ again
mataherry.bearblog.dev
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 on a kick lately of trying to visualize the oscillating clock, and ultimately the effectively arbitrarily complex activity of a computer processor, as modern refinements of the line shaft factory of the 19th century. Of compute as being not much more than profoundly refined "work" delivered by the electrical grid into marvelously complex machines.
Does that, as a metaphor at least, feel as important to you as it has to me of late? We spend so much time in a world abstracted.
ๆ
ไบ็ๅผๅคดๆปๆฏ่ฟๆ ท๏ผ้้ขๅ
ถไผ๏ผ็ไธๅ้ฒใๆ
ไบ็็ปๅฑๆปๆฏ่ฟๆ ท๏ผ่ฑๅผไธคๆต๏ผๅคฉๅไธๆนใ๏ผby ๅผ ๅไฝณ ใไปไฝ ็ๅ
จไธ็่ทฏ่ฟใ๏ผ
Stories always begin this way: a chance encounter, completely unexpected. Stories always end this way: two flowers bloom, then drift apart. (by Zhang Jiajia, I Belonged to You)

