This is absolutely not a simple Q&A transcript being dumped online, I assure you. You have no idea how much work goes into something like this. See the discla

This is absolutely not a simple Q&A transcript being dumped online, I assure you. You have no idea how much work goes into something like this. See the disclaimer at the top where it says the interview was condensed? A lot of information is hiding behind that disclaimer. That means that to get these 7 good questions, the writer might easily have asked 21 questions. That means that where you are reading 1-3 paragraph answers, the original answer was easily 10 paragraphs, because people tend to ramble when you ask them about their jobs, even when they're NOT being interview by the NYT. (Here's an experiment for you: Ask a friend or colleague one of those questions, do not interrupt them, in fact appear very interested, and count how many minutes the answer takes to unspool.) That means that when you're reading a nice orderly progression of thoughts, the writer probably had to take bits and pieces from different answers because the interviewee thought of something later to append to the original answer, or emailed a clarification later, or reminded himself of something. That means when you don't see words like "uh" and "um" and "like" and "I mean" and "I think" and "you know?", and when you don't see sentences that trail off into nothingness, and when you don't see run-on sentences, and when you don't see non sequiturs, that's because the writer has carefully removed them. That means the writer doesn't mention that it took three hours, easily, to transcribe a 45 minute sit down, and more time for the follow up to clarify and fact check words that were mumbled or inaudible and not in the notes. You don't want to call something like this "sloppy" unless you know what actually goes into it. You know how non-programmers often assume that very simple, easy-to-use software was similarly easy to make? How they don't think about the edge conditions that turn something that SEEMS like an easy two-week project into a three month project (http://www.joelonsoftware.com/articles/fog0000000356.html http://www.joelonsoftware.com/articles/fog0000000356.html)? You know how people around here are always saying that non technical people make bad tech CEOs because they don't understand the inherent and often hidden challenges of writing code? Well, other fields are like that too, including journalism. (Disclaimer, I write these sorts of Q&As myself.)