Hello friends.

I’m Boris, I’ve been coding for three months now, and I’ve never talked about it or celebrated in any way- so I thought that I’d commemorate with a blog post (but really an unordered list) containing reminders to myself (and perhaps you if you need them), unexpected things that came up, and odd thoughts and feelings. Maybe you read that last sentence and felt that it was too vague and that you still have no idea what this blog will be about. Perhaps you’d like a blog post on a single subject, with new insights by someone remarkable and renowned that might change the way you see the world of web development. Maybe you aren’t a big fan of a prolonged exposition and or improvised delays. Well fine, that’s a perfectly valid and thank you for stopping by and making it this far. Here is a <ul> of unorganized thoughts.

  • Say you have multiple fonts that you need to use on Google Fonts. And you have some icons you need to use from Font Awesome. You go ahead in your innocence as I did, copying the embed link into your <head>. Congratulations. You close the Google Fonts tab in your browser. Half an hour of coding passes. Maybe productive, maybe you are pulling your hair out. This is a perfectly normal behavior. You regain perspective and get to the <p> you need to style in your CSS. You realize your error- the perspectives that built you up just moments earlier disappear from your memory and you fall into an existential abyss. You open a tab and go back to the Google Fonts page that you haven’t realized is “href=fonts.google.com” … you’ve just been googling “google fonts” every time.

Okay, maybe this one is more for myself. But I think it’s a good idea to copy Google’s suggested CSS rules to the top of your CSS and comment it out, and you can even delete it when you’re done. Same for Font Awesome and other materials you’ll use. Or forget this because your brain can only handle so much at once and you have other, more pressing issues. You know what is best!

  • I wonder if anyone has written a website that is completely non-visual. As in, content would not be read but there would be a tool that reads the content like a screen reader would, regardless of if you were sighted or not. If not, I think it might be a good idea to do it. I am a sighted dev, and I’ve heard that the brain fills a lot of the gaps between what we assume might be the experience of a non-sighted user and how that experience actually is. Maybe this would be a good simulation? The greatest test would still be asking the opinion of a non-sighted user themselves, I’d think
  • Tried going mobile-first while putting together my first project in the Web Dev Bootcamp at Juno College, and I thought the process was a lot easier than a desktop first! Highly recommend!

Well, that’s all I have! Thank you for making it this far,