Author Topic: Omnimaga Rules Update  (Read 9097 times)

0 Members and 2 Guests are viewing this topic.

Offline calcdude84se

  • Needs Motivation
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2272
  • Rating: +78/-13
  • Wondering where their free time went...
    • View Profile
Re: Omnimaga Rules Update
« Reply #15 on: September 13, 2011, 09:12:20 pm »
Names help indeed. With modern languages comments are less necessary since it's often apparent what the code does. :) The extreme version of the maintainability problem is not knowing why some complex/heavily optimized assembly code that you wrote is buggy (which has happened to me, hence my caution <_<)
"People think computers will keep them from making mistakes. They're wrong. With computers you make mistakes faster."
-Adam Osborne
Spoiler For "PartesOS links":
I'll put it online when it does something.

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55943
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Omnimaga Rules Update
« Reply #16 on: September 13, 2011, 10:43:54 pm »
To be frank, this new rule was kinda existent since 2008, but I never really made it clear nor did not need to enforce it very much. People should code the way that suits them best. Some people learn better from modifying people code, like me. In fact this is how I learned how to make tunnel or snake clones. One snake clone used matrices and taught me how to use matrices.

Afterward I just wrote my own code. If I optimize a program to death then decide to have someone check if it's as perfectly optimized as I thought, then I want the person to tell me what I did wrong if he changes stuff, so I know the next time.

Just make sure that if you voice your views on a coding method that you do it with respect, without imposing your view on others.
« Last Edit: September 13, 2011, 10:44:26 pm by DJ_O »