>One thing that's telling here . . . you say you did the pseudocode and flowcharting in high school and college but never in a real job. I think many people here can relate to that (including me). There's a pressure to get something out the door and design is often the first thing to go under that pressure. Some programmers are better than others when they forego design and it's often easier to go without design on smaller projects, but the big projects really need it. Find something that you think is effective and you're comfortable with and use it. Unit testing is the latest fad and there's a unit testing product for VFP - so that's one more option in the stable.
>

We do have a design document, but it's more of a word document of what the client wants in the end. Mgmt is looking at the number of reported bugs and was looking at ways to reduce it. One of the ideas was to make developers write a more techincal design document or pseudocode before they start programming. I'm not convinced that it will.

Also we aren't sure if the number of bugs reported is high or not this is the first go around at even looking at the numbers, but I guess that doesn't matter because Mgmt thinks they are high.