1. Comments, don't be shy, use them.

2. Label your programs with meaningful names, then display them so you can find them later.

Code:
  Pause StabilizeTime                 ' Let PIC stabilize
  LCDOUT  $FE,1,  "PROGRAM SOURCE CODE:    "
  LCDOUT  $FE,$C0,"        18F44K22 LCD.pbp"

  Pause DisplayTime                   ' Let PIC source file display
  LCDOUT  $FE,1,  "      PIC BASIC v3      "
  LCDOUT  $FE,$C0,"    18F44K22 LCD test   "
Yup, I finally got fed up of not knowing what programs are in what breadboard.

3. Start with the basics,
  • look up the CONFIGs if you're using a new PIC (C:\PBP3\DEVICE_REFERENCE for PBP3).
  • add a heartbeat LED.
  • add 1 function/feature at a time.
  • keep the use of GOTOs down to a strict minimum.
  • use subroutines when sections of code is used more than once (GOSUBs).

4. Stuck? Come here and use ADVANCED SEARCH feature at top right.

5. Can't find an answer to your problem? Start a new thread in what you think is the most relevant section.

6. Not getting answers to your problem? (it can happen) Google is your friend.

7. If you do find your answer elsewhere, please report back here in your thread to help the next person.

Got more ideas? Share them.

And good luck! I just thought I'd start this 'cause I was royally fed up of not knowing what I left in PICs months ago.