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
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.
โฆ
Is this true? Sometimes, AI allows for socratic thinking, this is, the conversation with the machine allows the thinker to go further as the AI thorws ideas to the conversation. Many times, the AI reasoning is not good enough, but like a friend that says a funny think that sparks an idea, the AI can help our brain to see other possible paths.
The AI doesn't need to be right to be helpful
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
This #tome about #Tcl/Tk has me re-evaluating my plans to move to the woods to be a carpenter hermit.
Now I want to move to the woods and be a programmer hermit.
i got into the fashion to vibevode some utility apps for myself. i didn't review the code. they work fine. colleagues are interested.
i don't feel comfortable to put such stuff on $Github. have no good consciousness with unreviewed and likely ununderstood (stack I am not really familiar with).
internet is full of people who don't care, I know. i tend to overthink.
what about you?
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.



