DEV Community

Anthony Maxwell
Anthony Maxwell

Posted on

Finding your own style

Following a message, I've decided to jot down an outline of how I've been learning to code. I have to admit, that I am fully aware that I have chosen the scenic route, but I'm in now rush and for me, it's important to understand before moving on, Though I admit, as I come to the end of one subject I begin my next so there is a little overlap. (currently I'm completing HTML and CSS and I've started some JS reading, more on that in a bit!)

So, my approach to learning to code: I have actually been using a number of different sources, because I found the "read this, do that" method wasn't really working for me, I found that by combining that with a mix of video lectures - I would actively listen and take notes followed by my own practice, I'd create simple pages and tinker with the styling - I can't stress how important it is to write the syntax over and over, because missing a simple semicolon can mess things right up!

I also love having a decent reference book to review and highlight it until it's begging for mercy! I would recommend 'Responsive Web Design with HTML5 and CCS' by Ben Frain. It assumes you have a basic knowledge and it builds on that. I found the Jon Duckett 'HTML & CSS Design and Build Websites' book to be a little out of date, it does have HTML5 semantics, but they seem to be bolted on at the end of each chapter. I refer the the Frain book a lot and I find that after I've learned about a certain subject, say Flexbox, I'll then read what he has to say. Usually he goes into a little more depth.

A little tip that has worked for me: I found that when I designing a web page, that by sketching it out as a rough guide this allows me to identify containers and chose the correct semantics, as I am a visual learner.

I do find though that it's important to follow a structured curriculum, so I have been following The Odin Project, where a lot of activities so far have been through freeCodeCamp, which is fine, but I lacked understanding using just that source. So therefore by jumping between sources this does leave for some repetition and overlap in stuff that I'm covering, but I found that it has really cemented by learning. For example I couldn't get my head around CCS Grid Syntax, so I found a lecture (Traversy Media, honestly - it's fantastic) and as I wrote my notes it suddenly clicked. I have purchased some courses of his on Udemy, as well as a JavaScript course which I am looking forward to starting soon.

I believe that using git is really important, so I code on a Linux OS (Ubuntu) and I use the command line as often as I need to, logging commits and sometimes pushing stuff to github. I think it's important that that becomes more of a habit that anything.

I should be done with HTML and CSS in the next week or so, as I code each evening or listen to lectures, and then I'll move to JS; I have started reading 'Head First JavaScript Programming' (Freeman/Robson) which really breaks stuff down in a very simple way, and uses a lot of visuals so when I come to that part of the curriculum I'll have a very basic understanding. I also picked up a copy of Flanagan's Definitive Guide to JavaScript which is also really good, but not as simply written.

I admit, it's probably not the most efficient way of learning, but revision is important, I think part of the reason I'm doing it this way is my lack of confidence, learning this stuff isn't difficult some people will take longer than others, sometimes I am going through stuff and it's almost painfully easy, but others I need to focus more. But that's the same with everything, I guess.

So that's how I'm learning to code. I'd love to hear how others are also delving into their own self-learning!

Stay safe!

Top comments (0)