HN user

jshc

106 karma
Posts10
Comments19
View on HN

^this. refactoring into React or any tech stack does not correlate directly to user engagement or revenue. It sure does have impact; but perhaps it's more relevant to state something like improving page load time, developer productivity, time to market (or MTTR, etc) because of cleaner architecture that enables to iterate faster and so on

React in Patterns 8 years ago

curious about the explicit true and false in one of their code examples. any good reason for that?

// dispatching an action based on state change componentWillUpdate(nextProps, nextState) { if (nextState.open == true && this.state.open == false) { this.props.onWillOpen(); } }

if you have to use a throway foo bar, whey do they need to get back to you? It's as a curtsey but don't think it's necessary. It's possible job hunters just spam resume for no reason. To me, a template reply is no better than a no rely.

How in the world could someone who makes $200K+ live a miserable life?

What's the likelihood for the current startup to exit at $86 million valuation in 4 years? (based on brudgers' calculation. I like his logic!)

Also, I would have to agree with you from my own experience as well, I wouldn't do it again unless as a cofounder.

Perhaps instead of reinventing each tool that already does well in its own space, one could build a platform that allows users to link all these tools (if API is available) and customize with their own workflow and dashboard. I wonder if there's anything similar already existing yet? I feel in some big corps they may have developed their own proprietary homegrown tools for these.

OnHub 11 years ago

still remember the day Google collected public WiFi data ...now they have your WiFi covered ;)