Ive Got Some Feedback

Jobs’s taste for merciless criticism was notorious; Ive recalled that, years ago, after seeing colleagues crushed, he protested. Jobs replied, “Why would you be vague?,” arguing that ambiguity was a form of selfishness: “You don’t care about how they feel! You’re being vain, you want them to like you.” Ive was furious, but came to agree. “It’s really demeaning to think that, in this deep desire to be liked, you’ve compromised giving clear, unambiguous feedback,” he said. He lamented that there were “so many anecdotes” about Jobs’s acerbity: “His intention, and motivation, wasn’t to be hurtful.”

This incredibly in-depth piece on Jonny Ive, the Senior Vice President of Design at Apple, reminds me a lot of the lessons and insights learned from Mike Monterio’s book Design is a Job.

To do good design work is to relish in good feedback. Don’t think designers or developers want you to say, “I like it!” when you really don’t. We all need to be honest – brutally and politely so – with one another to make better design.

Björk on Working With Men

After being the only girl in bands for 10 years, I learned—the hard way—that if I was going to get my ideas through, I was going to have to pretend that they—men—had the ideas. I became really good at this and I don’t even notice it myself. I don’t really have an ego. I’m not that bothered. I just want the whole thing to be good. And I’m not saying one bad thing about the guys who were with me in the bands, because they’re all amazing and creative, and they’re doing incredible things now. But I come from a generation where that was the only way to get things done. So I have to play stupid and just do everything with five times the amount of energy, and then it will come through.

From this Pitchfork interview with Björk (via Waxy.org)

David Foster Wallace on the Humdrum of Life

learning how to think really means learning how to exercise some control over how and what you think. It means being conscious and aware enough to choose what you pay attention to and to choose how you construct meaning from experience. Because if you cannot exercise this kind of choice in adult life, you will be totally hosed. Think of the old cliché about “the mind being an excellent servant but a terrible master

This commencement speech from David Foster Wallace1 is really interesting.  The whole thing is worth a read, with many sections that made me let out an audible, “Ooof”. Especially the part about the boring routine of adult life.

As someone who’s many years from graduation, the whole thing really does ring true and is solid advice for anyone, not just graduates. Although, I assume a younger person would gain more value than those who are older.

I still struggle with the choice of where to put my mind.

(via kottke.org)

Shubhro Saha on why software engineers should write

Software engineers should write because our craft is increasingly collaborative. Open source projects invite worldwide participation, while industry products often require an army of engineers. (Google Maps has 1100 full-time employees!) Good writing– whether it be in a GitHub comment, code review, or technical documentation– facilitates clear, concise communication for projects like these to move forward.

I’m going to take Shubhro’s essay on why software engineers (i.e. programmers, developers) should write one step further. Everyone should write about their craft. Database administrators, project managers, accountants, plumbers, Wal-Mart door greeter, you name it.

Writing is thinking. Writing helps you to understand your work better. To take a step back from the hustle and bustle and reflect on what you’re doing. You ask different questions about your craft when you take a moment to think and put it down in words for others to read.