gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Add new tip (#25610)

Browse Source 
An idea that has helped me in the past.
This commit is contained in:
Bcardona21
2018-11-25 22:08:19 -06:00
committed by Randell Dawson
parent 513d0dfc8a
commit 2aeb03d17d
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
guide/english/miscellaneous/tips-for-your-coding/index.md
View File

@ -9,10 +9,7 @@ This list was created by compiling common issues and questions when working on t
3. Use the chrome javascript debugger console in conjunction with something like the netbeans IDE or sublime text to write your code. Both are free to download. The freeCodeCamp code editor is great but you can get a lot more feedback on your code's behaviour by using chrome's JS debugger and a bunch of **console.log(myVariableGoesHere);**
4. Posting your code in Gitter is as simple as adding a line consisting of only 3 backtics **`** then your code in a new line and another line with 3 more backtics.`
5. Ask for help in Gitter! I can personally relate to staring at a problem for hours, then seeing the solution as soon as I try to explain it to someone, or having someone say something like "typo on line 6" as soon as they see it. Take advantage of message boards and social media groups as well as in-person peers to attempt to have a fresh set of eyes glance over your work.
4. Use your resources. Stack overflow is your friend, and so is Google. However, don't limit yourself to just non-human resources. Sometimes talking about your code to a real person is enough to get you back on track, or spur some new ideas.
References