slipperyp

Kinda wish there were more details on this page to understand or interpret what the author is talking about or compared it to.

I have a Canon 9000F (consumer grade) that is getting very old now and often difficult to get running when I pull it out, but it scans film at 2400dpi which has been adequate for my home archival purposes. I don't know if this is in the ballpark of what the author used as the comparison for the consumer scanner (nor is the DPI cited). About 8 years ago I was going to start a new film scanning project and thought "Hey, maybe now's the time to buy an updated film scanner" but I learned there is very little on the consumer market and it's gotten very expensive.

I think the 9000f hasn't been made in a while but I still find it to be a great scanner when I need this.

As I'm WFH next to my Synology and look down at my ESD bag-wrapped spare WD Red, I can't help but be reminded of Peter Graves glancing down at his tray with a perfectly cleaned fishbone in "Airplane!"

It's not a horrible place to work. I've worked at Microsoft and work for Amazon now. It's unavoidable that with a company the size of Amazon there will be some (maybe a lot) of bad areas to work and it's obvious that despite even the best hiring practices in the world, you'll find people winding up in a position for which they are not a good fit.

There's a lot of interesting work, though, and a lot of people happy working on it. I wouldn't tell anyone it's the best place to work or that it's "better" to work than another place, but I love what I do and work with hundreds of people who (more or less) feel the same. I also know people who don't feel this way and I encourage them to move on or move out because nobody should be in a job they really dislike (and I'm aware of the incredible privilege that's reflected by my ability to say that).

I don't know if it's statistically valid, but I've used methods similarly based on this to do calculations like you're talking for a role similar to what you described.

There are more subtleties that it might be important for you to take into account - primarily:

1) need to sample fairly extensively before/after outage to calibrate more accurately against Holt-Winters (the Holt-Winters seasonal projection should accurately project the trend, but actual numbers are probably running at some slight or significant rate above/below projections)

2) When running those samples, it's important to sample data where you believe the data points are definitely not impacted by the outage. This is often quite challenging since outages sometimes might span low / peak traffic periods or ramp-up/down periods.

3) Finally, it can be hard to pinpoint the actual start / end of the event (the identify the time samples you want to consider in your measurement for the outage cost). Particularly the end, since there's often some pressure for queued operations (by software or by your users who are itching to complete what they were trying to do) that may make your samples fluctuate. That backfill pressure can be substantial and is important to not ignore in your measurement of the actual cost of the issue. Say you're a retail site - if you have a 15 minute period of 50% order drop but the first 5 minutes where service is restored, the total order rate was 50% above projections. Do you count that as 15 minutes of 50% order drop, or 10 minutes of 50% order drop? Both are legitimate but it's important to know what metric you're measuring yourself against so you're as correct / honest as you can be.

Yeah, but this isn't to produce a drinkable brew. It's not even a super different projection from the brew time when I've homebrewed (which has been a while but was probably closer to 6 hours for me to get it into the primary fermentation tub). This thing looks pretty cool, but I'm interested in seeing more on the whole setup / maintenance and, especially, cleaning.

He wasn't laid off - he was fired. This is the first point the CEO makes and it's an important distinction that the poster seemed to not own up to at all. Not knowing the difference between being fired and being laid off is bad - there's a pretty remote possibility that the poster's direct manager didn't own the message well and told the guy "we're letting you go" and he didn't understand he was being fired, but even if that's the case, most organizations of any reasonable size should have someone in HR handling the exit interview who makes things like this super clear.

I have no insight into what happened here, but I definitely have had experience working with and processing the termination of underperformers who don't recognize or accept that they are not meeting the bar and this sounds a bit like one of those cases.

There are probably some aspects of this separation that were imperfectly handled on both sides, but given the context of "guy is fired from company chooses to be interviewed on company site and say the company didn't give him any reason why he was fired" and the company says "you weren't doing your job" - I tend to trust the company.

Right. It's a bit disappointing in the context of a page with the lead-in "What if every soldier could run a four-minute mile?" but I trust this research is still a work in progress and adding an 11lb weight + helmet and taking those times off is a significant achievement.

Many thanks - that's exactly the discussion I was looking for :)

Apologies if this seems like an inappropriate fork, but the author uses a convention in the introductory paragraph that I find jarring, at best, and I wonder if anyone knows what it's called? It's this (emphasis added):

"...You're not wrong (though not entirely right, because descriptivist linguistics): An intuitive code governs..."

Is there a name for this? It feels, to me, like an "abbrev" or something, where the speaker wants to either convey cleverness or assume common understanding with the audience. Maybe it could be called a "redditism" - that's where I think I normally see the form. Does it have a name? Just curious...

Paul Ford is a magician and offers terrific perspective on subtle aspects of what is typically our American culture. If you're looking for him to beat you over the head with THE POINT about what he insists you're suppose to think, you're reading the wrong author.