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

Back to Subject List

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


 
Msg Score: +1
 +1 Good Answer/Helpful		 #180656 - studying code ...
Responding to: ???'s previous message
... can be god and bad.
If, for example you end up studying code from "the best programmer in the world of those that do not understand embedded" you will pick up some bad habits.

likewise you end up studying code from "the best embedded engineer in the world of those that do not understand programming" you will pick up some bad habits.

The examples above are extreme, but all code I have seen (I guess including mine) will have elements of the above.

What would, in my opinion, tbe the best approach? go ahead and look at some code, not to "study code" but to see if you can pick up a 'trick' or two. then, carefully evaluate if those 'tricks' are they good or bad?

Anyhow my $0.02 re embedded programming: if you are not fluent in assembler and hardware, you will never be 100% in embedded C

Erik

PS the above refer to "small to medium embeddeded" in "large embedded" there are places for "non-embedded programming" that just happen to be in an embedded device.

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