When I auditioned chairs at a previous job, I greatly preferred the Embody (also by Herman Miller) to the Aeron. I probably sat in it for 4-5 years before changing jobs, and was quite happy with it.

This acquisition doesn't make any sense to me. Broadcom is buying all of Brocade, selling off the pieces poised to grow in the wireless and IP networking segments, and keeping the part that serves the shrinking storage-specific networking market? Can somebody explain this to me?

I hope they don't wreck the IP networking and wireless companies. I really like the Brocade VCS fabric stuff and Ruckus wireless kit..

The two I care about are that it supports larger file attachments and it's encrypted.

Do you have a source for this? All I've seen is that Akamai/Prolexic was unwilling to keep doing it for free, because it was getting really expensive. That seems like a significant difference, especially from the perspective of somebody intending to pay money for the services rendered.

That's interesting. My recollection from working on them a bunch of years ago was that our mainframes were IPLed on a regular, scheduled basis, because the folks responsible for them were disciplined about it and wanted to make sure there would be no surprises when one needed to be restarted. The fault tolerance you mention was used to make sure that the scheduled IPL's were the only times they went down though, and I never saw any unplanned downtime on them.

I use Cloak on iOS, and it supports this functionality. I configure it to allow unencrypted traffic on specific trusted networks, and the VPN auto-connects on any network that I haven't approved, blocking other traffic until the VPN comes up. It seems to use the enterprise features Apple has provided to do this via a VPN profile, and it works very well. I have no idea what features it supports on Android and/or Windows Phones, but I'm very happy with it on Apple devices.

It demonstrates either a lack of understanding or more than a passing familiarity with the applications. MS Office has used AES for the built-in encryption since Office 2007. That would seem like a reasonable choice for sending a file to a contact, provided you choose a strong password and communicate it out-of-band.

According to the Boston Globe, police pay in Massachusetts can exceed $250k, not including benefits.

They could change the timeouts. If an iMessage is sent to a destination that's a phone number (instead of an email address), and a device configured to receive messages for that phone number has not checked in within the past 5-7 days, deactivate iMessage for that phone number until a configured device checks in again.

I agree this is mostly user error and haven't had any problems resolving it for people who've asked me about it, but people don't typically anticipate this result when switching phones, so containing the undesired effects to a shorter transition window would seem like a helpful thing to do.

If your tapes are writing that slowly, something is wrong, and I'd be worried about shoe-shining. Without putting much effort into it, my LTO5 jobs currently run at around 125-135MB/s. With modern tape, it helps a lot to stage to disk first, or get software that can multiplex backup streams to keep the tape buffers fed.

This isn't true. There is a gender-neutral, third-person, singular pronoun for a person. In the nominative case, that pronoun is "he". In the objective case, it's "him".

Yes, it's ambiguous that the gender-neutral pronouns are spelled and pronounced the same as the masculine ones, but it's far from the only case in English where we've got two words spelled and pronounced the same that mean different things. I always figured if people wanted to communicate in an unambiguous fashion, they'd choose a language other than English..

In the current arrangement, the parallel CA hierarchy allows you to provide a (theoretically) verifiable connection despite your registrar or DNS provider being perhaps less reputable than you'd like. For an attacker to silently redirect your SSL traffic, he has to compromise at least two external entities--your CA & DNS host/registrar or your CA and somebody in a position to MITM your traffic (obviously a local compromise gets him everything, but this is within your direct control). While I'm no fan of the CA model, the stuff pulled by companies in the DNS market (registrars and hosts both) make the CA's look positively responsible, and handing them all the keys necessary to silently redirect traffic makes me uneasy.

It seems that by suggesting these functions be consolidated into DNS, you're effectively saying that by consolidating two untrustworthy parties into one untrustworthy party, you'll be more secure. I'm pretty sure I don't agree with that, but I'm willing to listen. How do you address such criticism?

This is an interesting approach, especially across hosts in a cluster. Is it safe to assume you expect your hosts and interconnect to be very reliable?

I'm curious about the methods you use to mitigate the problems that would seem to result if you clone VM 1 from Host A onto VM's 2-10 on hosts B-E, and Host A dies before the entirety of VM 1's memory is copied elsewhere. Can you shed any light on this?

While this was true in ESX 2.x (which introduced virtual SMP), this is no longer the case. This limitation was largely removed with the introduction of relaxed coscheduling in ESX 3.x (2006-ish). More information is available in this document.

It should be cooked until the fats have just liquefied, for optimal juiciness and flavor. In my experience, most good restaurants call this "rare". At most other restaurants, it's a complete crapshoot, which is why I typically prefer to cook steaks at home.

Start with high heat to sear, move to lower heat to finish if necessary, and don't forget to let it rest before you serve/eat it. Rubs are an exercise left to the reader, but kosher salt & fresh-cracked pepper make a good place to start.

Enjoy!