🚀 A guide to keep on learning after Le Wagon bootcamp 🚀
You've just finished some of the most intensive and hardest weeks of your life. But you've made it! Congratulations, you are now full-stack developers able to build great web projects from scratch.
But Le Wagon is just the beginning of a long journey. Being a developer is an incredibly rewarding position because you get to learn new things every day. But it is also a challenging role. With this repository, I want to share with you some tips and resources to keep on improving your skills as efficiently as possible.
One of the most difficult things after Le Wagon is that you won't have teachers and TA anymore to help you every day. Of course, you have Le Wagon community on Slack but it is not as instantaneous as a ticket. After Le Wagon, you should aim at being really autonomous to solve your code problems as fast as possible. To do this, you need 3 skills:
During the bootcamp, you may have seen teachers solving problems you had been struggling on for dozens of minutes just by reading your error message. It takes some practice but learning how to find your error messages and how to read them will solve 90% of your problems. Sometimes it will give you directly an answer, most of the time it will narrow the scope of the problem. Good developers are (almost) always happy when they see an error message because they know it will help them solve their bug.
When the error message does not directly give you an answer, learn how to debug with
binding.pryin my code to see what is going on and how do my variables look like at this specific moment. With good
binding.pryskills, you will rock in the developer world.
P.S: Aaron Patterson, one of the most famous Ruby developer, is a "puts debugger". It is another way to deal with errors. Enjoy this article to learn more.
When you are facing a problem you really don't know, get used to Google it. 99.9% of the times, you will find somebody who had a pretty similar problem on StackOverflow. Google skills are the most important ones for a developer.
Other places you can find some help are: Reddit and also directly on Github, in the issues section. There, you can ask your question to people working with the same tool as you. Sometimes you also get a reply directly from the creator of the project.
I'm talking about these two because they are not as much referenced as StackOverflow but are sometimes more qualitative/recent !
Here are my personal advice on how to progress after Le Wagon. I myself did/read half of the resources and heard really good reviews from Le Wagon alumni about the other ones. You can find free PDF of most of the following books on the web but, if you can, please support the authors. ;)
After Le Wagon, a lot of things look like magic because you don't have time to learn the core concepts. I found it super valuable to get back to the roots and learn more about topics not directly related to a language to get this right! If I was doing Le Wagon today, I would read the resources below directly after it.
If you know Ruby well, Rails will be so much easier!
Because of course!
You should know about some resources. They will help you a ton in your code every day. Here is a list of the main ones I can think of.
If you are a teacher, TA or experienced alumni of Le Wagon, do not hesitate to fork this repository and send me a pull request to improve this learning path. I am sure it could be much better. ;) :sparkles: