About coding well - DukeNukem3D code




I recently discovered the site of a french developper who travelled many times across oceans and between companies.

Fabien really loves coding, like me; and even more, he likes analysing existing code to learn by itself from masters, or from others.

I was happy to see someone (apart from John CARMACK) giving such importance to well coding : architecture, design, coding rules (names, metrics, etc) and so on.

And it reassures me in how I manage to develop my Procedural Music Generator project : I want to make something that I could go back and forth with the minimum sordid details in mind (like using a generic name variable and asking myself what it is used for); and also a project that anyone could re-use, modify, and enhance.

It is interesting to compare Doom code with DukeNukem3D one. Duke was amazing and in many ways better than Doom (faster, using less CPU, more features, slopped walls, etc) but in the end, its code is unmaintainable !

Doom Engine source code review (fabiensanglard.net)

https://fabiensanglard.net/duke3d/notes.txt


Comments