Dev-as-you-go | Day 3 of 100

I have fought losing battles with 'learning how to code' in previous years. From MatLab for University work to python for my profession, I can say I have never felt 'fluent' in any programming language. This certainly is not due to any lack of learning materials! In fact, in most cases, there is often too much choice. The vast ocean of great online courses is enough to swallow a newbie whole. My advice to any newbies, pick one quick and get started!

Saying that I would often stick with these courses for about two months learning a great skill along the way before wilting and finding some poor excuse for a blocker to my progress. Akin to the withering of the learning habit, my fluency in whichever language that was flavour of the month also waned. The net result being that I believed I had returned to square one, and would leave it a good six months before picking up the next trending language.

However whilst making some very basic CSS tweaks to this blog today, two things dawned on me which were a shift in perspective.

  1. Working or studying with a distinct end goal and tangible benefit (e.g. making your blog pretty) gives your learning much greater stopping power.
  2. Whilst I may have forgotten the majority of any given language, I have gained skill in logically deconstructing problems and constructing solutions, more generically speaking.

The latter of which is most certainly beneficial in my professional capacity. So not an entirely wasted effort for all you type As out there!

This also led me to realise that perhaps there are others like me out there! A new age breed of semi-developer that does not know any language in too much depth, but instead learns just enough to get by in the short-term. Is this solution-based, dev-as-you-go approach a more attractive 'sell' for computer science in the long-term? Do most people learn computer languages this way?

#100daywritingchallenge