jaymon

I'll second someone else's recommendation for The Martian, that was just a really fun read you can just burn through because it is so enjoyable.

If you want another really fun read, Ready Player One was fantastic.

I've also enjoyed the Old Man's War saga, there are 6 books but you can skip book 4 since it is a retelling of book 3 from the POV of another character. This is a space saga and I really like the universe he created.

In the hard sci-fi genre, I really enjoyed The Forever War.

And for just pure world building fantasy, the Game of Thrones books (The song of Ice and Fire series) are some of the best written books I've ever read.

I've added it to my list of books to inspire my kids. So if they ever come to me and say, "Dad, what is chemistry good for?" I can just give them The Martian and say, "read this and you'll know"

Did you like The Atlantis Gene? I've almost pulled the trigger at Amazon a couple times but the reviews seem hit or miss and my reading list is already so long.

I started The Martian by Andy Weir about 3 days ago and I'm really enjoying it. It's a really entertaining book that I highly recommend!

Last week I finished The Paradox of Choice and Zero Day. I enjoyed both of them, although I don't think I'll be reading any of the sequels to Zero Day.

Before that I went through The Maze Runner trilogy, those were entertaining reads.

Some other books I've read recently that I can remember off the top of my head are the Divergent series of books (eh), How Will You Measure Your Life by Clayton Christensen (great read), Ready Player One (loved, loved, loved this book), Starters (didn't bother reading any more in the series) and Moon walking With Einstein (I enjoyed it).

Just a note so people don't get confused, while specifying packages with >=1.1,<1.2 seems to be similar to the tilde in npm, in practice it isn't.

Basically, when you use >=1.1,<1.2 it will install the best version that matches at the time of first install, and then that version will never be upgraded because it will always satisfy the requirements. So you don't actually get 1.1.x release updates unless you install them manually.

We do, however, use this syntax in development when testing new versions to make sure any subsequent runnings of pip doesn't obliterate the new versions of modules we are testing.

I'd love official pip support for ~1.1 type declarations.

Medicare and medicaid have traditionally underpaid regular commercial insurance with the result that more and more doctors have dropped it over the years.

So it makes sense that payments would concentrate around certain doctors that are still accepting it because more people on medicare will go to them simply because they don't have any other choice, especially in areas that have high concentrations of the elderly, like Florida.

The problem I have with analysis like this is it doesn't take into account what Yahoo actually needs to do to grow. For the most part, the companies on the list are innovative companies, led by talented CEOs/entrepreneurs and are leaders in there sphere.

But Yahoo's revenue is about $1.2 billion a quarter, and I would say that they would need to grow that by 5-10% to even approach any sort of potential turnaround territory. That means they need roughly $50 to $150 million in new revenue a quarter, I bet you all those companies together don't make that amount of money in a year.

I think it would be awesome for Yahoo to buy innovative companies and give creative people free reign, but the reality is Yahoo buying these companies is like putting a band aid on a bullet wound. Yahoo's just too big and those companies are just too small to turn Yahoo around.

This reminds of the Evan Williams quote from "Founders at Work" pg 124:

"luck comes in many forms -- and often looks bad at first. I always look back on the deals that we didn't do and the things that didn't work out, and realize what seemed like a bummer at the time was really lucky [...] if you have some plan and it doesn't go that way, roll with it. There's no way to know if it's good or bad until later, if ever."

A lot of what is "best" has to do with how specific you want to be. Appending "every" to a date is great if you want something to occur every N. But what if you want it to occur every other N? Or the first N of every M? There's a reason why things like Crontab or iCalendar's RRULE are so specific and verbose.

In order to decide what is "best" I would first decide how specific I needed to be and then start to narrow my input options based on my defined need.