Development – Page 4 – Chris Koerner

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.

Silence in Open Source Projects

If you contribute to open source projects, or are the sole creator of an open source project, you need to keep talking about that status of what you’re working on. Never stop.

Silence will deter people. Even if your code is super stable. Even if all features have been added. If I see that the last update on your blog/twitter/etc. was a year ago, I’ll assume the project is not actively maintained. That you’ve moved on. That OS updates and/or browser updates will render upon me issues and bugs that will never be addressed. That I should find something else to use.

In a world where OS updates are yearly and mobile apps are updated without interaction, it’s maddening to see open source projects – good, solid, useful projects – go into a sort of hermit state.

Quicksilver went through a period where it wasn’t actively being developed. Now that it’s seen some love, updates are frequent and communication is constant. I know that it’s a living project and something that is being worked on. I can rely on it and treat it as something that is solid and tactile – not infirm or fragile. A feeling I often felt during the ‘dark times’ where it lacked leadership.

Most recently I’ve seen this with the Sequel Pro application. An application I love and use frequently¹. Sequel Pro hasn’t updated in over a year ². Devs say it’s still active, but aren’t communicating that.

I’m not advocating for point release updates just for the sake of appearance. I’m advocating for putting effort into your communication.

If you’re part of an open source project that is actively being developed – even by just a few contributors – make sure it is kept alive. Make sure new users, and existing users returning to see what’s new, know the status of things. Clearly and plainly. If the project is still active, communicate that. If the project is done and mothballed – let us know that as well.

The result is more people using your thing. More people making it better. That’s worth your time.

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.

Matt Mullenweg on the “State of the Word 2014”

The mission of WordPress is to democratize publishing, which means access for everyone regardless of language, geography, gender, wealth, ability, religion, creed, or anything else people might be born with. To do that we need our community to be inclusive and welcoming. There is beauty in our differences, and they’re as important as the principles that bring us together, like the GPL.

There are thousands of reasons why a person might pick one technology over another. Cost, support, growth, platform, user interface, etc.

The biggest one to me, and one that I’m happy to say WordPress embodies well, is the culture and community around such technology. After watching Matt Mullenweg give his State of the Word presentation at our WordCamp San Francisco Viewing Party, I’m glad to have aligned myself with such an awesome community. I want to work to use technology like WordPress to make other’s lives more rich. To improve my own knowledge of technology. To better myself as a person and be more including and welcoming.

Here’s to the future growth of WordPress, and all those who make it what it is. Grand.

A Great Interview with Mike Monteiro – “Design Is Not An Investment”

“Yes, investments are great. They’re also not necessary. When I think of investments I think of stocks, artwork, original Star Wars figures mint in box. Stuff that’s nice to have, and that you hope increases in value someday. Design is core. It’s not a nice-to-have. It’s plumbing. It’s foundation. You don’t invest in design. You can’t exist without it. A website without design isn’t a house without art, it’s a house without a bathroom.”

Like any professional I have numerous books on topics core to my work. Technical manuals for systems, guides for programming languages, historical text from founders in the discipline, and numerous outdated (FrontPage 97!) reference materials from years gone by.

Yet, there is only one book that I would give to anyone entering the field. Mike Monteiro’s Design is a Job. I’ve been a ‘professional’ for over a decade. I just read his book a few years ago and it has changed how I approach everything – for the better.

And now Mike has a second book out, from the other side of the table as it were, called “You’re My Favorite Client“. This interview with him is a great introduction to the relationships between designer and client.

Both of Mike’s books are essential for anyone working to create something for someone else. Web design, photography, app developers – all will gain more from these books than any technical guide or “Photoshop for Dummies” could ever muster.