Mar-22-2017, 05:45 PM
I think that's fine for small things, but will cause problems for large or novel projects. I wouldn't say you necessarily should change what you're doing, but you might find at some point that you've painted yourself into a corner because of a lack of foresight. You can imagine two options - (1) always consider carefully and it rarely matter or (2) never consider and at some point it bites you. "Experienced" programmers probably have heuristics that allow for a middleground which, while not perfect, is (slightly) less frustrating.
It can also depend on what you're working. If your work is constantly boring, you might be more in the mode of not worrying about it.
And one last thing - whether you think ahead or not, I'm definitely a fan of "get it working first" so while I do try to write Pythonic code the first time, you don't want to re-write as you go if you end up having to make big changes just to get it working.
It can also depend on what you're working. If your work is constantly boring, you might be more in the mode of not worrying about it.
And one last thing - whether you think ahead or not, I'm definitely a fan of "get it working first" so while I do try to write Pythonic code the first time, you don't want to re-write as you go if you end up having to make big changes just to get it working.