95 karma · joined April 21, 2016
I am a time-restricted eater. I use Zero to track my eating windows and make sure I'm not trending in the wrong direction, and that gives me the peace of mind to let up every once in a while.
Just this morning I broke my fast early because I didn't eat enough last night and I was pretty zonked before my workout (beyond the point I thought would be productive). I ate a few dates, recorded it in Zero, and will live to fast another day.
4% of 3 hours is more than 7 minutes! That could be equivalent to tens of hours on the road. $250 is a _great_ investment at that rate.
This is the "Why go to that expensive restaurant?" argument all over again. When it's your hobby, and it's important to you, the thought process behind the purchase is very different.
https://www.nytimes.com/interactive/2014/06/05/upshot/how-th...
P.S. I am also a happy NYT subscriber. +1 for supporting high-quality journalism!
One of the great things about being an IC at an early company is there is so much to do. You get to put your fingerprints on a lot of things across the company because there won't be enough people to spread out all those tasks. As the company grows, those foundations become opportunities for you to grow from sole contributor to technical lead on each one; so much so that the hardest part will be choosing what to give up control of, not to what to keep contributing.
If you find yourself in this situation, I strongly recommend being involved in the search for your VPE. It could be really frustrating to build the technical foundations for a company only to be so frustrated by a poor manager being hired above you without your input that you might even quit. Wouldn't be good for your equity, either :).
PS this implies that if you don't want to grow into mgmt, you'll need to grow into being a good lead developer. Early startups have no room for people unwilling to grow.
The 'cheap' big cities (sticking to the US, those in the middle of the country: Chicago et Houston in particular) have just enough tech to show up on the hypothetical chart and are cheap enough to place well. But IMO, even as a U of Illinois alum and massive fan of Chicago, the tech density isn't such that you would be able to find particularly interesting work, especially compared to the Bay. That said, surely there enough startups that need app/web developers to pay your rent in those relatively inexpensive areas if that's your thing.
The cities that interest me are those with a high density of tech at a lower cost: Austin, Portland, Raleigh, etc. The Bay housing cost is trickling down there too; there are so many people making _so much_ in the Bay that still can't afford to stay that when they start moving to these places they can really affect the smaller markets. Austin has had a crazy housing boom in the last ~15 years, but it would take a _lot_ more people moving to Chicago to move the needle there.
You still face issues with inequality squashing culture, like in Austin, which has a strong history of art and music and is so much cheaper than the Bay but so much more expensive than the areas around it. Bigger cities can generally support the diversity of people needed to maintain a viable culture if they aren't 7x7 miles and surrounded by water on three sides like San Francisco is. In other words, you could move out of the Bay to one of these places and live happily for a few years before you find these same problems following you to your new home.
This is a bit of an exploration but I think about leaving the Bay daily as my wife and I get more serious about starting a family. We talk about this often, and to each family, it's the most important thing in their lives. SV is really in for a wake-up call as it sheds talent that can't afford to stay.
Without the `del a`, it does, because they both have active references. If they were unique objects, we'd see a unique ID for `b` as long as a reference to `a` is active.
> Strings seem to behave like tuples. When I delete a string and create a new one it creates a new object with a new address.... unless the strings are of the same length.
String _objects_ (as opposed to variables referring to them) are immutable in Python. They tend to be allocated anew, but for optimization reasons you can end up with cases where the string objects have the same ID. Like here:
>>> a = 'asdf' >>> id(a) 4389881424 >>> a = 'qwerty' >>> id(a) 4395015672 >>> a = 'asdf' >>> id(a) 4389881424
'asdf' has the same ID with no deling involved because its object wasn't GC'd yet.
Below are some relevant links if you want to knock yourself out (some do) but I write an awful lot of Python and even for me this is well into the realm of "what happens when..." after a few beers or job interview trivia.
https://rushter.com/blog/python-lists-and-tuples/ http://guilload.com/python-string-interning/
Depending on entities like banks to determine who could/should be trusted, e.g., for loans, has allowed systematic discrimination against marginalized parties like African-Americans to continue for centuries. Being able to push the determination of trust out to the entities closest to the interested parties - perhaps those in their community who have lent them money and had it paid back - could allow for those people to have the same opportunities as the 'mainstream'.
There have been rumblings about Yelp reviews being manipulated for years. Small business reviews on blockchain don't allow for that kind of manipulation - and could be integrated with smart contracts that verify that only actual patrons of that business could leave reviews.
My personal favorite is the idea of blockchain election systems. It's not that I don't trust the U.S. government _per se_, but Congress has shown astounding indifference to modernizing and securing our election systems on their own. I would vastly prefer a well-designed decentralized implementation over whatever they could implement, securely, centrally.
PS I'm not saying these implementations are trivial or easy in any way, nor are we necessarily ready for them, especially for the general public. But I do feel that removing centralized arbiters of trust could leave us in a better place than where we started.
This is in opposition to someone (who may otherwise be a fine employee) who just wants to build React UIs, or a streaming ML backend, or whatever, and is agnostic about what they ultimately work toward.
Organizations with both types of people can work well (and a mix is probably healthy). Personally I prefer having confidence in the idea that the people with whom I work have customer pain points top-of-mind rather than the most kick-ass Spark/Cassandra/etc. cluster out there.
The gist is that while you (as the average B2B startup) can estimate how valuable your product is to your average customer, you will most likely vastly underestimate the cost of replacement for such a system. In other words, if your sales pitch goes well and they like the product but think to themselves "How much would it cost us to build this ourselves?" you will underestimate this cost from the outside. This is because the cost of replacement is a reasonably good proxy for a price ceiling and by being aware of it you can get a much higher average selling price.
NVIDIA is also in a tough spot in that they can't cooperate too closely with either Intel or AMD now that the race for accelerators is heating up. Understandably they're pretty psyched about Tegra but I'm not sure I'd want to rely on that and I bet they don't either.
This dude can explain grand ideas encompassing human civilization in (relatively) simple, brief, and entertaining language and I can't get enough of it. I think Homo Deus's forward focus will appeal to the HN crowd more than his more famous Sapiens.
Seriously though, Carcassonne has taken over my gaming group. We still play other games now and then but we've played it more than anything else by a long shot, and we regularly play with 2 all the way through the max of 5 people and it's fun in all incarnations. Truly incredible for a game of its simplicity.
About the OP: I effing _love_ pizza but struggle to make it at home. The quality and quantity of knowledge in this post is fantastic!
May I ask you about your first 'biggest learning': how do you eschew cofounder responsibilities in an early company? Someone who genuinely cares and/or is really interested in the core business (pretty common among first hires of startups) may have a hard time turning work away or willfully not participating in major discussions/planning when they believe their contributions could be valuable. In other words, situations when you know you can contribute but the company will get the 'better end of the deal' as you take on more responsibility without taking on more compensation.
It sounds difficult to ride that out - were you able to do that successfully or are you saying "This happened to me, don't let it happen to you?"
If your expectations are "reasonably entertaining book that's reasonably informative" and you're remotely interested in econ or behavior, it really hits the spot.
Your learning will culminate in this course: https://www.udacity.com/course/deep-learning--ud730