DEV Community: Anthony Maxwell

Finding your own style

Anthony Maxwell — Mon, 08 Mar 2021 20:55:54 +0000

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!

To
or not to
? That is the question...

Anthony Maxwell — Fri, 05 Mar 2021 22:06:06 +0000

I am starting to appreciate the fact that I came late to the coding game, and one of the things that I am appreciative for are HTML semantics; and how HTML5 brought a plethora of tags that have both vastly reduced the use of the

and greatly improved the understanding of the HTML markup.

One of the interesting things that I like about HTML is that it is simple, it’s as simple as coding comes,in the simplest of terms, HTML is saying ‘put this, there’ and CSS is saying ‘and do it this way’. Both HTML and CSS are complimentary partners, one is plain and simple, matter of fact and the other enjoys a little flair, and to coin a phrase, style.

Think of HTML as Lego, colourless lego to be precise. You fit the pieces together and eventually you get something, but CSS comes along and paints each brick a different colour and before you know it; you’ve got yourself something… anyway, I’m getting away from my original point.

Semantics.

HTML5 has been described by many as “forgiving” and from what I’ve been learning, yes it is forgiving in it’s nature. I will continue to wrap my src and href in “…” but the truth of HTML5 is that you don’t actually have to. The browser will understand what you’re going for and will sort it out. Think of it as a Teams call where a colleague is cutting out, but you still understand the point he’s making. It’s not clean, it’s not the best, but you get it.

HTML likes to keep things simple and for HTML to be both clean and efficient, it also needs to be kept organised, and this why why I am so happy that we are able to structure a page, without relying on the , now don’t get me wrong, I think the is a great tag, it breaks things up, it gives the markup structure, but what it does not give me markup is context.

So whereas we would this and that - now, you can structure your mark up, as an author would structure a story, by giving it a beginning middle and end. We’re taking for you main titles , , , , and there is a TON more! it’s an actual candy store of tags. What this enables you to do is actually think about your page as a piece of organised content, – sidebar, navigation, heading, subheading, article, footer.

When I am designing a page, or preparing the structure - before I even place a finger on the keyboard, (and I’m not going to pretend I’m not new to this), I sketch the page in simple blocks and what happens is that I see a structure that these HTML5 tags help to define – and in reverse, I find that I read a piece of code and I can visualise that structure – I don’t even have try because it’s right there – header, main, article, footer.

So to the almighty , thank you for everything, but like all things, we must evolve. So don't be afraid to explore the semantics in HTML5. Honestly, they make understanding the markup much easier.

Actually that was quite cheesy, but you get my point.

Keep safe.

I just learned HTML twice.

Anthony Maxwell — Wed, 03 Mar 2021 21:40:47 +0000

Okay so that’s a bit dramatic to say the least, bit I did. So I am studying to become a full stack web developer, well I am now, but the truth I don’t really know where this will lead me. Remember when you were younger and people would ask yourself “what do you want to be when you grow up?” well I wanted to be a film director, or a lawyer. And then I just wanted a job, eventually I found myself working in Bid Management and I’ve been doing this job for over 10 years. I’d say I’m pretty good at it, but it wasn’t the goal i’d set myself, but things worked out. I’m professionally successful and I work with an outstanding team. I have little reason to complain.

So with coding, what is the end goal? Machine Learning with Python? Building websites? I have a fascination with Machine Learning.. The truth is I don’t know, but what I do know, what I clearly understand, is that I want to be good at it.

I have known a few people who have recommended The Odin Project, so that’s where I started. I installed Linux and got to work, HTML Basics and CSS basics doing activities at freeCodeCamp. They seemed to go fine, but spending a few mins on each task and moving on, I did get the feeling that I was solving a puzzle, but not learning how the puzzle is solved. I can tell you what Pythagoras theorem is, but I can’t tell you why it works. This is what happened at FCC, when I got to the final five tasks, I found myself flicking through text books and revisiting previous activities, and then I was looking at YouTube videos. I discovered the tutorials of Brad Traversy – I assume that’s his name, because the channel is Traversy Media – check it out, the crash courses are really good for beginners.

So I decided to sign up to Udemy and picked up his basics course and err a bunch of others, because I know my plan is to get HTML & CSS down and then move onto JavaScript… and I’m a sucker for a discount. So I completed the HTML basics stuff today, I actually wrote a ton of notes and did some practising along the way using VS Code. It was painfully easy, but between the note taking, practice and the quality of the teaching. And it’s down. I’ll do the CSS stuff tomorrow; still got about 19 hours of content to go through, and all this before I go back to the FCC ‘tests’ to get the Responsive Web Design certificate and then back to Odin. Not sure I’m doing this right, but I guess repetition is the best way for me to learn? I dunno.

I think all people that learn should be comfortable with the way they do learn, and we are all different types of learners. As this gets more complicated, I wonder, will I be able to retrain my brain to think in a manner that will make me proficient in my programming choices? I’d like to think so.. and if I don’t get it the first time, I’ll just do it again and again and again until I understand and can apply foundational understanding and then as I develop more advanced concepts to whatever it is I’m working on.

DEV Community: Anthony Maxwell

Finding your own style

To or not to ? That is the question...

I just learned HTML twice.

To
or not to
? That is the question...