Journey to My New Career: Learning & Practicing
Tags: html, css, beginners, productivity
Published: 2019-07-11 01:29:03

In today's entry I wanted to share how I learn and how I practice those things so I can say I've <em>truly</em> learned something.

Does this mean I don't forget anything? Of course not! However, I feel that these skills are something not taught or spoken about often enough.

##How I Learn##

<ul>
<li><a href="https://teamtreehouse.com/">Treehouse</a></li>
<li><a href="https://www.google.com/">Google</a></li>
<li>Practice</li>
<li>More practice</li>
<li>Even more practice</li>
</ul>

Being a musician I learned a wealth of practice techniques. We'll touch on a few later, but as you can see above I like to do a lot of practicing.

Treehouse is my first stop for learning something new, even before Google. I know there are free options out there such as <a href="https://www.freecodecamp.org/">freeCodeCamp</a> or <a href="https://www.codecademy.com/">Codeacademy</a> (which also has paid tiers) but I enjoy the structure that Treehouse offers. I have also tried using Codeacademy in the past and was not happy with it - even with the paid membership.

Treehouse has provided me with a place to easily pick up something new with great videos and workspaces. Whether I put in 30 minutes or 6 hours I can achieve something on Treehouse no matter what. So why is structure so important to me?

Well it's because I've never been a good student. What I mean by that is I have always wanted to jump from A to Z, never having to learn the other 24 letters in the alphabet. Following the Front End Web Development track has kept me on course and going through the entire alphabet.

![](https://thepracticaldev.s3.amazonaws.com/i/n2pyj81aen9z73kjbswz.jpg)

When deciding to devote 110% of myself into learning Web Development I told myself I wanted to have as solid of a foundation as possible before adding anything else. That meant learning HTML really well before adding CSS, then learning CSS really well before adding JavaScript. I'm currently (trying) to learn Vanilla JS really well before adding a library - I'll be learning React first.

Over the last 2 months I have gone through over half of the above mentioned track. While the track is only a total of 56 hours, I have spent a lot of time working on projects as well as practicing what I've been learning. On top of working a full-time job, maintaining a relationship, re-finishing my apartment, and more. My story isn't unique and I know people that are working in this field now that had less time to learn than I. This is <em>my</em> journey.

When I'm at work I often can't devote more than 10 minutes at a time to coding, although I'd love to devote the entire day to it. When I started using flexbox I would just create a new project in VS Code from scratch and practice not just the HTML side of things, but also learning how to properly use flexbox. <em>Side note - I'm still not a master but I'm much better than I was.</em><hr>

###Google###

<em>"Ok Google..."</em>
Google is also a great place to learn, however, you need to be smart about what information you listen to. The internet is an expansive space, and working in a field where things are always changing makes it extra important to make sure you are looking up and learning from the most up to date and credible sources.

Some of my favorite places to look for answers are <a href="https://stackoverflow.com/#">Stack Overflow</a>, <a href="https://css-tricks.com/">CSS-Tricks</a>, and of course, <a href="https://dev.to/">DEV Community</a>. 

I also want to give a shout out to <a href="https://www.youtube.com/channel/UCu1xbgCV5o48h_BYCQD7KJg">Chris Sean's</a> discord channel, <a href="https://discord.gg/HctAeFh">#devslife</a>. Everyone in there is extremely friendly and happy to help.

While the above sites are great, you <em>do</em> have to become proficient at Googling, as any experienced dev will tell you they Google <em>quite often</em>.<hr>

![](https://thepracticaldev.s3.amazonaws.com/i/3ouwmz3079knnt4686eg.jpg)

This brings me to practicing. A viola instructor once said to me <em>“Practice does not make perfect. Practice makes permanent..."</em>

This is a partial quote from Sara Kay's <a href="https://shopsarahkay.com/product/no-matter-the-wreckage-signed-book/"><em>No Matter the Wreckage</em></a> and it has rang true for me in so many parts of life. For me, there are many parallels between playing viola and coding. Without further adieu, here are 3 of my favorite practicing tips that you can tryout yourself:

<ol>
<li><b>Isolate the difficult parts</b></li>
  Pick apart your code and separate the stuff you can do easily from the stuff you struggle with. Practice the difficult parts by themselves (isolation) and learn them more thoroughly before re-introducing it to the rest of the code.
<li><b>Slow things down</b></li>
  Don't try to speed ahead just because you are excited. Trust me, I know how difficult it can be but <em>trust the system</em>. You shouldn't go from learning HTML to messing around with Bootstrap in the same day.
<li><b>Take a break</b></li>
  This has been stated by others but if you are struggling or <em>just</em> not understanding a new concept or why something won't work, take a break! Go for a 15 minute walk, do some bodyweight exercises, whatever will help your brain stop working so hard for a little bit. This has proved invaluable to me.
</ol><hr>

###That's All Folks!###

Well, not really. I had more written but I decided to break it up into a couple of articles so as not to keep you here too long.

Coming up next is a look at the first iteration of my site along with the recent redesign I just completed...for now. As I am learning my portfolio site is a constant work in progress.

Thanks so much for reading and if this helped you at all let me know in the comments down below or share it with others you think could benefit from it!