Many times I’ve seen people take the attitude that non-UI developers can do UI development—usually when project time constraints come into play, comments like: “some of the back-end developers could jump on this”, “some of the designers know a bit of HTML and CSS, can they help you out?”, etc. I’ve always felt frustrated by this and at times I’ve felt this can come across as if UI development or writing CSS isn’t regarded or respected as a real skill, even though there is a team of UI developers. In my experience this just leads to annoying conversations about why it isn’t actually faster to have anyone dive in and write CSS—the time spent having to refactor poorly written CSS i.e. paying back technical debt, applying updates as details are missed, and potentially fixing UI breakages, just isn’t worth it. Just as I don’t expect to write back-end production quality code, the same vein applies to CSS.
Reflections of a User Interface Developer
Chris Pearce
412

This entire paragraph is solid gold. I’m currently working on a project where I’m outnumbered 9-to-1 by back-end developers. They’re pumping out new functionality faster than I can possibly scramble to keep up.

When they’re done with their sprint work they usually ask if they can help. Which is good! I often have to say no simply because they don’t even know what the box model is. I have to say no because they don’t know the meaning of “semantic HTML” or zone-out when I talk about accessibility. I have to say no because the end result will be so bad that I have to go back and rework it anyway.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.