Developing a hobby feels like an exhibition up a treacherous mountain peak.
While buddying hobbyists venture into the foot hills to enjoy the picturesque views, those with a profound interest assess the lay of the land, seeking out more adventurous (and unknown) routes.
It feels like I've reached a similar crossroad in my pursuit to code. Programming is my mountain I want to conquer!
I've been testing the waters over the last 18 months, dabbling in a bit of SQL, then Python, now C# - but never truly knowing what route to choose.
The urge to explore further has been great but like any expert mountaineer I now acknowledge peaks co-exist with crevices.
Metaphors of mountains, summit-climbing and sheer drops equate to fuelling a passion that can withstand set-backs while plotting a path to the summit.
Let's face it, novice climbers don't instantly pack their bags to Kathmandu, neither should I.
Now I admit overkill has been my Achilles heel in the past - "I'd go 0-100 real quick".
If results didn't match my enthusiasm, ultimately my attention would waiver.
Now I appreciate the transition from fleeting interest to life-long passion is long, strung-out and involves various trigger points - not all children who climb apple trees scale cliff faces.
An interest in programming didn't start at a young age, in school I hated Information Technology, born out of frustration of not knowing my way around a computer.
Our first family computer was acquired after dropping IT, I'd spend hours browsing (and deleting) settings before (a tech-savvy Uncle) restoring it.
Early life and even young adulthood, the concept of programming or computer science was beyond me.
After graduating in journalism at university, I went down the PR route but still I wasn't fulfilled.
I quit my job and took an internship in the corporate world, no direction or preferred route, I gave myself 12 months to let intuition guide me.
By chance, I landed in the technology department supporting a release management function with delivery.
IMPOSTER SYNDROME ALERT
The early days were brutal, having to quiz development teams on testing, version control and a whole manner of terms I didn't fully understand, but I loved the challenge.
Being exposed to complex systems and fortunate to have developers explain the nuances opened my eyes to technology.
Even in the beginning, I thought you needed a CS degree to delve into code.
5-years later I’ve realised a CS degree isn’t mandatory, I’ve met developers who range from self-taught, boot-camp alumni and guys who probably coded while in nappies.
At heart, I love learning, analysing/problem solving, and being creative – ultimately I can get this and more by learning to code.
I’ve come to the realisation I want to code and it’s time to seriously explore.
So what is this post all about? Mountains right?
Well no... It’s an introduction about me, my journey so far and the trek to come.
In the coming weeks, months and years I’ll document my ascent, what works for me and what doesn’t with the aim of becoming a solid software engineer.
I have no idea what route I’m going to take, I’m sure there will be setbacks but I’ve determined to climb and figure out the best route for me.
For starters I’ll be tackling:
• Finishing CodeAcademy CS Path (I’ve started it, I might as well finish it)
• Harvard’s CS50x Course (Help with CS concepts and get me into the habit of building using a range of technologies with integration: C/Python/JS/SQL)
• Exercism Python and C# Tracks (Help with problem solving using current knowledge-base and re-factor already-submitted exercises)
• Pluralsight C# Path (.NET is used heavily across my current organisation so it’s a great chance for me to explore frameworks closer to home)
Everything is set, I’ve got my Sherpa by my side (Dev Community ;) ), I hope you enjoy the journey!
Top comments (0)