I disagree. Too simplistic. It's my job as a developer to try and think of all the ways my project can fail and bog down before hand (within reason on the perfo

I disagree. Too simplistic. It's my job as a developer to try and think of all the ways my project can fail and bog down before hand (within reason on the performance). I've got a list of items I am actually working on and will post it above my desk when done: 1. Let me think about this some more before giving you an answer. 2. I will use my debugger. 3. I will create a new branch for this task. 4. I have commented my code and commented it well. 5. I have accounted for fail scenarios. 6. I have considered multiple solutions to this task. 7. I have not begun hacking away immediately at a task. 8. I have attempted exploiting my code.