130 karma · joined March 1, 2014
Ask all those people in NYC with walkups.
I would recommend rubbing with oil before the rub, and not water. Most seasonings are oil-soluble and will work better if you've oiled them first.
Request domain name, e.g. www.google.com
Request type, e.g. A (which stands for IPv4 record), AAAA (IPv6 record), NS, MX, TXT, etc.
Transport protocol on which the request arrived, i.e. TCP, UDP, or HTTPS
Client's AS (autonomous system or ISP), e.g. AS15169 User's geolocation information: i.e. geocode, region ID, city ID, and metro code
Response code sent, e.g. SUCCESS, SERVFAIL, NXDOMAIN, etc.
Whether the request hit our frontend cache
Whether the request hit a cache elsewhere in the system (but not in the frontend)
Absolute arrival time in seconds
Total time taken to process the request end-to-end, in seconds
Name of the Google machine that processed this request, e.g. machine101
Google target IP to which this request was addressed, e.g. one of our anycast IP addresses (no relation to the user's IP)
I think this piece was intended as an eye opener, and a blunt one, because the world isn't going to soften its blows on you.
The "stub point" is a common thing, and can be very, very difficult to pinpoint. They had one specific finisher that kept jamming when you printed to the top tray. It didn't jam 100%, it was pretty intermittent. Well, this finisher had been in another lab for a few weeks or so and they couldn't find the source of the jams or a pattern to them. I had the finisher installed on one of my machines in the 3 days I'd solved it. There was a small stub of plastic on a flag for a sensor. The flag sits in the paper path, and when its moved, the sensor changes state. So this flag has an pretty smooth surface so as to not catch the paper, but somehow this one got a little nick in it. Enough to cause a jam when a sheet ran right into the nick. I filed it down and the machine never jammed again.
We had another issue with a printer at a customer site and the issue dealt with static electricty. a 30kv ESD gun and the inside of a printer.. we still never solved the issue.
"Trust me I know this already. I’m like barely 22."
At my old job, as an engineer, I also put images inline. I got emails all the time, or calls, asking why is this? The easiest way to show someone is in an email, with a screenshot.
Its not any different than an article in a newspaper or on a webpage with an inline image. It actually just works.
"But then we did this different experiment where we did a sale. The sale is a highly promoted event that has ancillary media like comic books and movies associated with it. We do a 75 percent price reduction, our Counter-Strike experience tells us that our gross revenue would remain constant. Instead what we saw was our gross revenue increased by a factor of 40. Not 40 percent, but a factor of 40. Which is completely not predicted by our previous experience with silent price variation."
and then: "Twenty-five percent, 50 percent and 75 percent very reliably generate different increases in gross revenue."
The one I have even has an AUX feature to hook up an external source for audio and a few other interesting features (dual alarms, etc)
Ie: a friend.