Reddit reviews Algorithms in a Nutshell: A Practical Guide

Essential Algorithms

Algorithms in a Nutshell

Mastering Algorithms with Perl

Mastering Algorithms with C

books and practice, practice and more practice:


check this one: https://www.amazon.com/Algorithms-Nutshell-Practical-George-Heineman-dp-1491948922/dp/1491948922/ref=mt_paperback?_encoding=UTF8&me=&qid=

Just did the sample problem and was extremely humbled.

https://www.amazon.com/Algorithms-Nutshell-Practical-George-Heineman/dp/1491948922/ref=sr_1_28?ie=UTF8&qid=1494523732&sr=8-28&keywords=data+structures+and+algorithms

I would focus more on deciding what you want to make. When you can make something that works, you're a programmer. When your code isn't brittle, is well commented/documented, is "clean" and other devs can understand and work with it, you're a good programmer.

So pick something you want to create and make it: a website, a simple program, a game, etc.

How to go about it? Once you have that thing you want to make, break it down into bite size tasks and start tackling them one at a time. First, you'll need to figure out what language and libraries you need (or want) to use. Then set up your dev environment and get a "Hello World" example to work. Then just start building piece by piece. Once it works, make it work better (i.e. refactor it).

I use a bunch of resources to be a better programmer:

• dev blogs (a google search for "best <insert your field here> blogs" should give you some good ones
  
  
• books for the basics. I can particularly recommend Code Complete 2, The Pragmatic Programmer, Head First Design Patterns, Design Patterns: Elements of Reusable OO Software and Algorithms in a Nutshell
  
  
• Tutorials. I love a good tutorial. The trick is to find one written by a professional (usually on a blog you trust or from a tutorials site that vets the content, like tutsplus). Unfortunately, any asshat can throw up shitty code and call it a tutorial, so be careful googling and look at the comments first to look for people calling out issues. As you get more experience, you'll be able to spot 'code smell'.
  
  
• pair programming. I hate pair programming. I instantly lose my ability to type or form coherent thoughts when someone is lurking over my shoulder. I am constantly terrified that someone will think I'm stupid. But it works.
  
  
• fellow devs. Nothing really replaces direct communication with another dev. Find someone or a community online or at work who you are comfortable with. Someone you can go to when you're stuck or don't get something. The difference between needing babysitting and needing help is having specific questions. Instead of saying "I don't understand x", approach them with a more specific question like "I'm trying to get comfortable with closures so I set up a simple counter, but instead of counting to 10, I get 10 printed 10 times, can you help me spot where my error is?"
  
  I hope that helps.