So every line of code required a punch card (see Episode 1), and obviously for a poor student like me I had to find ways to use less card as each card costed some money. You know, the more bugs the program had, the more cards I needed to re-program (i.e. re-punch new cards). And if the program was in-efficient (e.g. lots of lines to do one simple logic), the more cards I needed as well … So, the solution was (is) Flowcharting.
Flowcharting is not new, but if you asked 100 modern-time developers the question “Which is your favorite programming tool?”. I bet 95 of them will answer “My IDE (Integrated Development Environment)”. And the other five will answer “My hand …”.
But to me, the best tool was (is) the Flow Chart. If one could not draw up a flow chart to describe the solution, I don’t think the program would work. Anyway, if you wanna know the basics of flowcharting, check out here.
Lesson Learnt: Good planning for everything, and for programming it is called flowcharting.
M.Y. Lessons Learnt 