A long life.
We’re working on two big projects right now, Orbit (can’t say much yet about this) and The Daily Jolt. For both of these we’re doing major work to sites and systems that many people will use for a long time. And we feel the weight of this because each decision we make is something we’ll be living with for quite a while.
More importantly, the decisions we make are things our users will live with.
How do you develop for something that’s going to have a long life? Keeping things simple, modular, and fast seems to be a good starting point. But we’d love to hear from the rest of the world, especially if you’ve been working on any AJAXy ‘Web 2.0′ goodness.
(I do realize that we can change things at any time - after all, this is the Web, not print - but we want to force the fewest number of changes on our users later.
July 6th, 2006 at 9:39 pm
It would be wise to get as much honest feedback from outside sources (beta-ish types) so we stay focused and can justify our decisions.
July 8th, 2006 at 8:53 am
Agreed. I think you’d gain more from talking about your new project. That’s just me, though.
Also, I’d be glad to beta test the new product and provide feedback, confidentially (or publicly), whichever you prefer.
July 10th, 2006 at 1:18 pm
Thanks, Pete.
We do plan to talk about the project a lot more as we get closer to launching. We are also going to find some beta testers to really beat this thing up before we launch. You’re the first name on that list!