kolosy

success is a great thing, but this constant "we're the only ones that are doing it right" attitude is getting old.

i end up running multiple instances typically, as opposed to a single one over multiple monitors.

see audi circa 1987.

http://en.wikipedia.org/wiki/Audi#Reported_sudden_unintended...

short answer - the brake system has to suffer a mechanical failure. read the part where "brakes always win over engines".

let me clarify - i meant contributing to an OSS project.

it may not be profound, but it is quite refreshing. quite simple really - don't let people interrupt you, and do your f'ing work.

designers and developers are no different than anyone else in terms of focus.

fair enough.

(ot) any particular reason the title of this was changed?

but that's not what's happening - they're not paying people to write reviews, they're (allegedly) collecting money for removing unfavorable reviews. i think that's more damaging.

... then i would use other, less centralized and organized sources, as i did before yelp existed. what's your point?

i'm certainly not saying that yelp is stealing money from me, but trusted (yes, only to a certain extent) information is trusted information. if misleading, there are consequences to the consumer.

hurt financially == going to a restaurant/store/{insert random b&m service provider here} that i shouldn't have gone to, and spend more time/money + get worse service/product out of as a result.

isn't the whole point of a review system to influence people's decisions?

my issue isn't impact on the guys that don't play, it's impact on the consumer from the guys that do. a crappy restaurant that has 5 star reviews because the bad ones were paid off hurts me financially.

you know - these rumors were already flying by then... wonder if they had any impact on the outcome.

i've found locale-specific sites to always be better. unfortunately that does require knowing what they are if you travel.

interesting. well - we had the same problem with ndjango. worked fine with beta, crapped out with rc. that, and the shifty api is getting annoying. their last minute shift away from ocaml naming was pretty annoying.

yeah - that's been my experience too. the few times i've dealt with them, they've been back at me in hours tops. hopefully that'll continue despite them hitting RC

the same thing we do every night, pinky... plotting to take over the world... this time with a shivaplug.

ooh... what bug? and are you doing f# for web or just f#?

"founding general partner" is what the bio page says.

i was tempted to blog about this a while back. i've gone from java (back in the 'ole days), to c#/net only, to the view that platforms don't matter. or rather platform boundaries don't matter. i spent the last few months developing out a .net mvc framework for my dayjob. when it came time for us to build http://friendsell.com, that's what i and the guys knew best, so that's what we built on. but we wanted to use CouchDB as the backend... and so we did.

there are subtle implications to the platform decisions you make, but on the scale of most startups, the extra $40 bucks a month you'll pay for that windows ec2 ami isn't gonna make a difference. what will make a difference is you building on top of the stack you're most proficient with. for us that meant building on .net and couch. for someone else that'll be RoR and mysql.

agreed.

we (http://friendsell.com) are running c#/bistro/ndjango/couchdb

how sad that firefox reaches its adoption peak while hitting an all-time low for stability. it took me 7 years to jump ship from ie to firefox. it took me 1 to go from firefox to chrome.

well that didn't take long...

http://stackoverflow.com/questions/1890914/how-do-i-backup-a...

it does seem a lot more verbose than it should be.

didn't russia already cop to this being a failed test?

http://www.nytimes.com/reuters/2009/12/10/world/internationa...

seconded. it's interesting how it forces you to build for scale right away.