I would argue that writing code is equivalent to writing, in general. As in prose, you're exploring a subject known to you. You've though about the problem at h

I would argue that writing code is equivalent to writing, in general. As in prose, you're exploring a subject known to you. You've though about the problem at hand, you've come up with a solution after a lot of going back and forth, you're now trying to impart this knowledge to other humans. As such, you have to be clear about what you're saying, going straight to the solution and not go round the thought and cover it up. That is, if you actually do have something interesting to say about it, and you're not thinking about gaining likes or money or fame from it. I've seen some projects lately with many people involved and months or years of development time invested in them, that I, an average programmer at best, was able to solve with a few days work and with at least an order of magnitude less paper used. [..]they put what they have to say into forced and involved language, create new words and prolix periods which go round the thought and cover it up. Moreover, they write down words, nay, whole periods, which mean nothing in themselves, in the hope, however, that some one else will understand something from them. I've seen comments and READMEs, for example, that have the exact same attitude to them, that is, they are written in the hope that someone else will understand them but the writer actually didn't, he doesn't understand why the project might be useful to someone else. I've seen big frameworks used, tests conceived, build methods and CI implemented but where the actual substance of the project was missing. Dozens of git branches and complex merging good-practices for projects with at most a few thousand lines of code and 2 or 3 developers only because someone else might look at it and see what a good job we've done. These projects usually don't solve much, but they sure talk a lot about how nice it is and how it will solve lots of problems for its users. Nothing else is at the bottom of all such endeavours but the inexhaustible attempt which is always venturing on new paths, to sell words for thoughts, and by means of new expressions, or expressions used in a new sense, turns of phrases and combinations of all kinds, to produce the appearance of intellect in order to compensate for the want of it which is so painfully felt. As years go by, I really feel that one, if not the most important skill in this field, is knowing how to write, how to cleanly and clearly express your thoughts that you yourself have about the problem and your ideas about the solution.