I recommend eating chips An Essay by Sam Anderson www.nytimes.com Join me. Grab whatever you’ve got. Open the bag. Pinch it on its crinkly edges and pull apart the seams. Now we’re in business: We have broken the seal. The inside of the bag is silver and shining, a marvel of engineering — strong and flexible and reflective, like an astronaut suit. Lean in, inhale that unmistakable bouquet: toasted corn, dopamine, America, grief! We are the first humans to see these chips since they left the factory who knows when. They have been waiting for us, embalmed in preservatives, like a pharaoh in his dark tomb. Looking Closely is EverythingOne brick seeingdetailsfood
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