we're taking over. :3 this site is for weird animal tgirls now
Any conversation
ai coding feels like it has reached diminishing returns for me. luna is my default orchestrator, routing work by complexity. in practice, usage lands around 16% luna, 48% sol, 30% astra, and 6% terra. at this point, i care less about each new frontier release. the system already finds a capable model for the job. the frontier is moving beyond my day-to-day work, so iโm happy to settle into predictable models for a while.
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.
my wife is concerned that my job search will not be fruitful due to my use of ai to build and orchestrate my json and latex resume and cover letter build pipeline. it has not changed much since I initially built it almost 20 years ago. there are only so many ways that the core metadata can be assembled for presentation, yes?
Just read a really interesting article on Japanese geography and history and it made me realise despite how great the Japanese are at adapting to a changing world they actually donโt have much of a history of being the centre of that innovation unchartedterritories.tomaspueyo.com/โฆ/how-japans-geography-determined-its
I remain ambiguous. This morning I used pi+gpt5.6 to create a color scheme based on evergarden.moe. It works, and I havenโt checked how well it stay true to the style used in vim-bundled schemas. Before I wouldnโt have done this, and now I can. But I donโt know if it is good. github.com/โฆ/evergarden.vim
Looks like you-know-who has finally come for nitter. :-(
nitter.net
