Ahhh, overlaps with XOXO! Too bad...

Some good books if you're just starting out:

• Thinking with Type — Ellen Lupton
• Detail in Typography — Jost Hochuli
• The Elements of Color — Johannes Itten
• Interaction of Color — Josef Albers (there's also an iPad app that works offline)
• Web Form Design — Luke Wroblewski
• Universal Principles of Design —William Lidwell

If I personally had 3 weeks set aside just to learn, I'd finally get around to reading:

• The Humane Interface — Jef Raskin
• The Animator's Survival Kit — Richard Williams
• Ways of Seeing — John Berger

Awesome to see some updates. Navbar looks awesome.

I check Designer News every day. I've never checked other "public voting" sites (Digg, Reddit, etc.) with the same frequency. I think it's largely because, as a reader, DN doesn't read like a popularity contest (even though it is). You can skim through the first page of links without noticing the upvote count.

This redesign has such an obvious Upvote button that it kind of ruins that vibe. I'll probably still read every day, but I'm definitely going to feel gross about it now.

Awesome to see some updates.

I check Designer News every day. I've never checked other "public voting" sites (Digg, Reddit, etc.) with the same frequency. I think it's largely because, as a reader, DN doesn't read like a popularity contest (even though it is). You can skim through the first page of links without noticing the upvote count.

This redesign has such an obvious Upvote button that it kind of ruins that vibe. I'll probably still read every day, but I'm definitely going to feel gross about it now.

You could switch away from Basecamp to a more lightweight system, but you would still be dealing with the same volume of requests. This seems like a problem of culture and tooling.

A few things to consider:

• Do you need to log issues in Basecamp yourself, or could you instead empower your colleagues to log issues when they see them?

• Instead of making others dependent on your team's availability, how might you allow colleagues to make design changes themselves and submit them for review?

An example: for internationalization purposes, we centralize all of our UI copywriting in a single file. This lets anyone on the team to submit a copy change for approval if they have an idea for better phrasing.

• When you receive a request, ask your colleague what problem the request is supposed to solve. It might be related to something you're already working on, and you can consolidate projects accordingly.

• When a colleague makes a design request, is it rooted in user data or personal preferences? If it's the latter, you can try to validate the root problem through user research, and only work on it if you uncover a demonstrable need.

Haven't used this, but I switched to Marked from similar CLI tools because the text rendering was just so much better.

Markdown is a great format for writing, but large, bureaucratic organizations (governments / enterprises) don't know how to read it.

It's a solution to a translation problem: you're converting from your preferred writing tool to their preferred medium.

Hey Edwin,

I live in Oakland and would be down for meeting up.

Email me: josh@rubenoff.com

The original title seems like a misnomer. From the job description, it sounds like their primary job responsibilities are design-centric, rather than dev-centric.

If you just want to rename the existing roles...

UX Analyst: Sounds like UX Researcher or Design Researcher

UX Engineer: Product Designer

Interactive Designer: Visual Designer / Brand Designer

In terms of what to hire for, I agree with Ryan and Adam... I've had the most success simply hiring for a "Designer", and evaluating their skill set from there.