Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Doron Geyer
Full Stack JavaScript Techdegree Student 13,897 PointsTrouble shooting methods
Steven Parker tagging you because you usually have useful answers. Also I have noticed you are extremely good at troubleshooting JS and finding errors, do you have a methodology you follow like check variables and methods camel case first, then compare variables etc. Or do you just read through and go by experience. not sure where to post this.
But I feel that perhaps there are more experienced programmers here who have learnt a method for debugging that works for them. Almost like you get BODMAS in mathermatics for Brackets, Of, Division, Multiplication, Addition and Subtraction.
Would love to get a couple of tips from you and any other experienced coders, because I often find I miss something simple like using .className and then one of them I randomly put in classname instead of upper case name.
Thanks for reading/responding. Doron
1 Answer
Steven Parker
231,172 PointsYou didn't tag me (and I'm flattered that you intended to) but I happened to see this anyway. To tag someone, you must enter a "@" symbol before their name, and then when you type it a pop-up will appear with a list of matching (or nearly-matching) users. You then click on the user in the pop-up to create the tag.
But since there are many regular contributors to the forum, I recommend asking new questions of the general membership first, and then adding tags later (a day or so) if you haven't gotten a definitive answer yet.
For troubleshooting it never hurts to check for typos/misspellings including case mismatch first, since that's a common issue. But otherwise, it's mostly just the nature of the issue that will provide the clues. For most forum questions, it's rarely necessary to do actual debugging, though sometimes it takes observing the issue happening in a forked snapshot to really make the cause clear.
Doron Geyer
Full Stack JavaScript Techdegree Student 13,897 PointsDoron Geyer
Full Stack JavaScript Techdegree Student 13,897 Pointsthanks for the response, weird I did use @ before hand, perhaps I hit enter instead of clicking on your user profile. Thanks for the response. I thought it would be an experience thing, but never hurts to check if someone has a method to make approaching the task easier.