trotter_cashion

Ahh... never thought of doing that. I like it.

More like the author was lazy and not thinking about correct ordering of the date there. It should absolutely be yyyy-mm-dd. I'll be updating the post w/ feedback from the comments sometime today or tomorrow. So expect to see that change.

My issue with host and version at the beginning of the log is that they'll roll away when your logs rotate. If you've got a service that's rarely taken down, anything written to the front of the logs is likely long gone by the time you have a problem. That said, there may be a better way to handle these two. I certainly don't like repeating information if it's not necessary.

Thanks for the feedback. I'm with you on the milliseconds and threads bits. As for hostname / version... how are you getting those into your logs? I've found having version in the logs very useful (and wished I had it when it wasn't there).

It's pretty close, but it has a few improvements. For starters, the Pivotal setup used Ikea Galant desks, which are a bit large. Instead of needing to cut that in two, we've got two Galant extensions. This eliminates the need for the desk staggering pattern shown in the pivotal post.

Second, the pivotal setup is based around an iMac with a second screen. We've found this somewhat odd as everyone has their own laptop. Therefore, this setup is driven from a laptop with the key addition of an hdmi splitter to make driving two screens from the laptop cost effective.

I've found pairing to be very useful when I don't know the stack or codebase all that well. It can certainly be frustrating though when the two people in the pair have extremely mismatched skill levels and are working against a deadline.

I wonder how strategic they're being in their choice of IPs returned. Sending a large number of invalid requests from IPs all over China to foreign servers could help in masking their hacking attempts against those servers.

Yea, totally a joke and not from github :-)