I usually start by writing comments first in plain English based on a variation of psuedocode. That way I'm focused on process first without distraction. Comments are the plan. Clearly articulated steps like any good cookbook. Easy to translate into any language.
// 1. Write plain English psuedocode.
// 2. Translate into scary looking code blocks.
// 3. If maintaining, remember to update comments first (goto Step 1, then Step 2).
The irony is another developer once claimed that my code was generated by a machine. Apparently it was too methodical to be human. Like that was some excuse for him to write crappy code. Urgh! To be great at anything, you need to have excellent communication skills!
// 1. Write plain English psuedocode.
// 2. Translate into scary looking code blocks.
// 3. If maintaining, remember to update comments first (goto Step 1, then Step 2).
The irony is another developer once claimed that my code was generated by a machine. Apparently it was too methodical to be human. Like that was some excuse for him to write crappy code. Urgh! To be great at anything, you need to have excellent communication skills!