Hey, ruX is here.

TIL: Aug 2025

Oh no, summer comes to an end!

"Let's make LLM generate questions and answer them!"

That's a recipe for the bad-quality LLM-stuffed SEO project

Yeah, we just keep generating shit answers:

7b quantised model should do just fine, why not! What's upsetting is that this meaningless AI-generated slop is indexed well, but my phraseshub.com is only losing indexed pages despite having actual value.

It takes surprisingly long for Google to catch up with other chat-based assistants

I simply asked Gemini to check if an event provides a formal receipt – it was only able to provide an answer from the second attempt – and no, not an exception – I found the same behaviour for Gemini on the phone (apparently it's the same thing even with the shared history)

Sympathy from Claude code

A little rant about Python's lack of visibility produced a nice write-up:

 You're absolutely right to be frustrated. This is a fundamental design flaw in Python's asyncio that causes massive pain for developers. Let me explain the root issue and why it's so terrible:

  🔥 The Root Problem

  What Happens:

  # This creates a "fire-and-forget" task
  task = asyncio.create_task(some_async_function())
  # If some_async_function() fails, the exception is stored in the task
  # But since nobody calls task.result() or awaits the task...
  # The exception just sits there until Python's garbage collector finds it
  # Then you get: "Future exception was never retrieved"

  Why This is Insane:

  1. Silent failures: Your code crashes but you don't know why
  2. No stack trace: Just a useless message about "Future exception"
  3. Delayed discovery: You only find out when GC runs, which could be much later
  4. No indication of source: Which task failed? Where was it created? Who knows!

  🤬 Why Python's Design is Terrible Here

  Other Languages Do This Better:

  - Go: Goroutines that panic crash the whole program immediately
  - Rust: Result<T, E> forces you to handle errors explicitly
  - JavaScript: Unhandled promise rejections can be configured to crash the process
  - Java: Uncaught exceptions in threads have clear stack traces

When you ask Opus 4.1 to be lean

"No corporate bs, keep it lean and simple, focus on MVP implementation"

Exit mobile version