2 years in

I’m been successfully employed now for 2 years. Probably doesn’t sound particularly impressive, but after 4 years of self-employment, I was pretty dead-set on never working for anyone else ever again. Today seems like a good time to read over the first post on this blog, which was written shortly after I started working here. (The best line is definitely “sitting around waiting for the email to ring”).



Math is HARD

I started reading a post on CSS Tricks about job postings, and I noticed something that really made me shudder:



Let’s Get Technical

The first time I create an issue on someone’s project on Github, I got yelled at. So I haven’t contributed anything to anyone else’s open source project until last week. Yes my solution to a long standing bug got the nod of approval, and I have to say it felt redeeming. I almost didn’t say anything, I was nervous that I’d be told my solution was dumb, that I didn’t know anything, that I should just go away.



Scroll Hijacking: I knew there was a reason I don’t do this

I hate scroll hijacking. You know, those sites where they steal your browser’s normal behavior and do weird things to it, like auto scroll you to sections or run animations instead of actually scrolling the site.



From the Archives

I am going through some old hard drives and found some golden oldies, including an Intro to HTML document I wrote. It’s really just too good not to share. So behold, How to Learn HTML, circa 2000, excerpts for your enjoyment.



Accessibility: Who’s Responsible?

We recorded a show about web accessibility last night, and a topic that came up was Responsibility. I know how to implement accessible features, but I also know how much extra time ($) it takes to do a good job at it. Regardless of the budget, I do the basics. But beyond that?



IE11, IE10 Flexbox overflow bug

Just putting this here for posterity.



Boilerplate

When work at an agency, you set up new sites all the time. If you work at an agency that does fully custom sites, coming up with a sensible and globally-useful boilerplate is challenging. You don’t want it to be blank and have to totally re-create the wheel every time, but you also don’t want to be spending a bunch of time stripping out unused styles (or worse, leaving them in). Boilerplate is not a set-it-and-forget-it type of thing. I tweak it nearly every time I start a project (tweak being the important word there, if I made major changes every time it wouldn’t exactly be “boilerplate” would it?).



Unpublished Drafts

Unpublished, probably will forever stay that way: Boilerplate, The Road to Hell is Lined with Empty Spans, Then when your internet hardly works, 5 tips to become wildly successful in all the things, when work becomes hard



Talking in Circles

No matter how many times you try to describe a complicated interface, there will be some people who just don’t get it. Not that they’re dumb, but the way you describe things and the way they visualize things might just not jive. I spent maybe an hour in a meeting yesterday talking in circles. What seemed so clear to me was quite obviously not clear to others, although they didn’t say so; no one likes to admit they don’t understand. Except me–for some reason I’ll freely admit I have no idea what’s going on (yesterday: “Does that make sense?” “…….um……nope, not at all”).