364 karma · joined March 25, 2016
The section about google maps follows a form of criticism that is widespread and particularly annoys me, namely => popular service 'x' doesn't exactly fit my power user need 'y', therefore x is hopelessly borked, poorly designed, and borderline useless.
There is always room for improvement, but all software requires tradeoffs. One of the things that makes a product like google maps so powerful is that it makes a lot of guesses about what you are actually trying to do in order to greatly reduce the complexity and inputs required in order to do these incredibly complicated tasks.
So yes, sometimes when you move the map some piece of data will be removed from the screen without your explicit consent, and yeah, in that moment that feels incredibly annoying. But balance that against the 100s or 1000s of times you used google maps and it just worked, perfectly, because it reduced the number of inputs needed to use it to the bare minimum.
Google maps doesn't need to fit every use case perfectly, and while its fine to talk through how your hyper specific use case could and should work, remember all the times that it seamlessly routed you around traffic from your office to your house in one touch while you were already hurtling down the highway at 70 mph.
And, almost all the vegetables you find at quick service restaurants are lettuce or greens heavy salads, which are fine, but not ideal. Really, the only way to guarantee that you are getting a vegetable heavy diet is by cooking at home.
The less we cook at home and the more we eat out, the fatter we (as a society) will become.
It's an extremely blatant and I thought transparent attempt to change the subject, but, if the first fifteen comments here are any indication, a surprisingly effective one.
One piece of feedback/missing feature was the ability to see a version history. Ideally I'd like to be able to back up my entire set up to github so that we could rollback changes easily.
`sleep 60`
Because one interruption takes x amount of time to deal with and the other interruption takes x + 60 seconds of staring at a chat window that FEELS like 3 times as long
Also 15 mph is a sub 4:20 mile, and for most people will be pretty close to a flat out sprint. Not super adviseable on sidewalks either. Most joggers will be going half that speed.
walking, 3mph
running at an 9 min mile 6.5mph
With that disclosure, was anyone else horrified that the lifespan of these scooters is only 3 months?
Are they really removing enough vehicle trips to make these a net positive from an environmental standpoint?
Is 8 weeks a particularly fast timeframe for raising a seed round? I'm sure that spending fully one quarter of the total lifespan of your company doing something besides building features would be equally unpleasant for many founders.
I didn't read this as the whining of the privileged, but rather as a well-written, detailed account of a business process that is fundamentally important to the tech industry, and yet is extremely opaque to those who haven't directly experienced it.
I particularly want to thank the writers for providing detailed and actionable advice regarding how they frame their business to investors.