Week 1 of AlphaCamp: How can I improve and change bit by bit

vincent
vincent
Aug 22, 2017 · 2 min read
  1. Practise Ruby using LeeCode
  2. Git commands
  3. Problem|Solution→Idea→Views|Posts →Must|Should|Can|Won’t →Wireframe

Problems I faced

  1. While Wee-liang go thru the Ruby LeeCode exercises, lectures, difficulties in taking notes while listening
  2. Write programs using unfamiliar or difficult methods/functions, resulting in taking longer hours to debug.
  3. Cannot VISUALIZE the program codes which I am writing
  4. Take longer to debug program
  5. Went blank on STARTING to learn how write a new program code

Solutions to problems
1. Since I am new to programming, WRITE DOWN ONLY KEYWORDS mentioned during the lecture. When have time, find similarities between KEYWORDS and place them together

2.1 Practise unfamiliar or difficult methods/functions on Ruby Compiler(repl.it) using simple expressions to understand before pushing to the main Ruby program

2.2 TickTacToe — Try not to write NEW INPUTS on the main program, bec u may be debugging the whole program inclusive of the NEW INPUTS. Test the NEW INPUTS on Ruby Compiler(repl.it) before pushing to main program.

3. Make a simple (column-axis or row-axis) table to easily visualize and go thru what the program really executes. Try not to use a (row-axis&column-axis)table because it is harder to visualize.

4. Use puts or inspect(p) to debug the program or cut out a smaller program out of the main program and test it on Ruby Compiler(repl.it)

5. Number of ways before starting to write a new program code

  • Input/output expectations
  • Find out the underlying problems between input/output
  • Break the problems into sub-problems

Need to improve for Week 2 based on week 1 (problem & solution)

  1. Take notes to write down new keywords without caring for the organization bec it is impt to listen to Wee-Liang first

2.2 Test out unfamiliar html/css elements using codepen first before executing to main html/css programs

2.3 When encounter html/css main program problems, cut out a smaller html/css out of the main, test it using codepen before putting in main html/css programs.

3. None

4. None

5. When starting new html/css

  • Input/Output expectations
  • Find out in-between problems
  • Break problems into sub-problems

)
Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade