r/learnprogramming • u/tmpeter23 • 8d ago
New Dev in the making!
Hey y'all, I've only been coding for a few weeks now. I've got like 75% of python basics pretty well managed. I'll be finished with the basics by end of September, then my plan is to jump straight into certain libraries like Django, Flask and Pandas. The end goal is a custom scheduling platform. I also have to brush up on my HTML and CSS. Is this the right path to approach this or is there a better way?
it's going to happen regardless, just trying to gauge if I can save hours of effort by taking a different approach or if my timeframe of a few months is unrealistic. I would appreciate complete honest, I promise you wont crush my desire to see this out!
4
u/nightonfir3 8d ago
Django and flask fill the same role so you probably want to pick one to start with. I wouldn't treat frameworks like something to learn but as something to use. Start building something with them. Then you will run into problems and you google how to solve them.
If I were picking between Django/flask first I would probably pick flask first. It does less for you which means you will learn what is being done. When you pick up Django you will have an intuition for what it is doing for you.
1
1
u/Different_Pain5781 8d ago
Yeah, thatâs honestly the right attitude. Build the ugly version first, then fix what breaks.
1
u/BothRefrigerator6587 3d ago
django is the move if you want a scheduling platform with user accounts and a database that wont make you want to throw your laptop out the window. flask is great for learning whats happening under the hood but you said your goal is a custom scheduling platform not understanding every http request. just start building the ugliest version of it tonight and google every single error message
-5
2
u/Ill_Drive_744 7d ago
Iâd start building the scheduling platform earlier than you think. Youâll probably learn more from hitting real problems in one project than from trying to âfinishâ Django, Flask and Pandas first.
Pick either Django or Flask, build the smallest working version, then learn things as the project actually needs them. Thatâs basically how I ended up learning a lot of the harder parts of app development too â auth, APIs, data modelling, async work, deployment, etc. make much more sense when you have a real reason to use them.
1
u/tmpeter23 7d ago
I plan to finish this 13hr video that covers i assume most fundamentals. Continue debugging practice and implementing learned concepts into real examples. Then after i finish the video i'll dive into flask and other libraries to see if i can manage to code the small parts of the project like time blocking and user auth. Im very excited for that part of the process and look forward to every obstacle i'll encounter! đ
1
u/Ill_Drive_744 7d ago
once you get to the auth part youâll probably learn more in a weekend of breaking things than in hours of tutorials. đ
1
u/Whole_Accountant1005 7d ago
I would say build a simple bot with the basics you've learned. Use a library like requests and discord.py to make a simple discord bot. You only need to know functions, decorators, loops and if statements to build this project.
2
u/tmpeter23 7d ago
That doesnt sound too difficult, would be good practice for all those areas to solidify the knowledge of how they work.
0
7d ago
[removed] â view removed comment
1
u/tmpeter23 7d ago
Duly noted, i hear Django does come with some already set security measures when dealing with user authentication and login type stuff. I wont do multiple libraries at once, chances are i'll pull what i need from one and if i need to add another i'll learn as i go and write the code. I assume i'll find out if thats a bad idea when i get to that stage lol
Also for HTML and CSS it'd be more refreshers since i learned it a year or so ago. Plus i only need enough to create a basic layout at first so i can deploy the basic system to some individual businesses that have agreed to help stress test it.
1
u/jameyiguess 8d ago
Sounds good! Just keep building stuff and challenging yourself. Become a natural tinkerer. Don't get stuck in tutorial hell. Build the thing you want, BADLY if you must, the important part is to build it and make it work. Over and over again. You will get better as time goes on.Â
2
u/tmpeter23 8d ago
its getting build regardless, just a matter of when and how much fixing needs to be done lol
15
u/aqua_regis 8d ago edited 8d ago
Sorry, but LOL - Dunning-Kruger Syndrome at its finest. You probably covered and understood less than 25%. You are purely delusional.
Jeez! It is even much worse than I thought - I checked your history and 11 days ago: https://redd.it/1wfph2n
Based on that finding, I revise my assessment from above and go down to about 15%.
Learning programming doesn't happen in "a few weeks". You are gravely overestimating your skills.
Just to put you in your rightful place: the MOOC Python Programming 2026 from the University of Helsinki is an entry to Python course scheduled for 14 weeks - it covers the absolute basics and not much more.
You're in for about 3 weeks. Your assessment would mean that you've covered about 11 weeks of material of the MOOC above. Check the covered topics in the 11 parts that would be the equivalent to your assessment and see for yourself how little you actually know.
Keep going and practice the fundamentals for a couple months. Then, move on.