oaktowner

I think profiles are a hard-to-discover feature. But once I discovered them, I really liked them.

They help me to separate my work and personal everything. Not just email, but my tabs, bookmarks, saved passwords, extensions, etc.

That is a fascinating story. I hope she writes a memoir some day.

Oh, I'm not above buying the occasional ticket, either -- for that matter, I like playing Blackjack and view any losses incurred as entertainment.

However, people at the lower end of the income spend a lot more of their money (proportionally) on lottery tickets. [1]

And states are increasingly dependent on those revenues [2], which means in effect we've got a system where our schools become dependent on our lowest income population wasting money on what is essentially a pipe dream.

Note: I'm not saying "we've got to stop lotteries!" As I said: I play myself. Just noting that we are funding our government on the backs of people who are making what is arguably a terrible investment.

In other words: lotteries are a tax on people with bad math skills.

[1] Lots of studies back that up; there's a pretty good list here: http://stoppredatorygambling.org/blog/category/research-cent...

[2] http://taxfoundation.org/article/gambling-tax-policy-states-...

The lottery is a tax on people with bad math skills.

Google Product Manager here. I get on the bus about 8:30 and start working. In Mountain View (where meetings commence) by 10a. Usually pretty solid w/ meetings from 10-4. Get on a 4 or 4:30 bus and work again (email, etc) until I get off at 5:30 or 6.

Probably 2-3 days a week I put in an hour (or two, rarely 3) after the kids are in bed.

If they're like my kids (6, 2, and 2): 10 isn't their bedtime...it's when I've finished dinner cleanup after their bedtime and can get on my computer to finish up tasks for the day.

Thanks!

Yep. Normally doesn't. She made slow but steady progress the whole time, so they never resorted to any other means (besides the aforementioned suction device in the end).

It's right. But it's not normal! After 5 hours we employed a suction device (and would have gone to emergency c-section if that failed after 3 pushes).

Baby was 9 lbs, 9 oz (4.3 kg).

This generation of cars doesn't have a "wheel" at all -- there is literally no steering wheel and no way for a human to operate it.

So legislation will clearly need to change before these are street legal.

It varies widely.

My wife had two pregnancies: one was 52 hours (with five hours of pushing!). The second was about 2 hours total.

Neither involved pitocin.

I joined Google after being at a big, soulless enterprise software company.

Google is not the same. However, it is undeniably a big company. If you want to be at a startup, it's not the place for you. But it does "big company" better than most. We are treated amazingly well, we are well compensated, and we are surrounded by smart developers (all pretty unusual for bug companies).

And, in general, people have a pretty wide latitude in heat they do -- especially engineers. And if you get tired of a particular project, movement between teams is encouraged.

I see all of those things in my office for sure.

Maybe it's already happened!

More appropriately stated: couldn't determine a priori that you were a human.

I think worst case scenario is that they get what they have today (solve a captcha style problem).

Con: They will have an additional click. Pro: They might get a more solvable puzzle than some of the "read this distorted text" images they would see today.

Funniest reply I've read all day.

And the world's most popular mobile OS.

YouTube is likely as profitable as Netflix.

http://news.investors.com/technology-click/051914-701377-goo...

I've had the opposite experience. I once was offered an unfair equity package from cofounders of a startup. I (and two others) wrote up a document voicing our unhappiness and the reasoning behind it.

And they ended up agreeing with us. While the offer they first came up with was not fair to us, they honestly hadn't realized it (they had a lot on their minds, it was the first solution that came to them, and they simply proposed it).

We did not poison our relationship. They agreed that our solution was more fair (it involved each of them getting less equity and each of us getting more, by the way). And, in the end, the company had a (modestly) successful exit.

We are all friends to this day.

OP: If it's unfair: write down why it is unfair and what you would propose as a more fair agreement. Only if and when they reject that should you involve an attorney. But there is absolutely a chance that they will realize your solution is better.

Ah, Ousterhout. Guess he's at Stanford now; he was a prof at Berkeley when I was there. He had an amazing knack for presenting CS in an entertaining (and, at times, hilarious) manner.

Best professor I ever had.

Yup. I agree -- I have lots of Apple devices, bought my first Android, and this bug does not make me happy.

I'm not a fanboy for either camp...but I also do want to feel like a vendor is actively trying to lock me in to their hardware forever.

Which will make me less likely to choose an iOS device next time I buy one.

I agree - I think of "high-end" as indicative of price.

> Hundreds of millions of people sharing rich media in realtime on non-FB services is a genuine threat.

Yup, I agree entirely. This wasn't about getting new users, it was about getting the content to run across their services.

Johnle - Indeed. It works better with Chromecast than Netflix on Android in my experience!

Waze is better for both of these use cases. Maybe Google will integrate more of its functionality over time, but for now (though I hate the look and feel) the routing and traffic info make it absolutely worthwhile.

But that's only from within the Google ecosystem. Click on on a link in a non-Google app and you won't see Chrome as an option.

Nice call! I was coming in to post that link, but I see you beat me to the punch.

One thing to bear in mind is that documentation serves two different audiences.

One audience is the people who will use your code. For them, every external method should be properly documented (sure, use a tool for this). And make sure it's good enough that (barring debugging situations, because you wrote perfect code) your "users" never have to look inside your code. (If I think about this in C++, I think you should be able to look at a properly commented header and never read the code)

And then there's the poor slob who's going to come in and debug/fix your code some day. He may not need to have every method doc'd but he damn sure needs to know what's tricky, what's interesting, where the gotchas are, etc.

He has time for running? I think I know what's wrong.