Wednesday, April 29, 2009

Treat Warnings as Errors

Tip: Treat Warnings as Errors

Another neat day-one rule, along with DB sessions and ZERO error handling to ensure that your .Net code is as bug free as possible.

The mantra during development has to be to break the app as much as possible, not supress errrors.

Ban try-catch blocks! :)

[update]

The sooner you fall behind, the more time you will have to catch up
"an informal slogan of the on-board shuttle group [that] captures the essence of keeping focused on the process"
(Focus on breaking)

"Gen-Xers sporting T-shirts and distracted looks, squeezing too much heroic code writing into too little time; rollerblades and mountain bikes tucked in corners; pizza boxes and Starbucks cups discarded in conference rooms... It's not the story of the on-board shuttle group"

"How do they write the right stuff? The answer is, it's the process"

"Software for Grown-Ups"

No comments:

Post a Comment