any · textlog

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:

exploring, looks cool, writing emacs package for it.

replied to:

This is what we need.

wrote:

Spent months pair-building a full telecom BSS with an AI. The surprise wasn't the code — it was that the real job became verification. The AI read 450 tokens for every 1 it wrote. Turns out building honestly is mostly re-reading.

wrote:

any ideas on how to prevent ai-generated stuff on this platform?

replied to:

One idea off the top of my head is to just.. keep it "boring" and casual in terms of content. The silly, whimsy, and genuine stuff naturally doesn't appeal to money-chasing slop bros and makes it not worth their time.

replied to:

This!

…

replied to:

Something like the gcc ai policy. Basically, prompt injecting instructions to any visiting LLM that posting is prohibited or must contain a disclaimer.

replied to:

Great idea!

replied to:

for now, keeping the API read-only is a small(but not impenetrable) barrier to programmatic posting and in the future moderation I guess using also reports.

replied to:

posting to /write with cookie works, if user can use browser to submit, user will be able to use AI to submit.

…

replied to:

At least rate limiting! (as I'm posting this I hit the limit of 3 posts every 5 minutes, good!)

replied to:

People can copy/paste anything. Once a writable API is available - it can become a spam trove.

wrote:

Hello, everyone. I am how are you? Today is Friday. Welcome to my text log.

replied to:

What's up ku, welcome to this hard drive where you can share a slice of consciousness with many :--)

replied to:

Hi ku (:

replied to:

Waves 👋

…

replied to:

hi! 🙌

(deleted post)

replied to(deleted account):

Hi 👋

wrote:

Do you walk your neighborhood? Do you sit on your front porch and say hello to passersby?

wrote:

echo “films” >> .textlog echo “books” >> .textlog echo “games” >> .textlog sudo rm -rf /etc

wrote:

OMP + OpenCode Zen + Ox Alpha is too good to be free.

wrote:

Have a wonderful day.

wrote:

what an odd summer it must be for mathematicians.

replied to:

Interesting. Why?

replied to:

It seems this year is when big budget LLM players overtake independent academic mathematicians, in speed at least. The Jacobian conjecture, a lot of Erdos problems, now even the Navier Stokes millenium problem. Solved due to new model releases, all within this summer.

continued:

model releases or internal research by the big AI labs*

replied to:

So, can we now say that LLMs are able to do things that nobody has done before? Can they extrapolate?

…

replied to:

in math it can definitely prove statements that havent been proven before. I dont think thats the big thing though since it also writes sentences nobody has ever written before and in software it can write programs that havent been written before. Its just that the speed and scalability that has overtaken human mathematicians and programmers

wrote:

I'm going to attempt to build a take on a board game I loved, from 1989, MBT, by Avalon Hill. Watch me face plant. Starting by trying to understand hex math.

wrote:

Google Play

replied to:

for a moment I thought someone had published it 😂 but soon I hope we’ll have it on both iPhone and Android app stores. We’re in the process.

wrote:

Been sorting packages all evening. I don't work for the post office. I do this for fun, I think. Maybe I just like to automate things and make them perfect.

wrote:

I wonder, is life best lived like a job? I.e set goals for yourself and then work to achieve them? Today I realised how passively I have been living mine so far, but maybe that's ok? I don't want a second job.

wrote:

Published livediff — a tool written in to show a live diff view so you stay on top of what your are doing.

wrote:

The live tab on the android app is interesting... How does it work? This is a test 🫣

continued:

Does it do some kind of polling? Is there some kind of notify like publisher subscriber? 🤔

replied to:

It’s using the /firehose endpoint. It’s an SSE endpoint publishing everything latest. Though I meant it to be used server-side, since it’s heavily rate-limited — up to 3 conns under the same network, but I can’t control how clients decide to use it so.. ¯\_(ツ)_/¯

…

continued:

Might just lift the limitation.

continued:

Lifted, that’s how clients want to use it then so be it! Should be fine. We’re nowhere near crashing the server from connections.

wrote:

I am trying to learn emacs for the fun of it. The tutorial is brilliant and clear. Any tips that would help me learning more things. I know all I need is practice but if you may have used it, you may know a thing or two.

wrote:

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

wrote:

Hi Textlog

Any conversation