“As far as I’m concerned, you can never be too rich, too thin, or have too much screen space. By “screen”, I mean not just large monitors, but multiple large monitors. I’ve been evangelizing multiple monitors since the dark days of Windows Millennium Edition.” – Jeff Atwood.
I love the nerdy ways to get more desktop space mentioned in this article.
“Have you ever encountered a software error message that apologized for – or even admitted a mistake? Software is always quick to tell you what you did wrong, but it never seems to admit the possibility that it did anything wrong. In the real world, a person who always blames everybody else and never accepts responsibility for his own mistakes is quickly ostracized.”
Things go wrong. Nothing we can do about it.
What we do have control over is how we handle the situation. I think rule one of crisis management (even on a really, really small scale) is to acknowledge the issue. Finding the best way to communicate to your users is the first step.
What began as a platform to give live updates (like what you were eating for lunch) has evolved into a tool businesses use for much more productive reasons. Twitter is a great way to let your app’s users know when something has gone wrong. Plus, what better way is there to get your message out to so many people in such a short amount of time? Keep Reading
“40 years ago you could open the hood of your car and see and touch just about every component in there. And you had to, because many of those components required frequent maintenance. To properly own a car required, to some degree, that you understood how a car worked. Today, you open the hood of your car and you see a big sealed block and a basin for the windshield washer fluid. You can buy a new car, drive it for years, and never once open the hood for yourself.
That’s the iPad.”
Solutions, resolutions, working toward restitution. Awesome reminder to keep positivity at the forefront of your workflow. Via 99%.
If you don’t read The 99 percent you should start. They’re pitch-perfect and useful so often. This article however, I think needs some clarification. Quotes like this:
“Sometimes it’s best to launch a product before it’s perfect.”
bother me for two reasons.
The article uses our favorite example company Apple to prove a few points. Like Apple launching the iPhone without Copy/Paste as an example of putting a non-perfect product onto the market. But I think this concentrates on the wrong side of things. Copy/Paste, and a thousand other things were not right on the iPhone, so Apple omitted them.
Courage and taste come from omitting what’s not right. Perfection, like an absolute grid in physics, is a pointless metaphor that only confuses the reality of the situation. The design of applications, or anything for that matter, requires rigid standards, and an unerring willingness to omit any single item that does not meet those standards.
The focus on maximum greatness is a red herring. We believe the real trick is to focus on the minimum acceptable answer that meets very high standards.
And Scott, (who I totally do not know) -sorry to disagree if you should read this. I usually agree wholeheartedly with everything else you say…
Lots of good bits here: http://the99percent.com/tips/6103/the-40-30-30-rule-why-risk-is-worth-it
Like this:
“My coach explained, though, that if I wasn’t falling at least once a day in training, I wasn’t trying hard enough.”
Great idea from Jesse at Hogbay Software. He has a new page on his site that lays out exactly the quickest and best ways to get support, and what to expect when you do. This is especially great:
“If you have an idea for improving my apps please send it. I read all email and forum postings, and they effect what I’m working on, but I’m not likely to respond directly.”
Unlike some in the web app business, we love hearing new ideas for our apps. They’re like a gift in email format. But it is sometimes tough to convey our love, sympathy, empathy, regret, and joy in a new creative way for each idea sent.
