vvvnnnnvvv

Took a quick look at sleep.io and seems like it might just be CBT-I. There's a free app from the VA (ironically, given the subject of this thread) - https://mobile.va.gov/app/cbt-i-coach. It's a little rough around the edges, but if you have the general idea of CBT-i it's probably good enough.

In case you don't have the general idea, here it is - 1. Decide your desired wake time. Figure out how much sleep you are currently getting.

2. Go to bed late enough that there's only enough time to sleep the amount you are currently sleeping before your desired wake time. When the wake time arrives (or before, if you wake up too early), get out of bed. E.g., If you want to wake up at 7am and you are currently only getting 5h of sleep each night, you should go to bed at 2am.

3. (Be really really tired for a couple of days, oh my god)

4. Once you are finding it easy to fall asleep and stay asleep until your desired wake time, start backing up the bedtime gradually. (* this is where the app will help, can tell you when to do it and by how much)

5. [follow a bunch of other rules about when to go to bed and when to get out of bed and when to exercise, drink alcohol, and coffee]

Not defending sleep.io or your experience here, which does sound very frustrating - just hopefully some help from a fellow insomniac. CBT-i did help me, albeit temporarily. I have to re-do it periodically.

I recently left Amazon, and I don't think the stack ranking is to blame for the reduction in talent (which I also noticed).

Amazon doesn't pay top dollar for engineers, and the delta between Amazon and other companies is growing every year. (The compensation ends up being competitive when you take into account stock growth, but the new hire offers are not attractive.) And it's a very results-driven, stressful work environment. The effect of that is that people who get better offers go elsewhere, both new hires and existing employees. Those who are left either don't feel like interviewing or interviewed but didn't like their other options.

That may be the public way of explaining it, but I see it slightly differently. Amazon doesn't like "good intentions", rather it prefers "mechanisms". We all know that managers should put low performers on PIPs, but Amazon doesn't really trust managers' good intentions. It wants to make SURE that low performers are put on PIPs. The mechanism they've selected is an unregretted attrition target. The target represents the number of people they expect to be under performing and only applies to orgs greater than a certain size.

source: recently left Amazon as SDM

I had a miscarriage at 10w (baby measuring 6w). For many months, I was haunted by things like going in for my first doctor's appointment and seeing my empty uterus on the screen. I thought about all those people, like the receptionist in the waiting room, who said "congrats" even though there was nothing to congratulate me for. I opted for medical management but didn't take the drugs until the pain was unbearable. Although that was the single worst 45m of my life, I don't think about it as much.

I am pregnant again, but I am not the same. I am not excited, I am not making plans. We waited to tell our parents until 13 weeks. Even though I'm showing, I've told the people who absolutely need to know because I don't want to talk about it. I don't want to have a baby shower because I don't want to have to look all the stuff if the baby ends up dying.

I participate in /r/Miscarriage, /r/ttcafterloss, and /r/pregnancyafterloss. People there are sad about losses that happened months, years, sometimes even 10 years ago. They - we! - are triggered by pregnant women, our original due dates (next week for me), the idea of getting pregnant again.

It's a surprise to me that we're able to call this a discovery. I feel like a Native American talking to Christopher Columbus.

I wonder if millenials can't afford to buy in the same numbers as their parents did/do.

I believe the treading is only required for the "boating test", if you plan to sail or row.

One of my CS professors gave us this advice about starting a company (which I think generalizes what you're describing):

Companies don't care about saving money. Even when the amount is the same, they're much more receptive to pitches that involve them making extra money.

Yes! Battery life is a killer feature for me. I'd be willing to sacrifice a lot of functionality for something that was as hardy and needed as little recharging as my kindle.

Gorgeous visualization! Takes a really long time to watch though, even after clicking the "up" on speed a bunch of times, and so it's hard to get the same sense from watching the points on the map as you get instantly from the chart under the map.

Have you considered aggregating a little more, so that years move by faster?

I received a similar email about AWS keys checked into a public github repo. The email was very specific about this being the issue, so I suspect they were crawling and not merely detecting a strange usage pattern.