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
A couple of afternoons of the
jinn coding harness and glm-5.3 and my taxus static site generator is properly whipped into shape.
get-taxus.org
It now has a frickin' data model, that's documented, as well as installers for your platform of choice.
Try it, break it, I'll be doing the same. Let me know where it broke for you.I still don't get how now after AI coding there's people saying that contrary to common belief code wasn't a bottleneck and I realized that when I was starting to code at 10yrs ago when I was 15 and read it in a stackoverflow comment. I thought that was the common belief and still can't believe a lot of supposed senior programmers apparently believed so.
Morning everyone, I've started a project to bring back "classic" era Instagram, from say the 2012 - 2013 time frame, long before it was ensh**ified.
It's nowhere near ready for public consumption, so I've closed off registrations. Right now it's mainly for me to show my photography.
halation.photos



