2 replies to this topic

[Fsquad]

I'm not a pro programmer but I do know it is very important to visualise the application you want to program before starting to program on it. As a lot of you probably already experienced, if u don't do it, you'll get confronted with problems that could be avoided if you had taken the effort to make a sequence diagram / Flowchart.

I'd like to hear if some of you pro's take that effort and out of experience can share tips with us new and inexperienced programmers in the form of some sort of guide tutorial. If its possible of course, it is not really something I've seen before.
Thanks

[bay]

Honestly, the more you code, the better you get at it, and everything just works in your mind.

I never really needed to outline anything on paper, because I could understand the concept in my mind and then transfer it straight to code. I'm pretty sure that's the same with most coders as experience increases (as far as the coders that I talk to regularly).

Now, I'm not saying outlining is useless, or you shouldn't do it, because everyone is different, and different things work for differen't people....but something I do think is very important is commenting code, even when you yourself coded the project and understand how it works, because trust me, you'll eventually go back to that project months down the road for an upgrade or out of curiosity, and if its 500+ lines in OOP (Object Oriented PHP) it's a nightmare to parse in your brain again (trust me, i've been there). Comments help a lot, especially if more than 1 person is working on the project at once.

[Fsquad]

Yeah i guess the more experienced you get at it the better you transfer idea's straight in too efficient and clean code.
Thanks for the reply.