Know where to look

I’m listening to Jen Simmons and Rachel Andrew talking about the pace of the web industry these days. About how it’s not possible to know every new tool, process and technique that pops up day in and day out in this field. And that this is okay. I agree.

I feel there is this insane pressure now, and has been for a couple of years—that as a web developer—it’s my duty to stay on top of every new framework that’s being thrown out the door. I’m not interested in that. And I can’t do that. It’s way too much information. I need to prioritize, and right now my priorities are still good ol’ HTML and CSS.

Sure, I still write some basic JavaScript now and then but the important part is that when I need to get my head into a new JS-framework, because a certain project demands that, then I know where I can find valid information. That’s what I have my Twitter feed for. It keeps me updated–on a surface level–about what’s happening in the industry. But I don’t dig in deep until I have to.

They talk about something that clings very true to me—that it’s not about knowing, but rather know where to look.