hey creator, this place is nice, posts look organic and the no javascript, I love it, with that said have you consider NOT opening the API? and have a 1 way to come here and enjoy it? the rationale being that API also opens the door to the slopai?
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.
One idea that I've been thinking about is an or where it is a app so you get a new file everyday right except the app keeps track of all the files for you. the idea is that anytime you type anything it it basically makes a commit and use so anytime you type something it commits automatically after a quick pause after you stop typing.
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.
Today I wanted to share some Music from my youth :)
www.youtube.com/watch?v=8Hn-pNxtByM

