RyanGWU82
Joined 19 years ago
Joined 19 years ago
According to the timeline on their own incident, it took them 71 minutes to notice the issue and acknowledge it publicly.
He first made this argument in 2017 in an article about Uber: https://stratechery.com/2017/the-uber-dilemma/
This is indeed a dupe.
* The sound quality is excellent. Wired or wireless, the sound is sharp and crystal clear. But it's not particularly flat; there's a lot of midrange that makes it sound a little muddy. I've set up a custom configuration for the iTunes equalizer that helps with the (rock) music I listen to: punchy bass, clear treble, but less mud in the middle.
* The noise cancelling isn't bad. It does a great job on public transit but it's not as all-encompassing indoors as the Bose QC35 seemed to be, from the little I've tried them.
* The BB2Ps aren't nearly as ugly as the product photos make them look. They're not particularly brown in real life, just dark.
* They're pretty comfortable although I find it fatiguing to wear them for more than a couple of hours. The new over-ear shape looks like it made a big difference on the comfort level.
* The Bluetooth signal tends to cut out quite a bit from my iMac at home, which is pretty disappointing. It works better from my MacBook Pro at work -- not sure if there's some interference at home or what.
Overall I do like them, but I don't know if I like them enough to justify the $200 I spent. I haven't decided yet whether to keep them long-term. If I don't keep these, I might switch to the Beats Solo3 without ANC, or just bite the bullet and go for the Bose QC35...
But it's only a penny, right? How much could it matter? It actually matters a lot. At both my previous and current employers, a surprisingly large portion of our hill comes from data transfer across AZs. All the microservices, all the memcache hits, and all the database replication add up quickly.
One downside is that you need enough free space on your disk to hold the packed copy of the table, so you need to run it before your disk gets too full. The last couple of times we've waited too long, so we've had to move the data to a larger host before we could repack it.