One of the things I hear from people and my friends is questions about the best way to work with PHP. They always want to know how to get started on a project, what software to use, how to plan it successfully, and so on. In this article I plan on revealing the ďmagical secretsĒ about how I do my PHP programming so quickly with so few bugs.
If youíve read any of my other articles, youíll know whatís coming at this point. Thatís right, grab your paper and pencil. Itís time to be a little old school. Iíve always found that if I draw out my plan on paper that itís easier to code because I know what goes where how it all links together and what type of structure Iím working with. Also, itís nice once youíve been working on your project for some length of time to be able to look back on what youíve already done so that you can easily remember things about your project that you may have forgotten.
Writing down things like declared class names, global variables, function names, and so on really can give you an edge if you get right down to it. Letís say you have two classes, one named load_interface and one named load_ini, or something, then letís say you're one of those type of people who will declare a class with a two-letter variable (and I know there are those of you who do it). Well, if you made load_interface three weeks earlier in the same project, and you didnít use it for all that much, are you really going to remember that youíve used the $li variable already.. really?
Some people may not. Or, letís say that you start a project and then you get someone else to help you out after about a week or two. Wouldnít it be useful to them to know whatís already been used? And would it not help speed up the time it takes them to actually get into the project to start programming?
That just goes to show you -- ďpaper isnít just for breakfast anymoreĒ --well, it never was, but Iím just saying thereís more use for paper than letting it jam your printer.