I've been learning Python for a few weeks and feel comfortable with many of the basics, though I know I still have plenty to practice. My plan is to finish the fundamentals, improve my HTML and CSS, and then start exploring tools such as Flask, Django, and Pandas while working toward a custom scheduling platform. Is that a sensible progression, or would another approach save me time? I'm mainly trying to understand whether building a basic version within a few months is realistic. I'm learning for personal interest, so I'm prepared for the project to take much longer if necessary.
3 Answers
Build the project even if the first version is messy. Starting with a small, limited version will teach you more than staying in tutorials indefinitely. Break the scheduling platform into simple pieces, such as creating users, adding events, displaying a schedule, and saving data. Improve each part as you learn. The timeline may take longer than a few months, but that’s normal—the important thing is to keep making working versions.
A few weeks can be enough to get started, but it usually isn’t enough to truly understand all the fundamentals. Don’t worry too much about estimating your skill level right now—keep practicing, solve small problems, and build a few complete mini-projects before judging your progress. A structured beginner course can help fill in gaps, but consistent hands-on practice matters more than rushing into advanced tools.
That makes sense. I’ve only spent around 25–30 hours learning and applying Python, and I haven’t completed a full small project yet. I’m treating this as a long-term hobby, so I’m fine with improving gradually rather than expecting to master everything quickly.
Django and Flask serve similar purposes, so start with one rather than trying to learn both at once. Flask is a reasonable first choice because it provides fewer built-in decisions, which lets you see more clearly how the pieces of a web application fit together. Build something small with it, run into real problems, and learn the relevant solutions as you go. Later, Django’s conventions will be easier to understand.
I’ll focus on Flask first and build from there. I like the idea of learning the framework by actually using it instead of trying to memorize everything beforehand.
That’s the plan. It will get built eventually; the main variable is how long the first version takes and how much cleanup it needs afterward.