All posts by Brett Wysocki

One of my favorite bands is Motion City Soundtrack, and I’ve just been listening to “Can’t Finish What You Started” off their album, Even If It Kills Me.  I love so much of what they have to say in this song, and it gets me to think of how I’ve been approaching the last couple years, not finishing anything I’ve started.

It’s about just getting it out there.  No project is truly complete, or as complete as you maybe like it to be, but that’s not justification for giving up on it.

“Systematically revealing to me, that I need a new approach.”  – Motion City Soundtrack

So, here starts the new approach.  Finding the time to put a pen to paper, or in this case, finger to keyboard, and write out even some abstract thoughts in case something comes of it.

While there is no end in sight, that doesn’t give me any justification to give up on it.  Every journey begins with a single step, or so they say.

I said when I started this that I don’t know what I want this to be.  I’ve been working on a couple pieces and I think I’ve started to figure out that the best topics aren’t the ones that are reactionary.  They’re proactive.

Credit where none’s due.

I haven’t really written since college.  I’d like to write more, and this is what I thought this was going to start out being.  But somewhere between scrapping 3 separate posts did I realize that a lot of what I wanted to talk about was grievances I’ve had working in an area of the country that still waiting to get 4G from more than one provider.

That’s no one’s fault, except maybe my own, but I’m looking to place it elsewhere, anyway.  And that’s not right.

Teach a man to fish…

The internet is such an engrossing place that sometimes it’s easy to forget that not everyone lives on it like I do.  I remember someone saying at the last WordCamp I went to in Minnepolis last April,

“The way we use the web today, is the way the everyone else will use it in a year.”

A lot of what I get frustrated at can come back to that statement.  People having issues in ancient browsers, testing default browsers in older versions of Android or iOS, someone not understanding basic development structure.

It’s my job to help nudge those people toward the future, or, I guess, to how I’m using the web today.  This just leads to me needing to pay more attention to what has changed for me over the last year, and what lead me to here.

So that’s where I’m at. Wanting to help shepherd the masses toward the future of the web, all while not going absolutely insane.


So that’s my goal, I guess.  It might change, but I want to make sure that we can move forward together.

It’s too much to say that I’d wish everyone would get on my level, but…I kinda do.

Being a designer can start you off on bad footing with most coders.

Being a coder usually makes you a enemy for designers.

One provides endless imagination and creativity while the other the structure and knowledge to display information to millions. Design and code don’t have to always be at odds, but most of the time, that’s the case.

Defining Roles

Design and code for the experience and content the website provides, not to the pixel perfection of the design, nor to the ease of the functionality of it.

It’s no wonder why jobs have been created recently for User Experience and User Interaction. Their jobs are to understand both coders and designers. On top of that impossible job, they’re also expected to understand users.

Usually they’re involved in the process early on with wireframes, before the design starts.  However, not everyone has the luxury, and that section of process can be taken for granted.

Flexibility Without the Yoga

For coders, it’s important to remember that not everything is going to be thought of all the time.  Yes, this is irritating.  Yes, you can’t believe it got this far without it being thought of.  That’s why you’re here.

Frameworks are so popular because there’s some solace in the idea of creative structure from the usual chaos. Keep with this tradition, and try to keep things consistent, even if it means possibly taking liberties that could be changed later.

That last part may be the hardest for coders, because usually there’s two functions for code. It works or its broken. That’s not the way design is done. There needs to be more patience with design, the hardest part being that the final answer sure could be 2+2=4, but it is only actually right when it’s written in 24pt Open Sans, italicized.

It’s Not You.  It’s UX/UI.

As a designer, you have had your head buried in a design for hours/days/weeks getting it to the point it’s at now.  You might be on a bit of a high since the client approved that design.  And why wouldn’t you be?  It’s awesome creative!  And then, some non-creative is about to come in and pick everything apart.   Why?  What did you do to them?

Well, to be fair, it could be that they’re running low on caffeine, patience, or both.  Or, the more likely scenario, is that they’re not seeing your magnificent design for its whole beauty, but instead are already breaking it up into divs, spans, and unordered lists in their head.  How will the user know that they are able to interact with this element?  How will they know it’s disabled?  What does the design look like on smaller screens? The list grows for every browser, screen size, and interactive element.

Plan for Breaks

I’d recommend taking a step back from your design often, ask yourself what elements have been placed since your last design break, what purpose they serve, and how you imagine the user will interact with them.  Keep an open notepad, and jot down your notes.  It may add a little more time to design, but I promise you, it’s worth it.

Also, keep your Photoshop files in order for everyone’s sanity…


It is very difficult to walk the fine line of either being both a coder and a designer or being a coder who can live with (and not hate) your designer (and vice versa). However, it is possible to create a symbiotic relationship, where you each do a little work for the other to keep things flowing.

Be a logical designer. Be a creative coder.

I don’t know what this is going to be.

That’s not what I’d want to read if I were you. It’d be nice to even have a clear statement, like “a blog about blah, blah, and blah.” But I don’t know what this will evolve (or devolve) into. But just because I’m not willing to give this a clear framework, doesn’t mean I’m not looking forward to what it’ll bring.

I may not know what it will be, but I know what I want it to be.