Funny you mention log files with extra spaces. At my current job, I deal with an API called the RTO, and I wanted to log the requests to that API and the matchi

Funny you mention log files with extra spaces. At my current job, I deal with an API called the RTO, and I wanted to log the requests to that API and the matching responses. Of course the words "request" and "response" are not the same length. But I thought it would look nice to line things up for a request and its matching response, so I just added an extra space after "request:", like this: RTO request: {...} RTO response: {...} When testing locally in a terminal, this looked great. Everything lined up and was pretty. What I didn't realize was that most people view these logs in New Relic, which does use a monospaced font but does not prevent collapsing of adjacent spaces. So the logs look like this: RTO request: {...} RTO response: {...} Obviously not the end of the world! But it did happen that the first part of the {...} stuff should match between the request and the response, so it made it easier to understand (if it worked) to line them up. I am tempted to change the messages to this, which I think will work around this problem: RTO request : {...} RTO response: {...} Sometimes you can't win for losing!