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 trialSteven Carbuhn
13,020 PointsAlgorithms related to skill level
I was curious. Is a person’s ability to solve coding algorithms deeply related to a persons skill level and understanding of the language? I was going through some algorithms, and although i would have the idea of how the pseudo code would go–due to the lack of my skill in JS i wasn’t really able to convey those thoughts in clear code to come to a viable and passable conclusion. Also, when you are unable to answer an algorithm, what is the best practice? Should you try to continue thinking it through? Should you look for the methods that you think would help you solve the problem? Should you use the peak function? Sorry I just want to ensure that I’m learning this as it’s intended, and which will be most beneficial to me in the future.
1 Answer
Jennifer Nordell
Treehouse TeacherHI there, Steven! Sorry, I just noticed your request for assistance in that other thread. I like to think of algorithms a little like a Sudoku puzzle. There are many kinds of Sudoku including ones that use numbers, ones that use, letters, and even ones that use pictures and colors. It's the ability to get the solution that's most important here and not the expression of the elements. It's the logical thinking and problem-solving skills that are most critical.
Your coding prowess will come with time, effort, and a lot of patience.
Also, when you are unable to answer an algorithm, what is the best practice? Should you try to continue thinking it through? Should you look for the methods that you think would help you solve the problem?
Absolutely continue to try and think it through. Eventually, you will likely hit a wall where you just can't get it. Go out and look at a solution. Then go through that solution line by line until you understand everything it's doing and more importantly... why. Even if you have to have a thousand console.log()
statements, it'll be worth it if you can see what's happening.
Then, and only after you've done that, treat it like a mandala. Just wipe it all away. Now, for the hard part: reimplement it yourself. No peeking!
This is, of course, just my opinion, but I hope it helps!
Steven Carbuhn
13,020 PointsSteven Carbuhn
13,020 PointsThank you so much Jen for your thorough and elegant answer :) I look forward to applying this knowledge to my coding in the future! This is extremely insightful, and It will help me with the way I approach things