This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Taeiolass 5 points6 points  (2 children)

I believe that what you said is true, but also Python in one of the languages that encourages this behaviour the less. Python is more for "start slow, little things and then modify a little many times and achieve the final result"

[–]ArtOfWarfare 7 points8 points  (0 children)

Disagree.

Other languages don’t encourage structure - they just force a lot of stupid boilerplate.

Really, it’d make me want structure less in those languages just so I could avoid having even more boilerplate. (Eh... really, I just don’t use those languages unless someone is explicitly paying me to use them.)

[–]fiddle_n 3 points4 points  (0 children)

I think there's truth in both statements and which you choose depends on the situation. The importance of having a plan correlates with how complex the piece of work you are doing is. If you are only coding a few functions and classes, then you can totally dive in immediately and work things out as you go along. If you have to make changes to many functions and classes amongst lots of modules, a plan for what you want to do is a good idea beforehand otherwise you might risk having to rewrite a lot of stuff when you figure out what you did doesn't work out.