41–50 of 56 posts
Earlier quoted context omitted.
On my way to make a Dexter meme on this When you think OP vibe-coded the project but can’t prove it yet https://x.com/FG_Artist/status/1974267168855392371
OH YES! I Love it/this meme lol!! Dexter's memes have been popping up recently and I am loving them I don't know who bay harbor butcher is though :sob: but I don't want spoilers, I will watch it completely some day My friend says that he watched complete dexter just via clips lol.
You'll need to license it if you want others to consider using it.
Did you vibe code this? A few things here and there are a bit of a giveaway imho.
What makes you think so?
If someone has ever written any code is well aware of what can be done in a weekend and especially that no one doing something "in a weekend" will ever add all those useless comments everywhere, literally a few thousand lines of comments. That takes more time than writing code. Comments in Claude style. Other claude-isms all around.
It's ok to vibe things, but just say so, no shame.
And yes, after 5 minutes of looking around I had enough evidence to "prove it". Any moderately competent engineer could.
Earlier quoted context omitted.
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?
I mean, no biggie and I don't understand the reaction but hey, I'm old so...
Earlier quoted context omitted.
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?
Can't you just say that you used Claude and be done with it? I mean, I don't really care but in general I would refrain from posting "Show HN" with stuff that has been vibed, or state that you did since in that case it's even more interesting from my point of view, like you could describe how you kept everything under control during generation, etc... I mean, no biggie and I don't understand the reaction but hey, I'm…
We are soon entering into the territory of "no one cares if you did it, but can you say something interesting?". I created X software is soon leaving the ranks of cool stuff.
Earlier quoted context omitted.
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. o…
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
}
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.
Earlier quoted context omitted.
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?
I like it, I comment exactly like you do. Comments are free, storage is plentiful, why not add comments everywhere?!
I'm impartial in this discussion but that's usually how the counter argument goes.
Great work! Would be interesting to see how it compares to Lucene performance-wise, e.g. with a benchmark like https://github.com/quickwit-oss/search-benchmark-game
Thanks! Honestly, given it's hacked together in a weekend not sure it’d measure up to Lucene/Bleve in any serious way. I intended this to be an easy on-ramp for folks who want to get a feel for how FTS engines work under the hood :)