Physicists analyze systems. Web scientists, however, can create the systems.
At MIT, mostly what I did was documentation. I sort of read things. Wrote some descriptions of various aspects of the file system. Did not really do very much programming at all. At least on Multics.
I do as much debugging as possible on the Mac, but I occasionally must debug problems in the PC world, which is significantly slower.
I was a programmer.
My passions were an intersection between peace in the Middle East and climate change. I know how to understand a technology problem, break it into its components and solve it. I also knew I couldn't make peace solely through technological inventions.
Many of the engineers I interviewed worked on reverse-engineering technology. It's a hallmark of Area 51.
It's kind of a funny way to put it, but if you want to study a dynamic economic system, what you'd like to be able to do is focus on the linkages, say, between asset markets and the macro economy without having to model everything at the same time.
Our system is dynamic, always shifting gears. What I do is I build models to beat the market.
I've got a lot of respect for a handful of coaches, and there's a lot of great stuff put out there on film. So, I always want to stay up to speed on those current trends and figure out if you can steal something that fits your players and your system. I'm certainly not afraid to steal from some of these great coaches.
You look at the world around you, and you take it apart into all its components. Then you take some of those components, throw them away, and plug in different ones, start it up and see what happens.
Troubleshooting a wiring problem is a soul-killing experience.
As you deal with more and more complex systems, it becomes harder and harder to find deep and interesting properties.
Anybody who has been in a relationship, raised a family, worked in business or been a systems analyst, you have to look at how the whole system works together. You have to find those opportunities to collaborate.
Economic engineering is about the design and analysis of frameworks for achieving specific economic objectives.
The cyber review team will proceed with the most sensitive systems first, but ultimately all systems will be analyzed and made as secure as modern technology permits. And hopefully, that's gonna be our technology.
Sometime they don't let you know that they know that they don't know everything, but the core of the medical approach is that you try to identify pathologies, which are subsystems within the human body or the larger system that are having undesirable consequences.
'Debug' is '2001' from Hal's perspective.
To develop drugs for people, we basically dismantle the system. In the lab, we look at things the size of a cell or two. We dismantle life into very small models.
Ross Perot came and visited Apple several times and visited the Macintosh factory. Ross was a systems thinker.
A good engineer thinks in reverse and asks himself about the stylistic consequences of the components and systems he proposes.
As you may know, I am a mechanical engineer.
Moneyball' doesn't have anything to do with on-base percentage or statistics. It's a constant investigation of stagnant systems, to see if you can find value where it isn't readily apparent.
If your project doesn't work, look for the part that you didn't think was important.
The belief that complex systems require armies of designers and programmers is wrong. A system that is not understood in its entirety, or at least to a significant degree of detail by a single individual, should probably not be built.
Before the 1940s the terms "system" and "systems thinking" had been used by several scientists, but it was Bertalanffy's concepts of an open system and a general systems theory that established systems thinking as a major scientific movement
