1. 01 Aug, 2017 1 commit
  2. 17 Jan, 2017 2 commits
  3. 23 Nov, 2016 1 commit
  4. 01 Aug, 2016 1 commit
  5. 15 Jan, 2016 1 commit
  6. 13 Nov, 2015 4 commits
  7. 07 Nov, 2015 5 commits
  8. 06 Nov, 2015 1 commit
  9. 30 Sep, 2015 1 commit
  10. 19 Sep, 2015 1 commit
  11. 10 Jun, 2015 1 commit
  12. 20 Apr, 2015 1 commit
  13. 18 Apr, 2015 1 commit
    • Sébastien Wilmet's avatar
      programming-guidelines: add book references for writing good code · 4e0347f5
      Sébastien Wilmet authored
      When possible, the link is the official web page for the book. As a
      fallback, a link to wikipedia (if a page exists) or Amazon.
      
      If only one book should be chosen for "writing good code" (the subject
      of the page), it should be Code Complete IMHO. It covers a wide range of
      subjects, from single lines of code to the general architecture of big
      programs, with introductory chapters on other topics like refactoring,
      debugging, performances, etc.
      
      The Refactoring and Design Patterns books are also the references for
      those subjects, which are important for code quality and
      maintainability.
      
      Finally, Object-Oriented Design Heuristics is also a really good book,
      that contains many guidelines for writing OO code. It's IMHO a more
      important book than Design Patterns, although the latter is more
      well-known. The guidelines explained in the book apply to every OO code,
      even for a small codebase. On the other hand some design patterns are
      useful only for big codebases. Since every software must begin by a
      small codebase, it's better to apply OO best-practices from the
      start.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=747997
      4e0347f5
  14. 16 Apr, 2015 3 commits
  15. 18 Mar, 2015 1 commit
  16. 19 Feb, 2015 1 commit
  17. 18 Feb, 2015 1 commit
  18. 14 Feb, 2015 6 commits
  19. 12 Feb, 2015 2 commits
  20. 11 Feb, 2015 5 commits