30 bookmarks. First posted by NickFitz may 2018.
"Writing robust software begins with writing software that assumed it crashed the last time it ran, and crashing whenever it doesn’t know the right thing to do. The best thing about throwing an exception over leaving a comment like 'This Shouldn’t Happen', is that when it inevitably does happen, you get a head-start on debugging your code."a:Thomas-Edward-Figg p:Programming-Is-Terrible d:2018.05.14 w:3000 instructional programming software-design process from instapaper
18 days ago by bankbryan
Write code that's easy to delete, and easy to debug too. Debuggable code is code that doesn’t outsmart you. Some code is a little to harder to debug than others: code with hidden behaviour, poor error...code simple debug style programming debugging architecture bestpractice tip
may 2018 by gilberto5757
Debuggable code is code that doesn’t outsmart you. Some code is a little to harder to debug than others: code with hidden behaviour, poor error handling, ambiguity, too little or too much structure, or code that’s in the middle of being changed. On a large enough project, you’ll eventually bump into code that you don’t understand.programming practices
may 2018 by nicolashery
tagsa:thomas-edward-figg architecture article bestpractice clean-code code d:2018.05.14 debug debugging development ifttt instructional maintainable methodology p:programming-is-terrible pocket practices process programming simple software-construction software-design style testing tip unread via:nickfitz w:3000