Explore our extensive collection of courses designed to help you master various subjects and skills. Whether you're a beginner or an advanced learner, there's something here for everyone.
For all the self-taught geeks out there, here is our content library with most of the learning materials we have produced throughout the years.
It makes sense to start learning by reading and watching videos about fundamentals and how things work.
Full-Stack Software Developer - 16w
Data Science and Machine Learning - 16 wks
Search from all Lessons
Curated list of small interactive and incremental exercises you can take to get better at any coding skill.
Curated section of projects to build while learning with simple instructions, videos, solutions, and more.
Guides on different topics related to the technologies that we teach in our courses
Every week, we pick a real-life project to build your portfolio and get ready for a job. All projects are built with ChatGPT as co-pilot!Start the Challenge
A tech-culture podcast where you learn to fight the enemies that blocks your way to become a successful professional in tech.Listen the podcast
First of all, please ask questions!!!!!! We cannot encourage this enough - asking questions is the best way for all of us to learn and understand. For your programming teacher, student's questions are a great source of information to understand areas of weakness, level of understanding and pace of learning. Questions are also the most powerful way to seek an end to frustration.
When working remotely, you have to pay lots of attention to the way you communicate your ideas, questions, etc.
Believe me when I tell you that following these steps will get you straight answers in a matter of minutes instead of having to go back and forth. Here is a guide on how to ask questions by stack overflow.
Let's compare these two questions:
Do you notice how the second question is much easier to answer? You will probably get an answer in a few minutes since it will be very easy to review your code and give you feedback in a few lines. Who knows? Maybe the coding error is just a typo!
Use screenshots to keep color highlighting and formatting as you see it. Pasting in "text snippets" can cause more confusion for those trying to help you. If you do paste in text through slack, make sure to use "code block".
You can use a plugin for Google Chrome such as Awesome Screenshot.
"How can I START this exercise" or "I tried X approach but it did not work, what am I doing wrong?" (including any error messages!) will give you much better feedback than "how can I SOLVE this exercise?" - the more you break down the process into methodical steps, the easier you will be able to understand the issue as a whole.
Take around 20 minutes to try and solve the problem yourself by using terminal responses, searching online, and developing a strategy for testing within your code. Finding the specific answer will help you during that problem, but creating an effective problem solving strategy will serve you time and time again!
Slack is the perfect tool for this, you can even start an instant video call with the responder. Avoid using traditional less effective methods like phone or sms.
Enter the #public-support channel which is where you will be served quicker.