A collection of advice and tips organized into loose categories. Looking for additions and feedback. If you want to submit ideas via survey, I've put up a survey on Gorilla Survey!

DBC_advice.txt

+# Learning
  
+#Proper Variable Naming - make the variable name descriptive and concise
  =>don't name after the data structure
  =>avoid numbered variables (var1, var2, var3)
  =>avoid single character names (except for short blocks or indexes)
+#Proper Method Naming
  =>use the right suffix (! or ?)
  =>the name should reflect the method's single responsibility
+#Keep it DRY
  =>condense repetitive code
  =>create methods to encapsulate common functions
+#Write Good Tests
  =>include driver code with tests
  =>tests should include the expectations

+##Principals of Ruby
  =>Consistency
  =>Readability
   =>https://github.com/bbatsov/ruby-style-guide
  +#Apprenticeship
    https://gist.github.com/dbc-challenges/c39818d9d8b056df89b4
    =>Why revealing ignorance helps gain confidence
    =>Focus on your strengths, but learn and understand your weaknesses
  +#Requirements
  +#modeling
  +#planning
    pseudo code
      Script: CONVERT TO PIG LATIN

      Iteration One: CONVERT SINGLE WORD

      GET a word from user input
        IF the word starts with a vowel, don't change it
        ELSE replace the word with its pig latin equivalent
          GET all of the consonants before the first vowel in the word
          SET the consonants at the end of the word and add the suffix "ay"
        ENDIF
        PRINT the pig-latin-ified word
      
      Iteration Two: CONVERT COMPLETE SENTENCE

      GET a sentence from user input
      FOR each word in the sentence
        CONVERT SINGLE WORD
     ENDFOR
       PRINT the converted sentence
     DISPLAY the number of words converted
  +#Pairing
    https://gist.github.com/dbc-challenges/8cf595b275fb2dcfdb15
    =>Dig a deeper understanding of how you feel about pairing
    =>Improve your pairing style so that you get and give more value when pairing
  +#Simplicity
    =>Are you writing a single, gigantic method or breaking down your program into logical units?
    => When you describe what you want to do, does it just sound confusing? 
    => + If you want to do something simple, but have 5 steps to get there, you're probably overcomplicating it.

this would be more readable in markdown :)