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 04:53
Read: times


 
#180638 - Studying good code?
Jack Ganssle once observed that while students in most professions spend an appreciable amount of time studying quality examples of their craft, firmware engineers rarely get that opportunity due to the proprietary nature of the work. We all know that there is plenty of code snippets available online, and even quite a bit of complete programs available to study, but we also know that much of that code is not worthy to be studied, or at least not in a positive sense.

So, are there any good projects which are open to study for the 8052 or another small MCU. Again, I'm not talking about one driver or one routine, but a complete project which could model good structure, with simple and elegant code design.

Also, is this generally a good way to transition from someone who just knows C to a efficient firmware architect?

Thanks,

--David

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