Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
01/19/11 12:45
Read: times


 		 #180705 - and there's the rub
Responding to: ???'s previous message
Oliver Sedlacek said:
I would suggest that gold standard code needs to follow two rules.
Firstly, it needs to follow an agreed coding standard, by which I mean more than just MISRA. A style guide should be followed.

Secondly, every statement effectively needs a paragraph of comments to explain what it does and why the alternative 'bad' alternatives are 'bad'.


Clearly, that requires a very great deal of work!

And similar explanations are required of the overall aims, structure, objectives, etc, of the code as a whole.

This requires that you are not only able to write good code, but are also able to write good text to explain it well.

Clearly, there are very few people who have the skills and the time to do all this properly - and for free!

List of 37 messages in thread
TopicAuthorDate
Studying good code?            01/01/70 00:00      
   Apprenticeship            01/01/70 00:00      
      Always good to read code            01/01/70 00:00      
   I assume you write ...            01/01/70 00:00      
      Nice! :)            01/01/70 00:00      
   Becoming an "efficient firmware architect"            01/01/70 00:00      
      Professional training classes            01/01/70 00:00      
   A call to the 8052 community            01/01/70 00:00      
      Stumbling stone is commercialism            01/01/70 00:00      
      my initial offerings            01/01/70 00:00      
         Great!            01/01/70 00:00      
      A more fundamental problem            01/01/70 00:00      
         Hardware-specific vs. "good code".            01/01/70 00:00      
            source of inspiration            01/01/70 00:00      
               Intentionally bad vs. unintentionally bad?            01/01/70 00:00      
                  Hard to intentionally write really bad code            01/01/70 00:00      
                     why it's hard to write bad code...            01/01/70 00:00      
                        Standard mistakes.            01/01/70 00:00      
                           Brilliant link            01/01/70 00:00      
                     Bad code that actually works.            01/01/70 00:00      
                     it takes a genius            01/01/70 00:00      
         Good code for teaching            01/01/70 00:00      
            _More_ than just MISRA? *heartattack*            01/01/70 00:00      
            Pedagogical            01/01/70 00:00      
            and there's the rub            01/01/70 00:00      
               Problem with commenting too            01/01/70 00:00      
               Many hands make light work            01/01/70 00:00      
         Arduino            01/01/70 00:00      
            No need for reference hw            01/01/70 00:00      
               Beautiful Code            01/01/70 00:00      
                  There are lots of books on good coding practices ...            01/01/70 00:00      
                     And that was the OP's specific question!            01/01/70 00:00      
      Another Fundamental Tenet            01/01/70 00:00      
         Critisism            01/01/70 00:00      
   studying code ...            01/01/70 00:00      
      Even high-end embedded suffers            01/01/70 00:00      
         I agree, but            01/01/70 00:00      

Back to Subject List