Timeline for What should every programmer know about programming?
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 27, 2010 at 19:04 | comment | added | gawi | I think the point of debugging to validate your assumptions across your program. Sometimes, you need to go fishing for some clues. This has to be done systematically. It it perfectly valid to try something that might tell you something new. I do it often. | |
| Sep 27, 2010 at 18:59 | comment | added | gawi | Another weird behaviour is the programmer insisting that every part of his program is correct while the result if faulty. "-You don't need to print the array on the console to check if it's sorted because the line above is array.sort()." "-Well... you know, it's not working. There must be something wrong somewhere. You can't just defend your code at this point!" | |
| Sep 27, 2010 at 7:13 | history | edited | Igor Popov | CC BY-SA 2.5 |
Corrected spelling ("int he" -> "in the")
|
| Sep 15, 2010 at 18:31 | history | made wiki | Post Made Community Wiki | ||
| Sep 15, 2010 at 11:54 | comment | added | Evan Plaice | +1 I went from javascript/php to C# and fell in love with stepping through code. I wish that dynamically typed languages could do a much better job of this. | |
| Sep 9, 2010 at 18:30 | comment | added | Dov | I was about to post this. So much of a programmer's job is fixing bugs, and a lot of people tend to be incapable of doing so (especially in others' code). | |
| Sep 9, 2010 at 16:24 | history | answered | JohnFx | CC BY-SA 2.5 |