Changes between Version 17 and Version 18 of HowtoGoodProgrammingTechniques


Ignore:
Timestamp:
Feb 25, 2013, 4:17:31 PM (12 years ago)
Author:
Deon Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowtoGoodProgrammingTechniques

    v17 v18  
    8989* Always use local variables, don't share them externally or you can have catastrophic results
    9090
    91 * Use vim with a good set of plugins, no way to use a less powerful one
     91* Use a good powerful editor with good plugins, like vim with a good setup
    9292
    9393* trap signals, like exit errors etc
     
    9595* the simplest procedure/option is the best, do not think in complex ways to do supa-dupa-intelligent-features if they are not needed
    9696
    97 * Think on multi-work, if you use a temporal directory called /tmp/myapp, you could have conflict when another user try to use the same application which will point to the same location (so /tmp/user-myapp is a good option). Or also including the ID of the process is also a good method for avoid re-using the same directory if the application can be launched multiple times
     97* Think on multi-work, if you use a temporary directory called /tmp/myapp, you could have conflict when another user try to use the same application which will point to the same location (so /tmp/user-myapp is a good option). Or also including the ID of the process is also a good method for avoid re-using the same directory if the application can be launched multiple times
    9898
    9999* [http://www.makinggoodsoftware.com/2009/06/04/10-commandments-for-creating-good-code/ 10 rules for creating good code] that must be read until becomes subconscious