It’s pretty hard to get started talking about something like web design. It can be difficult to quantify how much you know. It’s one of those exponential kind of nightmares activities where the landscape is constantly shifting around you. When you’re just starting out, every move you make can leave you feeling like you don’t know as much as you thought you did. Since you don’t feel like an expert on the topic you feel like you can’t contribute to the discussion. But you can’t just wait until you’re all caught up before you start talking about it.

Terrible analogy alert

Being a web designer is a bit like being left in charge of a really slow time machine . It’s pretty common to find articles about the fun balancing act of accommodating the past (eg. Legacy Browsers), the present (Framework X) and the future (Framework Z, which is due to drop in about six months, just fyi).

There’s an overwhelming amount to see and do on your journey and you can’t be an expert on every topic. Whichever choice you make, you’ll probably have a lot of questions and do a lot of searching for the right answers. And when you finally get to your destination, time will have caught up and surpassed you anyway.

Trends trend and best practices pivot, and frameworks and libraries will come and go. New acronyms will get thrown around, pique your interest and stump you. Some of them might make it into your workflow. The tools we thought we couldn’t live without will regularly be swapped for new ones. Someone’s always got a faster, fresher, prettier way of getting the same thing done.

To add to all that confusion, most of the time our work is all there for our peers to view, comment on, and assist with. The open source community is inspiring and amazing, but as a noobie, it means we want our work to be neat and tidy and maintained and we want it to be helpful. We go out of our way have a responsibility to make our websites more accessible, more user-friendly, faster, and more beautiful with every project. And with budgets the way they are these days, we’re often striving for the improbable.

We get up extra early and stay up way past our bedtime and do extracurriculars to keep our passion alive.

Anyhow, when you find yourself googling how to do the nifty new things you would otherwise quite be able to remember off the top of your head, you should probably start a blog, open up your CodePen, dive in and start figuring things out. The best way to learn something new is to pull it apart and then talk about it. At the very least if you find yourself looking something up later on, you might have created yourself a shortcut to the information when you’re after in a pinch.

That’s all this blog aims to be really. I’m just a noobie trying to figure things out, and maybe contribute something helpful to others who also need a bit of help.

Footnotes

Earlier this year I spent a good chunk of time compiling other people’s work into a package for front end development called Gulp Caddy. I use it almost every day in my work and I can’t thank the open source community enough for figuring it out.

More recently, I’ve been documenting cool features to use on the terminal with iTerm2 in The Beginner’s Guide to iTerm 2. Which might help you learn a few tricks that lead to fewer clicks on your journey to get through the absolutely overwhelming amount of tasks you need to get done. I also discovered the secret to making the Terminal pretty. :)

Thanks for reading!