John Romero's id Software Programming Principles Do They Still Apply?

[@SteveMaves]

Thanks for sharing this, I had not heard of these before, great stuff!

[@computerhobbyists3070]

You're welcome!

[@bronsonschnitzel7493]

Definitely agree with you that a consistent code base and architecture is important as well as the output. Nothing worse than jumping into a codebase and there's no consistency across features or implementations.

[@scottchelmford7136]

how do you not prototype in any software development?

[@Architect54]

I have mp3 format s and i want to make it puncNice tutorialer plzz help buddy

[@alexandreferraz4194]

Great input.

[@computerhobbyists3070]

Thanks!

[@BonMoogly]

cool video cool insight thanks

[@computerhobbyists3070]

No problem!

[@jynx0riZ0r]

Programming is a creative art form based in logic. That does not mean that people can not agree on coding standards in a team project.

[@teckyify]

Often there isn't even agreement necessary, because you use static analysis with predefined profiles. I know this is often uncommon in C++ though because the tools there are expensive, because of the language's complexity.

[@bitwize]

"Polish as you go" and "always have shippable code" sound like standard enterprise-dev orthodoxy w.r.t. CI/CD and refactoring. But enterprises don't always practice what they preach...

[@pieteb_nl]

Point 10 seems to be completely be in conflict with point 9. Agrree it doesn't make much sense.

[@CallousCoder]

And yet SOAP is far superior to Rest! If I see important information being send by rest I shiver! Soap has WS-Security and signing of the actually message build in and hence if security is important than soap is still the better choice. And unlike Rest the wsdl and xml schema force a hard type. Use the best solution for the job. But he me at coding style as in dialect. For example I don’t use else’s. I avoid using try catch in user applications they are just apart of libraries where I truly don’t know what to do and need to throw it up to the caller. I’d you demand a coding standard in your company you’ll conform to the lowest (dumbest) common denominator. And you kill innovation and insight. My code as someone who learned assembler and C and had done systems development will look different (and be more robust and faster). Like in games, I will always have an old and current variable so I can compare and only send something to be drawn when it actually has changed. And I write that out in unrolled code (sure I would use a macro) because I know that eventually cycles do add up. I don’t see any developer now use that (weirdly enough). I guess they never actually programmed a game from scratch in assembler on a small system like a C64 or Atari 😁 And I refuse to change a coding style, it’s like changing your accent or dialect. You just have it, and you still speak the same language so you can understand it.

[@rhettbaldwin8320]

Lazy coders don't send their code to be tested by the in house testing department, that's too much work, they just check it in and claim it worked fine on their system.

[@teckyify]

I also saw his presentation and I wonder how much he actually follows his own advice today. Back then, when they wrote those relative simplistic games from scratch, it was rather simple to focus on correctness. Today's games would never be released when correctness would be taken seriously. The size of the systems is insane and most often we don't even close understand or control the system we use. His advices are almost naïve from today's software developer perspective. Some things are obvious, others strange, like the coding style, as you also mentioned.

[@puzzud]

The fix bugs when you see them is dangerous as that can cause more bugs. This principle probably is the most outdated and is likely tied to the lack of a version control system. If the bug was introduced by the work of the immediate task at hand, then yea, that bug should not be forgotten. In my practice, the rule is to always document a bug you find and address it when it is relevant or appropriate.