CSS is hard because we don’t have total control over the output. We have to tell the browser our intended output, and then depending on a ton of variables, it gives the user the best it can.
Think of it, we don’t know what device our users are on! Users can have different screen sizes, resolutions, and orientations. Different color gamuts and input devices, different browsers and browser settings, different operating systems, and more!
With all that at play, we can’t have total control over the output, the user does!
CSS doesn’t “fail”. If the browser doesn’t understand a line of code, it just skips it and keeps on going with the rest of it. This is similar to if it runs into overflowing content, it’ll let it overflow and keep on going.
As Robin Rendle put it in a response to a tweet of mine awhile back, it’s one reason a lot of people coming from a computer science background don’t like CSS. They have to face the “webniness”, or the changing nature and the unknown variables of the web when writing CSS.
How can we possibly deal with all those unknowns and variables? Part of it is anticipating the variables.
I've talked in the past about how important it is to sometimes make something for the fun of it, without the intention of learning something from it (though that can be a nice side effect) or for work.
When we make something for the fun of it, it can help remind us why we enjoyed this in the first place, and freshen things up a little bit.
It helps break up the grind.
As a content creator focusing on educational content, it can turn into a grind as well, and I have to do different things to break things up a bit.
That's one reason I enjoy live streams.
Lives help bring a different dimension to things, letting me interact with people and sometimes go in different directions than I'd intended. One of those live streams was a challenge brought up in the community: to try and code while blindfolded.
It was a blast to do live, and the chat was really into it, so I decided to edit it up and put it onto YouTube.
When editing it, I realized it wasn't the type of content most people subscribe to me for, but I thought it might be a fun way to break up the monotony on there as well.
It seems that people have enjoyed it for the most part, but some people feel that perhaps I jumped the shark with that one*. And yeah, they're probably right 😂.
Change from HEX to RGB to HSL in seconds with VS Code
There are a ton of websites that can help you pick colours for your web design projects out there, but most of the time, HEX is the only colour mode you can copy and paste into your editor without having to make any changes to get it working.
Ideally, we are working with HSL, as it's the easiest to make changes to. Here are the variations I have of my primary colour here on this site. The 400 is the base, and then I just modified the l value (lightness) for each variation. Easy peasy!
When I decided to get into content creation full-time, one thing I wanted to start doing more of was live streaming. After experimenting with both Twitch and YouTube, I've decided to stick with Twitch.
I did a couple of streams on YouTube that were a ton of fun, and which had a lot of people joining, with between 250-350 concurrent viewers for each stream.
After that, I decided to give Twitch a try. I wanted to do this for a number of reasons:
See what all the fuss was about
I like experimenting and playing with new things
Compare the experience between the two
Diversity myself a little bit more
To give it a proper try and see how I could grow on Twitch, I decided to start with two streams a week for a month, and re-evaluate at the end of the month.
That month is over now (or well, close enough), so in this post, I'll be giving you my impressions of Twitch, as well as how it compares to YouTube.
I recently came across a post by Peter-Paul Koch on his blog called CSS4 is here!. I see people using CSS4 as a way to get clicks from time to time and it really irks me, so I tend to ignore them, but for some reason I decided to click through and see what he was talking about.
As I read, I realized that he was making an excellent point, CSS needs to be marketed a little better.
I remember when HTML5 and CSS3 became things. They had their own logos and it was a big thing. It was pretty exciting and I think did a lot of good overall.
So I see the appeal of trying to do the same with CSS4 again. As he says:
I think that announcing a new CSS version will bring desperately-needed attention to CSS, and will help the people evangelising CSS in the field make an impression on web developers who are otherwise not very interested in it.
Before he gets into the nitty gritty though, there was a line that really stood out to me:
But the code of the web is not all the code of classical computer science, and should not be judged on the same terms. HTML is the code of writers, and CSS the code of graphic designers. Writers and designers are best positioned to write those kinds of code.
You're worrying about the wrong thing if you're trying to learn it all
There are a million and one things that we need to learn in order to be a front-end developer, and it seems like every 30 seconds there is another new thing that we need to add to our arsenal.
Learning new things can be fun, but when it seems like the list of new things we need to learn just keeps on growing, it can be overwhelming.
And there is another big issue. While we’re off learning all this new stuff, how the hell can we remember all the things we’ve already learned?
I often get asked, either through a DM or email from a follower, or sometimes as a YouTube comment, asking the best strategy to memorize everything.
The truth is, I don’t memorize anything. I remember things because I use them all the time, and because I get to focus primarily on CSS. The more I use them, the better I get with them and the more fun I have with them. But I don’t remember everything.