1,145 karma · joined February 25, 2007
http://news.ycombinator.com/user?id=jot
http://hackernewsers.com/users/madmotive.html
It might therefore be a good start to read Seth Godin's Tribes as well as Getting Real rather than just Getting Real on it's own.
However, while we felt this might work well if we were simply selling serviced office space, we didn't think it would help create a nice coworking environment. In a coworking space the individuals that come to the space are far more important than anything else. If we made a big deal out of the pricing structure, we might end up with people that are their primarily because they see it as cheap and not because they want somewhere to cowork. We choose to just keep it simple and replicate Citizen Space's approach: http://coworking.pbwiki.com/PricingExamples
ActiveRecord2SDB is also worth checking out - it's built on top of RightAWS: http://activrecord2sdb.rubyforge.org
As for ignoring web standards have you looked at the markup? It's compliant HTML5: http://adactio.com/journal/1524/
They also have a beautiful API so we can fill in any gaps very easily ourselves and they're adding new features every week... and they are probably one of the top users of http://getsatisfaction.com.
I've seen too many great engineers getting turned off working with technology because of the time they spent working in traditional businesses that just don't get it.
However, it is a slight sweetener that this seems to include all credit card processing fees.
Not looking forward to the jet-lag :)
They just need to get themselves into an environment in which they can most effectively do their thing. I'm sure they were in it or close to it when they started their own startups. :)
I think that Seedcamp not seeming to focus on the product, is a symptom of them suffering from too many cooks. These cooks probably start finding roles for themselves and end up pushing startups to put together all the elements required to build a complete restaurant rather than concentrating on perfecting a single dish.
YC being directed by just a few smart, well connected people is probably better suited in it's structure to focusing on a single dish and bringing in other people only when they are really needed.
I particularly hope the predication about SeedCamp comes true. It really does need to become more like YC if it's going to have as big an impact. Alternatively they could start again from scratch and keep it much simpler.
It seems to me that SeedCamp's biggest problem might be that there are so many people involved. Committees of even the brightest people are good at making ok decisions but rarely take the risk of making brilliant decisions.
Particularly happy to see two YC start-ups this week launching products so useable that they're being used on Hacker News... and with British origins too! :D
1) If we need to store large amounts of data at S3 and our app constantly needs to manipulate it, sitting between the user and the data rather than simply linking to it.
2) If we launch an app that has a high dependency on Amazon Simple DB.
In either of these cases we would get a significant performance increase from having always on EC2 instances for the app servers. In the meantime SliceHost continues to serve us well for a fraction of the cost.
... and groups like http://www.wiredsussex.com, http://www.projectbrighton.com and http://www.inuda.net (I'm the founder of that one)
.. oh and the weather today is amazing! : http://www.flickr.com/photos/tags/brighton/clusters/beach-pi...
If what you create proves to be really compelling, you should be able to convert a good portion of your Facebook users over to a stand alone version of your app at a later date.
Obviously this only really works if enough people in your target market fit into the typical Facebook demographic.
---- For us, it's really about scaling horizontally - to that end, Rails and Ruby haven't been stumbling blocks, compared to any other language or framework. The performance boosts associated with a "faster" language would give us a 10-20% improvement, but thanks to architectural changes that Ruby and Rails happily accommodated, Twitter is 10000% faster than it was in January. -----
http://highscalability.com/scaling-twitter-making-twitter-10...