psgibbs

tl;dr: government incentives

Range goes way up – electrification can turn a 10+ mile commute from something intense (where you need a shower when you arrive) into something manageable.

It allows bikes to be a substitute for far more things that you'd otherwise use a different mode of transportation for.

My understanding is this is precisely backwards: using BMI to gauge your own health is inaccurate, but using it to analyze populations is the intended purpose.

I think there's some "both sides are equal" aspects in your position that mischaracterize the reality as I understand it.

In 2016 Democrats thought manipulation / fake news (exactly the root problem in this article) was happening, and it appears it was. They recognized there is risk to systems and proposed to enhance election security based on the new (and proven) information that state actors were directly involved in trying to manipulate our election. I do not remember (I may be proven wrong), Democrats undermining the fidelity of the election itself, or alleging fraudulent votes, excepting one or two places where it was proven to happen (see the Dan McCready campaign).

My understanding is both parties now are roughly aligned with their longstanding positions in terms of how they view election security and relative occurrence of voter fraud and malfeasance. Comparing the 2016 positions on interference via fake news is apples and oranges, it is fundamentally a different subject – and the allegations of election interference were literally proven true by a justice system run by the Republican party.

I've seen plenty of junior engineers who read a FP blog post, and start arguing about 'purity' and the need to refactor lots of code – without having any clue that pure functions are useful regardless of other coding paradigms / architectural decisions.

Without much more detail than this, they don't sound like cofounders. If they're waiting until you launch to go 100%, then you're assuming all the risk right now.

Again take with a grain of salt, bc I have no context, but , if there's one you think is clearly the best, that you like working with them, get them to be a cofounder and make them go all in. They can do lots of manual work to validate the idea/product (ie manually do things you'd like your product to do). If there's noone you could see doing this, then their role is probably not going to grow that much when there is a 'product'.

Also: the product will never be done, and framing launch as a binary event doesn't help you (or your potential cofounders). It's all just a continuous spectrum of trying to cover as much scope/utility as possible for your users, and using a product to try to automate that. After 7 years, you'd be shocked how much stuff my sales cofounder does manually that we had framed as a 'required feature for launch'.

I'd make the argument that because there are low costs of switching (as has been mentioned elsewhere), these are scale effects (like in most industries), rather than network effects.

Why? I actually still have a 6S and I find the physical button feels mushy in comparison to the new solid state / haptic button. Is there a disadvantage I'm missing?

Yes – every day. By most metrics, my startup is going great, but it's taken years of all-nighters, working weekends, and skipped vacations. I love what I'm doing, but I'm also cognizant of all the friends, relationships, family-time, and other experiences I'm not investing my time in as much as I should.

Whether things work out or not, I'll always wonder what the counterfactual was, all the unknown-unknowns I chose to miss out on.

Regardless of what you read, what you feel like you're missing out on, know everything comes with a sacrifice. My only advice would be to think carefully about what you choose to invest your time in.

We use it for our core app, and now have a bit over 10K lines of application code.

Our general strategy is to organize the app by functional areas, each area of which is organized similarly to how most angular sample projects are: with a directives.js, controllers.js, services.js, etc. We use ui-router to tie this all together.

It's a $10 million dollar idea, they just sold 15% of it.