This is a highly opinionated, pseudo-motivational, unconventional and almost rant-like developer roadmap article.
This article is more than a compilation of best books/videos/courses to learn Python and covers the bigger issues that a beginner/early-intermediate faces on their journey. These are the undocumented problems Stack Overflow does not solve.
Why Python ?
Why should you learn Python anyway? Why not one of the 20 other languages trending right now? As you’re beginning your journey, this questions crops up multiple times (a day).
Picking your first programming language is a lot like picking a starter pokemon.
The inherent capabilities of a language are less significant than the skill of the programmer in using said language and their grit to make it into the big league.
If you want to start with a different language, do yourself a favor and stop reading this article. You’ll have a higher chance of success if you stay confident in your decision and focus on your next lesson. It doesn’t matter what language you pick. But once you make a decision, you need to stick with it.
There’s an overwhelming amount of noise on the internet about language/framework comparisons. Enough to give any sane individual a serious shock of analysis-paralysis or to make them doubt their decisions and abandon ship.
I’ve seen early intermediates claiming to know 3–4 languages. They tend to know all the trivia about 4 but can program in none. A result of wanting to try out everything without the commitment to stick with one.
Python is a seriously well-designed language. Also, there’s plenty of documentation and tutorials available online. And, it’s used in a lot of fields so no matter what your level is, there’s plenty of things to explore. But the same is true for most of the other 20 languages.
Every language has it’s pros and cons along with the use cases it’s best suited for. The 3 most popular uses of Python are data crunching, writing web application back ends and automation scripts. Python is arguably the best language for beginners due to the underlying principles of the design of the language that focus on clarity and simplicity.
There will always be voices telling you that you’ve made the wrong choice. 9 out of 10 times, those voices belong to people who are trying to sell you something or are troubled with serious insecurities.
How Python ?
Now that you’ve made your choice, let’s talk about learning Python.
It’s simple. Pick a tutorial and complete it. Then, pick another. Rest and Repeat.
A single book or video course will not cut it. You need continual exposure to code, along with progressive overload. Patience, persistence, commitment (and a bunch of other cool qualities) are required !
I’ve come up with a basic flow of what I’d advise a beginner to do. If you’re human (last time I checked, AI wasn’t interested in learning python, yet) your version of the roadmap will vary. Just use this for reference. It’s important to know when to move to the next level. Most people do it too late.
You might prefer to pick a course on edX instead of reading a book. The overall process is more important than the individual tutorials/courses you pick.
- Build a strong foundation by reading books.
- Follow the tutorials that teach you to accomplish a single task with Python, like sending email or writing files. This will introduce you to the useful packages and libraries available to a Python developer.
- Inculcate a habit of reading documentation. Build small apps by using the libraries available.
- Gain a deeper understanding of the language and it’s tools. Learn what the experts in the field are working on.
- Go straight to the source.
Here’s a list of useful Python resources if you’ve exhausted the ones in the diagram. Best Python Resources at Full Stack Python.
While following any tutorial, make sure you code along the way. Merely, reading the code examples isn’t enough.
Learn General Purpose Problem Solving
There’s a subtle difference between learning a language (or framework/library) and learning to program. It’s like comparing water colors to painting.
Before you pay for a ‘Full Stack Web Developer’ course, just know that it will not make you a good programmer. It will only teach you a particular procedure to tackle a simple problem (yes, the web apps built in most of these courses are indeed simple problems). Knowing the procedure is good, but being able to devise your own procedures is brilliant. Pay attention to programming constructs, design patterns and algorithms. These are not specific to Python and remain the same for almost all languages.
Do it long enough and the pattern will emerge.
If you get stuck (you will, several times), try to solve the problem before you start running in the other direction. There is a very high probability that someone, somewhere has faced the same problem before and the internet has documented proof of it. Search for the solution on the web. Also, the Python community (subset of the world’s population that use Python and actively participate in connecting with other Python programmers) is very welcoming. You can always ask people for help. Join the Python channel on Gitter.
Wow Python !
There’s a lot to learn in Python. It’s used in a whole bunch of fields. Do not skip the basics and jump to specialize in a particular field. Learning PyTorch should come after packaging, Django after Virtual Environments. Having in-depth knowledge of Python pays off in the long run. It will result in less time spent debugging your programs while you’re working with your super special library.
How Long Does It Take ?
It takes time to learn something well. Way longer than most people tell you. You cannot become an expert programmer in a couple of months. Good things take time and effort. I would recommend that you focus primarily on Python for at least an year. There will be distractions and diversions, avoid those. But don’t be scared of branching out to learn new things. Python is not the only thing you need to become a well rounded developer. Learning Git, Markdown, HTML pays off immensely. You might also need to pick up JS or statistics along the way.
Be a learner forever, but not JUST a learner !
Understand the Learn/Build cycle
There are two phases in any creative/scientific endeavor that keep repeating.
The Learn phase, where you should focus on amassing knowledge. Read books, complete every tutorial and explore what’s already been done.
The Build phase, where you create something by applying the knowledge gained in the previous phase. Stop doubting your skills, tune out the noise that says you can’t and write your own app. Only when you’re done, go back and learn again.
Balance the two phases. Have a month or two month long Learn phase followed by a month long Build phase. Most people are too scared to start the Build phase.
Become a student of the game.
Explore everything about your language, learn about the pioneers in your field, ask questions, learn why something is designed the the way it is.
There will be a time when you would be following Kenneth Reitz on GitHub, listening to Talk Python on your commutes and complying with pep8 in vernacular writing. And, you’d do it not because you need to learn, but because you want to know.
Thanks for reading, drop a few claps if you enjoyed. Check out some other posts I’ve written, follow and reach out to me on Twitter.