By piccoloprincipe
via css.dzone.com
Published: Nov 12 2012 / 09:26
Bad stuff happens: database records go missing, remote services are inaccessible from time to time, and disks get full. But many language-level errors are caused by programming faults, not by external conditions: an important practice is managing errors to make sure they are detected, stored and resolved with minimal overhead.
-
Building a Notes App with IndexedDB, Redis and Node.js
-
How a Scrum Master Can Handle Impediments with a Team
-
Part II: How many IOPS can a HDD, HHDD or SSD do with VMware?
-
Calling Non Public Setters
-
Sauce Labs Appium Now Can Test Android and Firefox OS Apps
-
Stupid Java Tricks » Changing Play 2 DB Configuration At Runtime: Beware of Dragons
Add your comment
