Documentation in the age of AI
Documentation Is Not Dead in the Age of AI. It Matters More Than Ever.
LLMs (Large Language Models) and AI are very good at producing code quickly. Sometimes, AI can generate in minutes what would take an experienced developer days to write. It's similarly very common to use AI to "update this function to..." or "modify this data structure to..." or "optimize this code to..." and let the machine do the heavy lifting.
It's tempting. It's really tempting. In fact, not only is it faster and easier to let the computer worry about edge cases or obscure syntax, there's often pressure to get more done, faster. Some places of business mandate the use of AI. There's definitely an incentive to "do more with less." Would you rather pay a human for hours of effort to write a function that may not address edge cases and may not be optimally efficient, or would you rather have an LLM spend twenty seconds to put together something quickly? After all, LLMs are trained using samples of code that were already written, already checked for edge cases, already optimized, and already made available to the public; why not take advantage of those existing efforts and investments?
So, if an AI will be drafting code, who cares about documentation? Why would someone take even more time to explain their code, document their choices, work through the details and consequences of a block of code? If the incentive is to get more code written faster, if the consumer of those comments will most likely be an AI that can figure out how things already work on its own, why in the world would someone look for new and creative ways to make that process take even longer?
That line of thinking is understandable. It is also wrong.
