Growing a skill takes time.

As simple as this might be to read these 5 words, this is something I have had a hard time actually practicing.

Yes, this is another of these meta post where I talk about learning about learning rather than what I am learning.

Let’s just say there are 2 aspects to today’s topic. One is how long I have been learning and the second how long it takes to just achieve anything.

Jerome Ydarack, long time student

I am 35. Started learning Python and Data Science in 2016 and in a way, I have little to show for it. No fancy job title. I am not even working in Data Science as of now as I have already mentioned in previous posts on this very blog.

In a way, there is so much to learn in this field. Python (or is it R or Julia), statistics, algorithm, machine learning, vizualisation, graph modelization, agent based modelisation, business knowledge (whatever that means depending on the industry and the company, and the company history, and the project/team you are part of). And that is only at the individual level. Add to that Git, Kubernetes, Dataware Lakes/Datawarehouse/Datamart, Redis, Spark, Hadoop.

And how to manage tech interviews without which you will not be able to do what you are actually aiming to do (but is barely related to the actual job content).

What I mean is that there is a lot to learn. A lot to practice. A lot to understand.

Before even been considered as a potential eventual candidate to a data scientist position.

Any meaningful project takes time

I have been working on my portfolio. Which would have been in a slightly better shape if I hadn’t delete my main Twitter account where I shared most of my results out of spite.

My main hurdle is that my current job is taking a lot of my time (12-15 hours a day) and a lot more of my mental health. So I am only physically and mentally able to work on improving my skills for 1 day a week (usually on Sundays). And I try to find project which I can finish in that timeframe.

Which in turn, limits the kind of projects I am focusing on.

I am slowly changing my approach. Using more project management approach in what I do in my free time, just so that I can do more ambitious and challenging projects. More interesting ones too.

But the switch is hard. And it feels like work. And it is harder to feel progress without going that GitHub commit number contest.

Long story short: my current challenge is still to put projects into more manageable chunks I can tackle over the week-end while still making progress or at least getting the impression I amd making progress.

And this takes time. Alway more time

Final word

If you were hoping for a positive message like “if you put your heart in it, you’ll achieve anything”, stop. I have no such message.

I struggle everyday. Be it Imposteur Syndrome or poor interview skills, I am still not in the field and working in a well-paid but not fulfilling job which makes me push through burnout out every single day. The more I spend learning, the more I discover there is to know. The more I apply just to get a feel of the field, the more I get burnt by template rejection letters without any clue as to what I could do to improve.

Rather than you, this post is addressed to me. To the now-me who is struggling both at his job and trying to enter a field and job he is actually interested in and not just a job which pays the bills. To the learning-me who is going through this and see no end and results any time in the future. And to the future me who is hopefully well beyond this but might need a reminder of the-good-ole-times and what he went through.

If you have read through this. Thank you. Enjoy your own personnal learning ride.