Day 7 of #30DaysOfDataScience: on slowing down to learn the why 🧠
8 posts in, and the biggest thing I've noticed is the learning curve hiding behind "best practices".
So much of what we code is industry best practice we follow without stopping to ask why. Each prompt in this challenge has made me slow down, hyper-focus on a single concept, and find creative ways to explain and build within its constraints.
Some days were slow. Some days I had the technical idea but couldn't find the right words to explain it; other days the words came easily and the code didn't.
Even so, it's had a really positive effect on both my technical and creative skills.
Want to try it? The prompts come from a small Python script I built that picks a topic and a set of constraints each day. It's open source: dev-prompt-generator. Grab it and start your own 30 days.
And if you have a moment, I'd really value feedback on any of my posts so far.
Cheers!
