@eny
@wp
That's my intention because what seems obvious is not so obvious in the real world. I intentionally create "easy to spot" bugs that are often much harder to spot, but the same kind of bug.
Think 100.000 lines of code (I have done much more than that - within a team - in some jobs).
It must be manageable, repeatable and understandable.
Feel free to help me! It's a wiki! Only thing is: let me fill in the empty subjects first: I have code for that. And carefully weighted text.
Also note it is about defensive programming, not programming...(well, it is...
)
Note it is actually very hard to create common bugs.....for educational purposes.. And that what is needed to teac defensive programming: start with the error.
And... eny... did you know that? "use ranges instead of integers for your index and think about range when writing your code! It will prevent you from introducing range errors and you will catch them at compile time.".....