Worth noting that this is an exceptional track record - 4 of 5 startups with a paying acquisition. Great story, but it’s not likely the normal result of doing 5 startups :)
One big advantage of using string representations of dates is avoiding misunderstood timezone calculations that may or may not occur at various layers of the backend stack. The downside of course is storage space.
For those seeking the office experience, it will feel a lot different when everyone is maintaining 6 feet of distance. Not going to be the same experience people were fond of, IMO.
1 is the only number for which 3n + 1 = 4n. So a number that didn’t reduce to 1 would have to get stuck in a loop of multiple repeated values. That seems unlikely.
The Uber layoffs announced yesterday now seem to be strategically timed. If we assume the standard 3 month severance offered by big companies, the layoffs would free up cash at the end of 2019 - right when they’d need it for the increase in CA drivers benefits.
Well, in the real world I find that you don’t understand the problem you want to solve until you’ve applied a working solution to it. Practically speaking I tend to deliver quickly to accelerate the process, then refactor once all the requirements have been exposed. As mentioned here, this probably doesn’t project well in an interview. It’s a case where the most efficient practice is not the most presentable one. I’ve failed interviews for this reason too. Lessons learned!
Spreadsheets could also be understood as just a fancy pen/paper for a manual business process. Looking at it this way, the competition isn’t excel but rather doing things by hand (i.e. a non-solution vs a competitor).
I just saw ads on that blog post. I thought that was odd given the context. I went back to see again, and they were not there anymore. Is one of the included script tags up to no good?
The challenge of details is best solved via rigorous definition of “done” (i.e. acceptance criteria). If you don’t have consensus for that, there are a million ways someone else can re-define the problem and thus expose “incorrect details”. Many orgs delay this consensus, making for plenty of post code review work, but I don’t think that’s necessary bad so long as you don’t let PR comments hurt your ego.
I suspect this might work better than expected. The fear is that employees will exercise some form of nepotism that would “lower the bar”. That might not happen in practice though. Would love to see an experiment.
Fundamentally, are performance systems done objectively or "on a curve"? Meaning, if 100% of the engineers are operating at say Staff Engineer level, do they all end up with that title? Or does the Staff Engineer title really come down to some sort of percentile in a stack ranking?
Given that you were essentially learning management while in the role, did you ever end up hiring people with prior management experience to report to you? What was the mentoring like for these folks - were there cases where your reports actually had more experience than you?
Solution: create a surplus of homes. That will detach price from income. Nothing else will work. (Note: we did this with food and it successfully kept prices low)
Below is the most relevant snippet, I don't think we see this as often for soccer as we do for other sports in the US:
Gwen Cherry Park is tucked near the edge of Liberty City, a lower-income neighborhood in northwest Miami that gave rise to Chad Johnson and Santana Moss; Amari Cooper, Devonta Freeman, Lavonte David and Teddy Bridgewater are also from here. Every Saturday, the park fills with dozens of boys, their families setting up tents and frying conch before football games. Grandmothers walk the fields in T-shirts with their grandsons' faces printed on them; high school coaches scout from the sidelines; grown men bet on games between children.
Wondering outloud: given what facebook did to snapchat, would one assume that you have to "beat" snapchat (and anyone else) without resorting to a legal defense? In other words, if you can't beat snapchat at your own idea (assuming your idea is good enough to warrant their interest), are you doomed whether or not you signed a non-suit agreement?
People used to summarize YC in a similar way. The devil is usually in the details though. I think this program could be valuable to a certain type of aspiring founder.
Seattle isn't too far behind SF with regards to housing (according to recent press at least). I've been wondering for years: could the larger employers in SF do more to coordinate which cities are expanded to? I'd be willing to change locations if my (tech) employer gave me the option, but others might have concerns about putting 'their eggs in one basket'. If 10 SF based companies all opened an office in the same city, would more people consider the move? My hunch is yes and I'd love to see this theory tested :)