Don't Write the Tedious Thing An Article by Maud Newton maudnewton.medium.com Ugh, now I have to write this boring part, I would think. I would spend a few days in active rebellion against this directive that I imagined the book was imposing. Then I would realize: this is my book! There are no rules! I can write it however I want! Also, I would think, if I’m bored by something that I believe I need to write, the reader undoubtedly will be too, if not because the subject is inherently boring, then because I myself find it so unbearably tedious to imagine discussing it for five pages. Often as not, I would remember some aspect of the subject that deeply interested me, something a little outside the way it’s usually perceived or written about. Then I would meditate on that, and soon I would be scribbling notes from an increasingly excited place until I found a way forward. A form of beginner’s mind. Zen Mind, Beginner's Mind boredomwritinginterest
The heart of systems engineering While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes. Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all. I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements