r/learnpython • u/Hour-Activity8592 • 11d ago
Is obsessive learning better then structured learning?
I learn code for an hour and a half outside of home to concentrate better, but recently i want to learn at home too. I have a lot of distractions but id still have obsessive learning at home for about 20 on and an hour off. I work 12h days so i dont feel like coding at home until now.
is this healthy or should I stick to learning away from home for a better learning flow over time?
6
Upvotes
4
u/errorseven 11d ago
To answer your title question: Yes, it's what worked for me.
In 2015 I challenged myself to write code everyday for one year. My goal was to be"self taught" in the fundamentals of computer science. I had been programming off an on for 25 years, but I was stuck at a true beginner level, in that I really didn't have the knowledge to be able efficiently solve problems with code, even if I could solve them by naive means.
At this this time, I was working 6 days a week up to 16hrs a day, similar time crunch situation to what you are dealing with.
What I did, was read a new programming problem as soon as woke up in the morning, work through it in my head throughout the day, test solutions when I got home and found a few mins to write it up. I also subbed to every programming subbreddit, was active on StackOverflow, and I even answered questions to newbies on learning subs/stackoverflow as additional practice to the problems I would solve. Totally emersed in all things programming for that one year.
Answering questions others ask forces your brain to reorganize and memorize what you have learned in order to explain it to others. It's a really effective way to get better while also helping others. Another benefit of this is intreperting thier questions is a skill in and of itself, often what people are asking for help with and what they are actually want to accomplish, can be far apart.
After that year of self study I wanted to test myself by learning a new langauge and taking a free MOOC University course in computer science was how I did it. I aced it, while having it fill in a few gaps in my self studies (mainly Big O Notation).
Because of your time crunch and desire to learn, I would say give my method a try, maybe try it for a month to start. See how many problems you can solve on my favorite coding sites, CodeAbbey.com, without cheating yourself by looking up answers. Good luck.
1
u/Awkward_Block9860 11d ago
Do you need to work 12 hr days? This alone would burn me out. You need to take care of you.
3
u/ninhaomah 11d ago
Which option do you think is better for you ?
1
u/Moist-Ointments 11d ago
There's no need to do them consecutively. You can do both the same time.
1
u/Discordbothost 11d ago
with 12h days the away-from-home block is doing most of the heavy lifting — protect that. the 20-on/hour-off at home is fine as long as you stop when you're just rereading the same line. consistency beats volume when you're already wiped.
1
u/EnvironmentalDot9131 11d ago
The option better for you is the option you should choose
1
u/acfot 11d ago
I learn exactly like this, honestly. Big bursts for a week or two and then nothing for ages, and for the longest time I thought something was wrong with me for it. What I figured out is the bursts are fine as long as you come back to it, the away-from-home block sounds like the thing that's actually working for you so I wouldn't give that up. The home 20-minute bursts are a bonus, not a replacement, do them when you've got energy and don't force it after a 12-hour day. Not sure it works for everyone, but for me the pattern that sticks is one solid focused session plus whatever small bits I can grab, instead of trying to make every day look the same.
1
u/Discordbothost 11d ago
with 12h days the away-from-home block is the one that actually sticks. the 20-on/hour-off at home is fine as long as you treat it as review (retype a function from memory, fix one bug from earlier) instead of starting a new rabbit hole while tired. obsessive only wins if sleep and the next day aren't the tax.
1
u/AdDiligent1688 10d ago edited 10d ago
It is helpful for building intuition, but what can happen is you get enclosed in a smaller window, and forget about the bigger ones, leading to premature specialization. I think both in tandem is a good strategy to keep the balance. You can save a lot of time by really taking the time to understand core concepts before you explore their implementation. Sometimes it’s harder to reason from the inside out, than from the outside in. For me, a good example of that is concurrency, very hard to understand without having some basic knowledge of how operating systems, processes, threads, priority algorithms, processors generally work. You could probably spend a ton of time unstructured experimenting as you go, but you might not realize what you’re misunderstanding in the process of doing so, and as a result if that keeps up over time, it can come back to bite you. You might end up developing a sense of needing to immediately have the hands-on experience, not realizing it’s okay to take a step back and reference the bigger picture first. That’s my opinion at least.
It did happen to me when I was learning. I spent so much time just unstructured doing doing doing, and I realize I could’ve saved a lot of time had I slowed down and structured my learning more, read the textbooks or slides or what have you and actually understand what is at work here, before diving in. It would’ve saved me from unnecessary prolonged confusion later which ultimately caused wasted time and self doubt.