Still cheaper than giving up the monopoly position.

I put Overview section from the Readme into an AI content detector and it says 92% AI. Some comment blocks inside codebase are rated as 100% AI generated.

Claude: "You're absolutely right" :D

> comment blocks inside codebase

Is vibe-commented a thing yet? :D

Wanted to give fellow readers a good on-ramp for understanding the FTS internals. Figured leaning into readability wouldn’t hurt

For me this makes the structure super easy to grok at a glance

https://github.com/wizenheimer/blaze/blob/27d6f9b3cd228f5865...

That said, totally fair read on the comments. Curious if they helped/landed the way I intended. or if a multi-part blog series would’ve worked better :)

Thanks for the link, very interesting data structure.

I'm wondering is it really worth dumping a general knowledge articles into code comments? To me it feels like the wrong place. Would just the wikipedia link be enough here?

I also notice a lot of comments like this

  // IsEnd checks if this is the EOF sentinel
  //
  // Example usage:
  //
  // if pos.IsEnd() {
  //     // We've reached the end, stop searching
  // }
  func (p *Position) IsEnd() bool {
      return p.Offset == EOF
  }

Is it really necessary to have a text description for a code like "a == b"? It would be really annoying to update comment section on every code change.

This is one of the typical issues when AI creates "code comments", because it always describes "What" is happening. A good comment should answer the question "Why" instead.

For the linked skip list module, a good comment could say why skip list was chosen over b-tree or other data structure and which trade offs were made. AI will never know that.

The solution, for sure, is not asking how to do this online. What worked for me is resolution that cheap dopamine leads to degradation.

I have a brilliant phrase for you, it's called a baggage without a handle. It's hard to carry it with you and it's a shame to throw it away.

I was in very very similar situation and just put the lights off. You can't trick your brain to do hard work for free. Why spend your time working on something that unsuccessful when you can work on something that you actually like?

They don't seem to link any source code or demo. They could have run Claude for 10 hours to write thousands of the verge articles as well.

A brain recognises futile effort with minuscule success rate and hints with procrastination.

Interesting point

People invented unions to prevent things like this.

I can’t help in any way, but I’m just curious why you decided to transfer it as a luggage and not as a carry on? Why it didn’t have something like an apple tag inside it and why it wasn’t ensured and didn’t have a backup? Did you research Pegasus before the flight to see if it has a good service?

Can it be a chance that customs didn’t allow your luggage to be transferred?

Softbank or Microsoft can’t be happy or sad. CEOs only care about the share price going up while they’re holding the wheel. If Sam wants to start the idea incubator, why would they want to shut it down?

My thinking was that both of these large investors specifically want openAI to produce something like agi or failing that, something so popular and useful they make enough money not to care. And they want results this year/early next year. Softbank's latest investment round is partially tied up in openAI resolving their non-profit status by the end of this year. Training random founding engineers with no expectations of even using GPT-5 instead of traditional hiring feels either like a lack of focus or niave during this critical juncture.

But having said that, I do see the wisdom in the comments that the costs in running a 5 week course/workshop are low and the value in having a view into what people are making outside of the openAI bubble is a decent return all its own.