Jason GormanWe spend roughly 10x as much time reading code as we do writing it. A tool or technique that makes you twice as "productive" at writing code *at best* makes you 5% more productive over all. Making your code easier to understand will have 10x the impact. But that doesn't sell tools or put developers out of work, so you won't be reading about it in Forbes.
Kevin Trainor@jasongorman It just occurred to me when a programmer takes the clear ideas in their head and creates code with bad variable names and function names that a lossy transformation is taking place. It is not possible for a person or an LLM to subsequently offset that loss by processing the code. The information has been lost.
Not a Spring Onion@_KevinTrainor @jasongorman
The real question is: If the programmer didn't express themselves properly in their code, were the ideas really "clear" or was the programmer just delusional?
The real question is: If the programmer didn't express themselves properly in their code, were the ideas really "clear" or was the programmer just delusional?