January ends today, which I believe means that the statute of limitations on posts reflecting on the past year ends as well. I felt it would be remiss for me to not at least highlight a few things that I spent my time on last year.
I’m with Ingrid: I see a growing movement of people who value craft and quality over price and immediate availability or convenience. That’s not to say that we all have to work as individuals or build small things, though. I believe it’s a harder challenge to scale good craftsmanship, but companies like Apple show us it’s possible.
It’s partly my personality, but I take a lot of solace in approaching my work with a craft method—as a craftsperson. It’s a perspective that allows me to take a deep breath and take on work with a balance of meticulous detail and function. A good craftsperson pursues quality and aesthetic, but also know when to pay attention to value and how something works.
It seems the ad agency world is still suffering from a forced transition into the digital age. It’s an interesting parallel to the “startup” space of the technology world. On that end of the spectrum, developers get their due respect, but designers often don’t. On the agency side, the development work is the afterthought. Many projects—and sometimes even entire campaigns—are dreamt up and signed off on by clients with very little consideration for the technology involved, or the people who will actually be building them.
The missed opportunity here is significant: with a little more balance, agencies—full of amazing talent—could be producing some of the best technological products of our time. But they’re not. The system simply isn’t set up that way and I don’t think most of them know how to adapt.
Friends and fellow Boulderites Quick Left know their dev stuff, and—apparently—their cupcakes.
Time will tell what this statement really means in practice—and I fully understand the argument (and Twitter’s right to take such a stance against their 3rd-party developers)—but it’s easy to speculate where this goes. It’s sad to see a company—that was popularized in no small part by giving 3rd parties access to their data—begin to change course and restrict those developers and former partners.
(via Daring Fireball)
Developer Elliott Kember and cohorts have been playing around with Instagram’s API since before it was actually an API, starting with a web interface for the iPhone photo app called Insta-great!. At a recent hack night, along with Marc Roberts and Phil Sturgeon, he created Instashade. It pulls photos from the service and then organizes them in a rainbow, of sorts. It’s very pretty. And, if you have a larger monitor, there’s a big version too.Visit Original
Joel’s article, referenced by DHH in the article from the last post is a good expansion on the idea of taking your time to build a business with software as its core product.
Please take a moment and read the entirety of this short piece. Some may think David is being black & white. I don’t think so; there are always exceptions to the rules. But I think what he’s saying is that we’re too often chasing the exceptions. And companies, projects, software, and customers can suffer for it.
Jason is applying this thinking to software, but I think it works for anything digital. How do you know when to stop tinkering in Photoshop? How do decide if you’ve shot too much digital footage? How many people is too many to follow on Twitter before it’s not as useful to you? When the boundaries aren’t physical the problem of curation is different.
I’m a designer who learned to program out of shear frustration. I didn’t have the resources to hire a programmer yet I had ideas that I wanted to execute and was tired of feeling helpless. I let the frustration motivate me, and now I can play both ends—design and development—it’s the best thing I ever did for my career.