Any conversation
Sigh. On the heels of , I just went into our garage to find a panel of insulation fallen to the ground, riddled with mouse droppings. ๐คข๐ซ
Cleaned it up (gloved and masked, naturally), but probably means we need to re-insulate the whole garage. Which will undoubtedly uncover a leak or some other issue. The fun never ends!
"If you don't think of yourself years ago as an idiot... Perhaps it is because you still are one."
In that spirit I started to write down my own thoughts. I think I am meant to call it a blog. Years from now I can read my old words and cringe at them.
www.gruntsoft.com/words/
mandelbrot
for y in range(10):
s=''
for x in range(25):
a=[]
for q in range(2):
z=c=x/25*3-2+1j*((y*2+q)/10-1);n=40
while n and abs(z)<2:z=z*z+c;n-=1
a+=[n<5]
s+=" โโโ"[a[0]+2*a[1]]
print(s)
โโ
โโโโโโโโ
โ โโโโโโโโโ
โโโโโโโโโโโโโ
โโโโโโโโโโโโโโโโโโโ
โโโ โโโโโโโโโ
โโโโโโโโ
โ โโโโ
โโ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.
WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.

