The access to information most people enjoy today is completely and utterly unprecedented. What once required potentially vast amounts of time, effort, and pre-existing knowledge has been simplified and made convenient with modern technology. My father, who had steadfastly sworn by his flip phone up until last year, now uses a combination of voice-activated Google Now and his Chromebook to sling Youtube videos onto his living room Chromecast to learn about anything from model planes to the latest tech craze he's heard me babble on about. How much more inundated are we web professionals (designers, coders, admins, UXers, et al.) with information that we can actively leverage? No more a relevant time and place is this seen than at the start of someone's career into web technology.
Who, What, When, Where, Why Bother?
Any active, user-content driven communities is sure to see a regular chorus of "What should I learn?" and "How should I learn it?" questions. These are almost too easy to answer. Everyone has their personal gospel of favorite things to learn, and sure-fire methods to become a rockstar with them. The more awkward question that can be a deciding point in many ways then becomes "Okay, I read that book / did that tutorial. What now?" Here lies the uncanny valley between concisely understanding the theory of how to perfectly do something, and the ability to do it. Worse, in many cases, the insurmountable obstacle of not having enough experience to be allowed to work to get more, actual experience! Many grand efforts and great talents go to waste right here. After three or four weeks of building a masterpiece webpage involving moving jQuery, smarty-pants SASS, and hand-made graphics, the magic is just kind of... gone. The discouragement often stems from not knowing when to call it "done", or what quality the work done truly is. Even if something seems finished... what do you do next? Pick another specific facet of a language or design theme and start from scratch with that?
Purpose and Momentum
To Err is Human
I may be biased, as I was never very good at learning without a purpose. I've found that most things people do have a cause-and-effect relationship. Even my love of random trivia is directly tied to how much I enjoy surprising (and confusing) people I know. The facts themselves are rather inconsequential to me. The largest reason people lose their way when taking on a task like learning coding or graphic design for the web, is that they've paired their cause and effect too loosely to genuinely feel the purpose. Time and again, I hear very skilled but very confused industry starters say that they're learning all they can today, to get a career tomorrow. Admirable, yes, but highly unlikely if you're still learning. By the same token, though, who wants to buckle down today, if that same payout is distanced by a year or two? There goes the motivation. Instead, it becomes very important to find the connecting dots between A and B to make something happen for yourself. Work backwards, work forwards, however you work, break it down into more approachable pieces. Say you want to get better at your back end coding and you're a movie buff. Try building a database of your own movies, or pick through work done by other professionals. Apply the abstraction of code or design to something tangible that you can care about. Instead of struggling for new ideas and then barely retaining half of what you learn, I promise, you'll be looking back in a few months at the robust projects you haven't been able to stop thinking about, and remember every last hard-fought victory to make them awesome.