Earlier quoted context omitted.
What makes you think so?
Probably the commit history.
Yayiee, the “cant prove it” Doakes Dexter meme, making it to HN
Show HN: I wrote a full text search engine in Go
21–30 of 56 posts
Re: Show HN: I wrote a full text search engine in Go
#22Did you vibe code this? A few things here and there are a bit of a giveaway imho.
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.
Re: Show HN: I wrote a full text search engine in Go
#23Re: Show HN: I wrote a full text search engine in Go
#24I really liked the README, that was a good use of AI.
If you're interested in the idea of writing a database, I recommend you checkout https://github.com/thomasjungblut/go-sstables which includes sstables, a skiplist, a recordio format and other database building blocks like a write-ahead log.
Also https://github.com/BurntSushi/fst which has a great Blog post explaining it's compression (and been ported to Go) which is really helpful for autocomplete/typeahead when recommending searches to users or doing spelling correction for search inputs.
Re: Show HN: I wrote a full text search engine in Go
#25Did you vibe code this? A few things here and there are a bit of a giveaway imho.
Another possible tell (not saying this is vibe coded) is when every function is documented, almost too much comments
Re: Show HN: I wrote a full text search engine in Go
#26Did you vibe code this? A few things here and there are a bit of a giveaway imho.
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.
> 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 :)
Re: Show HN: I wrote a full text search engine in Go
#27I really liked the README, that was a good use of AI. If you're interested in the idea of writing a database, I recommend you checkout https://github.com/thomasjungblut/go-sstables which includes sstables, a skiplist, a recordio format and other database building blocks like a write-ahead log. Also https://github.com/BurntSushi/fst which has a great Blog post explaining it's compression (and been ported to Go) which…
tysm, i love this, FST is vv cool
Re: Show HN: I wrote a full text search engine in Go
#28Did you vibe code this? A few things here and there are a bit of a giveaway imho.
Another possible tell (not saying this is vibe coded) is when every function is documented, almost too much comments
Ohh, I thought that inline comments would make it grokkable and be a low-friction way in. Seems this didn’t land the way I intended :'
Should a multi-part blog would've been better?
Re: Show HN: I wrote a full text search engine in Go
#29looks great! would love to see benchmark with bleve and a lightweight vector implementation.
tysm, would try pairing it with HNSW and IVF, halfway through :)
Re: Show HN: I wrote a full text search engine in Go
#30Shameless plug, you may wish to do Lucene-style tokenizing using the Unicode standard: https://github.com/clipperhouse/uax29/tree/master/words