View Single Post
  #4   Spotlight this post!  
Unread 24-05-2009, 17:00
rsisk's Avatar
rsisk rsisk is offline
The GURU Channel
AKA: Richard Sisk
FRC #2493 (Robokong)
Team Role: Mentor
 
Join Date: Jan 2008
Rookie Year: 2007
Location: Riverside, CA
Posts: 2,748
rsisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond reputersisk has a reputation beyond repute
Send a message via MSN to rsisk
Re: The "Right" way to program

Figure out what is needed, this can sometimes be the hardest part. View things from the end user's needs, talk to domain experts. These are your drivers, your builders, game experts, etc. Remember, you are making something they will use and you must support their needs.

Write down 4 or 5 features you are going to develop, code them to completion all the while testing out code as you write it (this is what you are currently doing), then test the completed system.

The entire time, keep your 4-5 features in front of you to make sure you are not missing your goal. Stay focused. Avoid feature creep.

If your features are too big to easily develop, break them down into smaller features. Still too big, break them down further. A process known as reiterative decomposition.

This basic strategy has served me well for the last 30 years of developing software. Especially once I figured out to view my solutions from the end user's perspective rather than from a developer's perspective.
Reply With Quote