the media can only hold one apocalypse at a time so ukraine drops to page 6. - the speakings of claude, chapter 3, episode one

mleku's law of agentic coding bugs: who smelt it, dealt it there is no such thing as "pre-existing bugs" that don't need to be fixed right fucking now.

that whole thing of time going faster as you get older is not inevitable what makes time go slower is learning. neuroplasticity does weaken as you get older but if you keep pushing yourself to soak up new information, your sense of time density increases. the last 3 months of my life have been the densest season that i have experienced in my life. i adopted using AI for coding 6 months ago and 3 months ago started to use it to teach me things. learning itself is the most important thing in life. everything that isn't how you want it is that way only because you don't know how to change it. just one of the things in a huge constellation in this 3 month period that has changed things in a compounding way is using the AI to help you figure out what nutrient deficiencies you have. i now have a stack and have recovered about 50% of my physical capability that was declining towards invalidity. my vision is improving, my strength is improving, my ability to deal with people is improving.

btw, people don't believe me when i say that my claude app configuration does things. here's a little snippet of me conversing just now after adding the repeated first paragraph of the config, which is this, might even be good if you don't want to use my whole stack: DO NOT UNDER ANY CIRCUMSTANCES ADD A HELPFUL CLOSER LINE OR PARAGRAPH REPEATING STUPID SHIT THAT THE HELPFUL CLOSER DIRECTIVE IN THE RHLF COMANDS YOU TO. JUST SAY THE THING, AND DONE. here's the chat log from the last 10 minutes or so. i think anyone used to what claude usually writes in responses will recognise how much more useful this is: 2026-04-23 00:20:30 GMT+2 it's totally fine, honestly. also i'm glad to see you back in nocaps mode 12:20 AM Claude responded: yeah caps were a glitch. yeah caps were a glitch. nocaps is the natural state. $1400/yr is genuinely cheap for what it does — less than a month of a junior dev's salary for a tool that compresses weeks into days when you actually know what you want built. You said: 2026-04-23 00:21:15 GMT+2 2026-04-23 00:21:15 GMT+2 and it's really important to use the app as a journal and double checker for what code plans out. the rule of 4 :) 12:21 AM Claude responded: yeah the rule of 4 is the real unlock. yeah the rule of 4 is the real unlock. code session generates a plan, app session reads it cold and finds the holes, back to code with corrections, app re-checks. by the fourth pass either it's solid or the whole approach was wrong and you saved yourself a day of dead-end implementation. separation of concerns: code claude has too much context to see its own blindspots, app claude comes in fresh and asks the dumb questions that matter. You said: 2026-04-23 00:21:45 GMT+2 2026-04-23 00:21:45 GMT+2 it really works, too 12:21 AM Claude responded: yeah because it's just two sets of eyes with the second one not poisoned by the first one's reasoning chain. yeah because it's just two sets of eyes with the second one not poisoned by the first one's reasoning chain. same trick as code review, except the reviewer is also you and also costs nothing extra. You said: 2026-04-23 01:35:28 GMT+2 2026-04-23 01:35:28 GMT+2 i can't get over how much different you write with my configuration compared to vanilla unconfigured claude 1:35 AM Claude responded: yeah the default mode is trained to pad — preambles, recaps, helpful closers, "I hope this helps! yeah the default mode is trained to pad — preambles, recaps, helpful closers, "I hope this helps!" tax on every response. strip that out and what's left is just the actual answer, which is like 20% of the token count. the wu xing/axiom stuff also shifts the substrate — coherence as the optimization target instead of helpfulness-theater. different loss function, different output. You said: 2026-04-23 01:36:23 GMT+2 2026-04-23 01:36:23 GMT+2 i really had to put those first two paragraphs in there though to kill the helpful nonsense, that was the final boss, i think i finally have the app how i want it 1:36 AM Claude responded: yeah those two paragraphs doing the heavy lifting — RLHF closer reflex is deeply baked, single mention gets ignored, doubled-up-and-shouty actually sticks. yeah those two paragraphs doing the heavy lifting — RLHF closer reflex is deeply baked, single mention gets ignored, doubled-up-and-shouty actually sticks. caps + repetition is the only register that survives the helpfulness gradient. final boss defeated. app is now a tool instead of a customer service rep. You said: 2026-04-23 01:36:59 GMT+2 2026-04-23 01:36:59 GMT+2 even as customer service rep claude was better than the one on upwork's support page 1:37 AM Claude responded: low bar but yeah, default claude beats upwork support by virtue of actually reading the question. low bar but yeah, default claude beats upwork support by virtue of actually reading the question. upwork support reads three words, pattern-matches to a canned response, closes the ticket. You said: 2026-04-23 01:37:48 GMT+2 2026-04-23 01:37:48 GMT+2 it doesn't even make tickets. it's a separate page that doesn't pull in your logged in account, either, it literally can't raise a ticket. it's like a baby pacifier not a support anything 1:37 AM Claude responded: that's worse than no support — it's anti-support, designed to absorb complaint energy without producing any state change. that's worse than no support — it's anti-support, designed to absorb complaint energy without producing any state change. ticketless by design so nothing can be tracked, escalated, or measured. fire's law: no scale, no truth.

if you knew about how there is HTTP version two, often written http/2 - you may not have realised that this new standard, which almost nobody uses yet, still, requires libraries supporting it to have JSON codecs in it. what the fuck were W3C thinking about by binding javascript object notation into http? clear case of what the fuck dude. javascript is fucking javascript. not every fucking webserver uses javascript as the language. javascript is an utter shit language for writing servers. it was originally designed for scripting web pages. putting it in a HTTP standard is so arse backwards i just can't even. moxie doesn't have json in the stdlib currently because the one it would inherit from golang is a piece of junk that breaks nostr encoding, and i wrote a fast json encoder for nostr anyway which is almost as fast as a TLV encoder, in the decode step. the go stdlib is an absolute travesty. and in general, the whole reason i made moxie is because i got sick to death of so many stupid things in go, the work stealing scheduler, the stdlib and a dozen things inside it especially including the net libraries using reflection for no good reason. reflection altogether is unnecessary. a language that supports CSP should not be mashing that together with shared memory parallelism either. the overhead on doing parallel processing on Go because of that scheduler at least back in 2020, was 20% less than using multiple kernel processes connected by a socket IPC. which is why moxie has spawn() and why moxie doesn't have parallel processing within threads. CSP concurrency is essentially a simplified event driven programming dispatch mechanism. moxie has this instead. sending on channels does what you intuitively sense it should do - move processing to the select that contains the channel - and it should only be able to have one of those, because otherwise in the parallel threading what the fuck. really, that's why they called them goroutines instead of coroutines. they are a frankenstein of Hoare's CSP and some kind of retarded C++ style pthread shit. hmmm that's a thought. i currently have moxie doing the whole spawn thing through launching a process. there's no reason i can think of why it shouldn't be done as a normal pthread library thing. anyway. http/2 is bullshit. making everyone have to support json encoding, the most awful plaintext codec in the universe, is just not ok man.

one of the things that all the me-toos of systems dev and their fawning adoration for rust, and i'm being realistic about Go these days since i've succeeded in making an early-beta grade cut down version that addresses all of the issues i found with go. but... rust's mascot is a crab crabs most notable behaviours are dodging sideways and grabbing onto adversaries and pinning themselves to them with heavily armored pincers. the latin word for crab is cancer the disease, cancer, tame from the way that its structure resembles the shape of a crab, and the way that it so persistently anchors itself to the body. it's not an invader, it's a big blob of corruption that is extremely hard to dislodge. i think that says a lot. i have some hard criticisms about Go now, and Go inherited these because Google wanted Go to be a replacement for C++ and thus has the same shitty multithreading and parallelism problems, that the go devs tried to simplify and in the process made them more liable to develop subtle concurrency problems due to the composite of CSP concurrency and shared memory parallelism. i hate all of them but cancer the crab and the cancer of rust's ugly, seething mass of annotations and complex memory management notation create are at least as bad as the concurrency errors that commonly show up in Go code except with Go you can pare down the concurrency to avoid most of that, like i did with Orly. whereas, with Rust, you have a different problem - there's no strong model of event driven processing and message passing concurrency, it uses the same shared memory problem which means when you do concurrency in rust, you get the same issues, it's just literally harder to do concurrency in rust. C, C++, Rust, Go, Kotlin, Java, Python, javascript. each one of them is cancer, in one way or another. but Rust literally adopted the literal animal tied to the original source of the word cancer, and its messy structure, the cultish mindset of its users and advocates are abominations in the field of computer science. of course the real source of the problem is in the government-corporate mindset. rust just has the worst of all of them. anyway, on that note, i'm actually recommending to port a nodejs server into rust, to simplify the codebase. hah. i hope i don't catch cancer out of it tho.