Ever have one of those days where you realize just how horribly behind you’ve become in keeping specific parts of your portfolio up to date?
Yeah, that’s today.
So here’s a list of the last… um… five article I’ve written for The Interconnected:
Of those, the top one was probably the most important, because it discusses ongoing differences between the way that most conferences handle codes of conduct and how we probably should be handling them.
But if you’re looking for general ranting about UX, the lamp post is pretty fun.
Also, a reminder: we’re always looking for authors so if you have something to say and want to post it to Medium and our little website, we’ll gladly take your submission.
In other news, I just got back from An Event Apart DC and had a fantastic time, so there will be a notes dump sometime soon. As in, I’m starting to write it now.
And October 8-10 I’ll be speaking at edUi Conference in Charlottesville, VA. Come on out and check it out!
My job role is UX Designer, my career is as an Information Architect, and I love Design.
But really, somewhere deep inside, there’s still a fiction writer honing her craft in here.
In this week’s post for The Interconnected, I wrote about looking at exactly how many damned files one person can generate for one unpublished (and unfinished!) novel… and exactly what a mess I’ve made.
There’s a tiny part of me that hopes I never do hit it big, because I don’t want to hoist this mess off on some poor unsuspecting archivist in the future.
One of the least-talked-about responsibilities of UX Designers (in part because not all of us are required to do it, or do it well) is testing pages in the Quality Assurance (QA) stage before they go to production.
I’m working with three different teams to test our pages for three different projects, so I’m pretty knee-deep in testing right now. The result? Page Integrity Testing, three tips for helping developers help me produce quality products. (Or three tips for helping me help developers produce quality products. We’re all in this together.)
I’m doing a lot of writing design guidelines at work right now — essentially codifying in words the things we’re already doing. Paving the cowpaths if you will.
My June 28 post on The Interconnected is about where to put design guidelines when you write them, what application to write them in, what to put in them, and why nobody’s going to read them but you.
Read Back to Basics: Writing Design Guidelines on The Interconnected
The truth about sucking at things is that you do it at the beginning, and suck less until you master a thing.
The damned annoying truth about sucking at things is that if they don’t have defined limits to what “mastery” looks like, you’re always going to be able to see progress. And that means, well, you’re going to suck.
Read the damned annoying truth about sucking at things on The Pastry Box.