Show HN: The DNA of DOOM – How code structure survives across 44 ports

Interesting project. Out of curiosity, have you done more work studying the engine, eg, an architecture breakdown or programming pattern analysis?

... I think this is a fun experiment.

And, I like the article, once I got through the 'jolt'. (Not gonna call it slop, I can tell it a good amount of effort on your part to make it present the data well.)

I love Doom, and I love the genealogy of it; dealing with doom modding and dehacked was probably my first foray into any sort of concept of 'programming' (after all, you could do some curious things with dehacked, as far as 'next frame' and how that sometimes could change things in curious ways)

I think, to give some constructive feedback;

1. Consider taking a markdown/output from analysis and writing your own starting scaffold.

2. Make sure to review the output and tweak it.

3. Hand refine what the end result is.

I'm not saying you shouldn't use AI to help with some of this, I'm just saying, that will help so much more. Cause this is really cool, but yeah it would be nice to have more polish around it.

[flagged]

[flagged]