I actually put together a blog post. Who’d have thunk it?
Good article about the need to actually ship - “Great artists ship” - that’s summed up in one sentence:
But if you’re not embarrassed when you ship your first version you waited too long.
Getting your product out the door, in front of users, is still the best way to find out what they actually want and need, instead of studies and surveys and interviews. Get people to use it, get them to complain about it, and that single act will provide you with all the information you need to prioritize the “What’s Next” list of features for 1.1, 2.0, 3.0 and beyond.
Ship it. Get it out the door.
I ♥ Rands.
(And, as an aside while looking up the heart character, I also love that Apple has an entire section in their Character Viewer titled “Divination Symbols”. What I like even more is that they’re all the I-Ching.)
Good article, but like many things on InfoQ, light on actual, actionable things to *do*.
The more I get to be an actual architect, instead of an extra pair of hands or a firefighter, the more it’s blatantly obvious that being an architect of course deals with technology, but is mostly understanding what an organization wants to do, how to use technology to get there, and then having the leadership – both the political savvy and the force of will – to get from Here to There.
A whole lot of vapor surrounding a pretty good idea, in general: Mechanical Turk meets test scenarios, perhaps? I can imagine how it would work, but I don’t see how it would scale, when there are things like CloudTest and JMeter+EC2 to bring millions of virtual users to bear in a load test.
Been a while, I know. But, it’s Rands that got me to post this little bit here, and for that I thank him.
Trust is something I feel really strongly about, especially after watching it get eroded quite a bit around here. How do you rebuild this trust, when it’s so severely damaged?