| Making Good Software | |
| " /> | |
| Keywords : good software, good code, Alberto G, Alberto Gutierrez, Best Practices, making good software, agile | |
| H1 tags : Making Good Software | |
| H2 tags : 1.- Transactions.; 2.- Database access.; 3.- Multithreading.; 4.- Logging and auditing.; 5.- Exception management.; 6.- Invariants.; 7.- Disabling/Enabling/Swapping services or modules.; 8.- Ubiquity and low coupling.; 9.- Self diagnosis.; 10.- Documentation.; What is important in an application?; The mission; Update; Dynamic tree building to find a solution; 1.- An exception should only be handled once.; 2.- Create your own type and tree of exceptions.; 3.- Who should catch the exception?; 4.- Understand the purpose and nature of the exceptions.; 1.- Always assume that your integration point may fail.; 2.- Cover your back.; 3.- Isolate the interactions with the integration point.; 4.- Do “what if..” integration testing before going to production.; 1.- Stories are better if you follow such and such conventions to create them.; 2.- Planning, with agile is fun and accurate.; 3.- Daily stand-up, the communication panacea.; 4.- Agile the process that fits everything.; 5.- Retrospectives, they fix everything.; 6- Unit tests is all you need.; 7.- Agile is a process fitted for junior programmers.; Customer, customer, customer.; Usability and simplicity; Content; Reporting and management; Don’t reinvent the wheel |
| Last Update : | 28/October/2011 |
| Google PR : | 3 |
| Indexed pages : | 101 |
| Internal links : | 90 |
| External links : | 3 |
| Archive : | Check how did the site look in the past? |