Quote:
Originally Posted by mr dave
isn't this ongoing programmer conversation the precise reason any teacher tells you to write out the logic of your code in a flowchart first? 
TURBO PASCAL MOFOS!!! hell, had i gone for a 2nd year i would have potentially learned freaking Fortran hahaha. |
Haha... nah I write it in my head. Those operation documents always seemed like an extra step I didn't need to take.
Programming is incredibly easy for me because of the way it operates. There are no real ambiguities. Only logic and either yes or no and situational arguments. That works for my type of default thinking, although I'll admit I'm less cut out for situations where that's a downfall.
Quote:
|
Totally, I do that too. 'Cause then I can go through the iterations in my head and it's easier to debug when you know what the program is doing in each line.
|
Exactly. You ever tried to debug someone else's code? Ridiculously hard. It could be the easiest program, but if you don't know how they structured things, it's incredibly hard to figure out what's wrong. Even when you see their process, most novice programs insufficiently comment their major code sections and without it, it's like trying to put a square peg in a round hole because both programmers are operating on a different way of thinking.
Quote:
|
Depending on how complex the program is meant to be, I feel like I have less of a grip on things if I have a giant load of if/else statements. But I do know what you mean.
|
At first I was like that, but when I started nesting conditional statements and properly commenting them and arranging them in logical orders, it became less of a situation where I had to read each statement. If you create your code in a hierarchical manner, you do better when debugging because you can spot inconsistencies in a wide-view first, when simply reading each line in its own context is too close of a view for larger-picture issues.