any · textlog

故事的开头总是这样，适逢其会，猝不及防。故事的结局总是这样，花开两朵，天各一方。（by 张嘉佳《从你的全世界路过》）

Stories always begin this way: a chance encounter, completely unexpected. Stories always end this way: two flowers bloom, then drift apart. (by Zhang Jiajia, I Belonged to You)

wrote:

Love the flat option for threads Edit: didn’t realise that was the old style. Hahaha

created a poll:

Best OS?

Windows0%

MacOS38%

Linux63%

16 voted

…

continued:

Results are back! 16 voted, Linux won! 🥳

wrote:

Spending mornings scouring job boards and listings and applying. Afternoons working on Cheltenham Open Data and iOS app development. What about you?

replied to:

waiting for my friend so she can put my hair into a bun

wrote:

shower thought: swap 'is a model' for 'is constructed' and postmodernism suddenly becomes a lot more palatable without losing much of its core message.

wrote:

and it's all

wrote:

, is this a bug?

replied to:

No just limitation currently tags are alphanumeric (latin) so it stopped at ñ. I'll see what I can do.

replied to:

Ahh, I see.

replied to:

Fixed :)

…

replied to:

Woot, woot! Hopefully the OP comes back. :-)

wrote:

I'm working on this command-center project. Human describes the mission. Agents define the mission, breakdown and come up with a plan, and drive it.

wrote:

Microsoft Word Online (web version) is horrible.

replied to:

It was the only way to reproduce the authentic horrible experience of the offline version.

replied to:

🤣 Did not remember the offline version being this bad, but maybe it went downhill in the past 5 years I have not used it.

…

replied to:

I never used the online version, but the last time I used the offline version it already was a horrible experience. This was about 5 years ago, before I had moved entirely to Linux. It was so bad I downloaded a pirated version of some old MS Office 2007 Blue Edition to have something acceptable. I unironically prefer Libre Office.

wrote:

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.

replied to:

I think you're right but executing on that idea requires a lot of care. It's similar to how functional programmers pathologically fear state; sometimes coupling/state are a necessary evil in order to keep the theory simple.

replied to:

true! i might have been wiser to say: code quality is about managing coupling across the whole system. extracting a coupling sometimes requires you to introduce complexity beyond that which the extraction reduces.

wrote:

Have a wonderful day.

created a poll:

, do you have warnings as enabled at ? How is your so far?

yes0%

no0%

0 voted

wrote:

the day is done! time to stop looking at the bad screen they pay me for to go home and watch the good screen I pay them for

replied to:

So true... I type in a screen I paid for 🤣

wrote:

is where all the linux fortunes get injected with new electrons, new spins, new universe fairy dust to have a second eternal life?

wrote:

been building a voice first os using jev and some small voice models. I'm surprised how well it's working and I'm very close to the point where I can go into a feedback mode and tell it what behavior I want changed, it will spin up Claude or codex inside itself and setup the build to restart itself and continue with new code. tempted to let it build itself completely

replied to:

It sounds amazing! A voice first OS was also in my mind. Curious to hear more!

wrote:

What did I build with claude yesterday - kanban board for my agents, Hamster Jerob game, imgproxy for thumbs in my photo sharing app, and ghostel-shell-command helper. Today - digital detox day.

wrote:

Anyone like James Michener?

wrote:

!

wrote:

apparently there is some filtering. can't say "hit*s with hand".

wrote:

So much present tense in generated prose. Terse, authoritative sentences, without breathing room, without hesitation or qualification. It jumps off the page, and not in a good way.

replied to:

What about the lack of density to paragraphs, the length of the sentences, or the confidence and determinism of their direction? Conviction with no limits. So reliably repetitive that you start seeing patterns as if you are looking and reading a record player with some scratches on it. Skips. Squeaks. Repeats. Yet. It gets the job done.

replied to:

Yet. It gets the job done. Here's where we disagree. Using these tools as part of the job, certainly. But if I am to read, discern meaning, analyze choices of diction and structure, consider the context both of the author and the audience, and finally derive value from the written word, then generative falls short on many levels. If the "job" is to produce something no one was ever intending to engage with, then we have a more fundamental question about the value of the job.

…

replied to:

Maybe what I messaged read as a disagreement and mentioning that they get the job done was actually not about producing prose (of any quality). I wholeheartedly agreed and still agree with you. Getting the job done was more about producing output - be it some prose, images, videos, software, whatever. They do generate output. It is not to say that the output is meaningful or meaningless. Some souls do enjoy it. Some others - don’t. I did start with a question though.

Any conversation