ZOD: How often should you code?
ZOD: How often should you code?
Zen of Data Science #4
The Big Idea
How often should you write code?
The short answer? Every day.
The long answer is everyone’s circumstances are different, and you should write code as often as you can.
But here are a few key points:
What’s Your Goal?
If you’re already working in a code-related job, you probably don’t need to study code daily. You can if you want, but you’re already learning on the job, so a few sessions a week to supplement your learning is enough.
But if you’re trying to land your first role in tech, then study as much as you can. Aim for 1-2 hours a day of genuine concentrated study. That’s enough to get you VERY far within 6-12 months.
Frequency > Volume
It’s better to study code for 30 minutes daily, than to study one day a week for two hours. You learn more through repetition, and giving your mind a chance to recognize patterns over time. So opt for more frequent coding, (even if it’s less time), instead of longer marathon sessions once or twice a week.
Be Imbalanced for a time
Work life balance is a lie. Life if not about being balanced, it’s about periods of intentional imbalance, followed by periods of “balance”.
If you’re trying to land your first job in tech, you might have to be imbalanced for awhile. Communicate this to your family and friends. Let them know what you’re doing, and for how long.
You can go all-in on coding for a few months, and then regain some balance. If you’re willing to forego balance for awhile, you can make huge progress. Just be sure not to do it for TOO long. Because what’s the point of success in coding if you neglect your family, health, and hobbies to get there?
What I’m Learning
I’m working on my Master’s capstone project. It’s titled “Correlation and Regression Analysis of Wine Prices and Quality Ratings”
It’s the last thing I need to submit to earn my degree, and I’m looking forward to doing the analysis! It’s one of the best ways to touch up your skills, and experiment with new technologies.
If you’re struggling to find datasets or project ideas, use Kaggle.com
You can find thousands of datasets and projects submitted by real people to get you started.
Quote of the Week
“One day at a time. It sounds so simple. It actually is simple but it isn’t easy: It requires incredible support and fastidious structuring.”
— Russell Brand
Landing a job in tech is a long journey. You can’t focus on how long it will take, or the what-ifs. All you can do is take it one day at a time.
Focus on what you can do today. Apply for jobs, study, build. Take pride in those things… they’re achievements in and of themselves.
One day at a time. Everything else is out of our control.
Something Interesting
Have you heard of a “Second Brain”?
If you’re someone who loves to consume knowledge, you should really consider setting one up.
I’ve been using mine a lot lately for all kinds of idea generation, and to keep my mind clear and more efficient, and it’s a game changer!
I personally use Obsidian (it’s free), but here’s a video explaining the concept for those interested.
Feel-Good Finds
I watched the movie “A Quiet Place: Day One” with my wife this weekend. It was a great movie, but I especially loved the relationship between the protagonist (phenomenal actress) and her cat, who somehow managed to stay quiet (unlike every cat I’ve ever met).
A great movie, with a surprisingly feel good story. I’m recommend checking it out.
Thanks for reading!
If you’d like more of my work, consider subscribing to my personal newsletter:
Every Sunday I send out a mini essay on something related to self-improvement, philosophy, etc.
If you enjoy what I write here, I think you’ll enjoy that too.
See you next week! 👋