It's Monday. Coffee is barely working and so am I.
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.
hello world ~ i'm a web developer from midwest, usa. it's been awhile since i worked on anything. since the i've been working my way up the ladder at a blue-collar job; i was promoted to team lead last week. but as i browse hacker news everyday, my cravings for web development increases.
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.
Sunk cost fallacy is no longer applicable in the age of . Now you can do broad changes without second thought, u can always revert back, without incurring the cost of doing so, since itโs all done so quickly and effortlessly.
Having spent the last 12 months using HTMX in $day_job, after 5 years with react, I have come to the opinion that whilst large amounts of JS and CSS are not necessarily wrong, they should be reserved for progressively extending the platform with a composable set of generic UI primitives that build out a cohesive design language โ encoding business logic (including routing) there is generally a mistake


