rehabindian

We just released a new product and its a bit unnerving. You know there are tons of features that we could put in; there might be a bunch of bugs we don't know, and we are somewhat worried that user-flow, or even the basis premise of the product is wrong. How do you deal with this?

Apart the constantly refreshing analytics, staring at the the dashboards, crash logs, or searching for tweets, mentions etc..

..two big things hackers are excited about now and can’t articulate why: Bitcoin and 3D printing" Paul Graham.

<p><p>Because Fuck governments, thats why. Hackers (the denizens of silicon valley) have always struggled with authority bordering in tyranny. Regulation which makes no sense, disadvantageous to the new kids on the block, skewed towards favoring old relics. Bitcoin represents liberation of a key aspect of economy, money. Hackers get to set it up to suit the needs of the new gate. (ref: Exit from 'Exit, Voice, & Loyalty). 3d printing represents the same, not locked in by pseudo free market appeals to the way of wild west.<p>P.S: This was a shower thought and wanted to post it somewhere to get feedback and discourse.

In the day to day startup grunt, Me and my team are trying to find how and when we should use user testing and user research in our product development process. Feedback, personal experience, and thoughts appreciated.

Douglas Crockford is back in action. His Javascript talk coming up this 21st on Paypal Campus in San Jose. Seems like the talk is open for all. Here's the RSVP link: http://www.meetup.com/TechXploration/events/65087252/

Was anyone there for his previous talks, if so can you share your experience?