Show HN: The DNA of DOOM – How code structure survives across 44 ports (squid-protocol.github.io)
blinkbat 2 days ago
joe-esquibel 2 days ago
joe-esquibel 2 days ago
mcculley an hour ago
happytoexplain an hour ago
Edit: And if so, was it for help with English? Or another reason?
mjdiloreto an hour ago
One constructive point for you: don't even write the first draft of a document you want humans to read with AI. It's much harder to get the AI voice out than it seems. Stuart Halloway talked about this at the last Clojure Conj, and I couldn't agree more. It also makes it harder to follow the sage writing advice to minimize what you write.
"How code keeps its family resemblance" - AI would say this, a person would not. It's just noise on the page.
"Measure only their shape and you can still tell who copied whom" - this is a sentence structure Claude loves, but no human would talk about "measuring" shapes. The verbs and the nouns don't feel right.
Then you start a paragraph: "DOOM is the perfect place to test it." But you don't actually say what "it" is specifically. It doesn't seem like AI would write that though... Maybe you did in a later draft? It's hard to switch voices, like switching authors.
If you want people to read something, write it yourself.
anonymous908213 an hour ago
KeplerBoy an hour ago
At this point I am not sure I wouldn't get a very similar output if I just prompt Claude for the genealogy of Doom ports as an interactive dashboard. Maybe try to deviate from that, even if that would rank lower on a model benchmark: you don't have to provide an interactive data visualization for everything. You can narrate a story from your own opinionated pov.
nater5000 an hour ago
I concur with the other comment that it's an interesting idea, but you should just write the article yourself. You can even link to the technical details so that those who are interested in exploring that data can do so. But as-is it's really a good example of AI slop.
philxor 39 minutes ago