Quotes About Systems

Cyber attacks rain down on us from many places. You have to make your systems secure and safe and teach your people cyber hygiene.

I've heard a number of our alumni - people who are running schools and school systems - think a lot about different models for the teaching profession.

My being a teacher had a decisive influence on making language and systems as simple as possible so that in my teaching, I could concentrate on the essential issues of programming rather than on details of language and notation.

I'm beginning to view democracy as the Siri of political systems. So much better in theory.

Yet among the countries most comparable to the United States and where democratic institutions have long existed without breakdown, not one has adopted our American constitutional system. It would be fair to say that without a single exception they have all rejected it.

The Dependency Inversion Principle (DIP) tells us that the most flexible systems are those in which source code dependencies refer only to abstractions, not to concretions.

If we are diligent about building well-formed and robust systems, we should never let little, convenient idioms lead to modularity breakdown. The startup process of object construction and wiring is no exception.

Arranging our systems into a plugin architecture creates firewalls across which changes cannot propagate. If the GUI plugs in to the business rules, then changes in the GUI cannot affect those business rules.

As an engineer, you have a depth of knowledge about your systems and projects that no managers can possibly have. With that knowledge comes the responsibility to act.

OCP: The Open-Closed Principle Bertrand Meyer made this principle famous in the 1980s. The gist is that for software systems to be easy to change, they must be designed to allow the behavior of those systems to be changed by adding new code, rather than changing existing code.

The goal of the principles is the creation of mid-level software structures that: • Tolerate change, • Are easy to understand, and • Are the basis of components that can be used in many software systems.

LSP: The Liskov Substitution Principle Barbara Liskov's famous definition of subtypes, from 1988. In short, this principle says that to build software systems from interchangeable parts, those parts must adhere to a contract that allows those parts to be substituted one for another.

The OCP is one of the driving forces behind the architecture of systems. The goal is to make the system easy to extend without incurring a high impact of change. This goal is accomplished by partitioning the system into components, and arranging those components into a dependency hierarchy that protects higher-level components from changes in lower-level components.

there's no such thing as a program that is impossible to change. However, there are systems that are practically impossible to change, because the cost of change exceeds the benefit of change. Many systems reach that point in some of their features or configurations.

There was a time, back in the sixties, when commenting-out code might have been useful. But we've had good source code control systems for a very long time now. Those systems will remember the code for us. We don't have to comment it out any more. Just delete the code. We won't lose it. Promise.

To be successful as a B requires: 1.? Ownership or control of systems, and 2.? The ability to lead people.

When I ask the classes I teach, How many of you can cook a better hamburger than McDonald's? almost all the students raise their hands. I then ask, So if most of you cook a better hamburger, how come McDonald's makes more money than you? The answer is obvious: McDonald's is excellent at business systems. The reason so many talented people are poor is because they focus on building a better hamburger and know little to nothing about business systems.

1.? Ownership or control of systems, and 2.? The ability to lead people.

Robert asks his students how many of them can make a better hamburger than McDonald's. Most raise their hands. But the reason McDonald's is making millions and they aren't is because McDonald's is excellent at business systems.

When I ask the classes I teach, "How many of you can cook a better hamburger than McDonald's?" almost all the students raise their hands. I then ask, "So if most of you can cook a better hamburger, how come McDonald's makes more money than you?" The answer is obvious: McDonald's is excellent at business systems.

The answer is obvious: McDonald's is excellent at business systems. The reason so many talented people are poor is because they focus on building a better hamburger and know little to nothing about business systems.

My rich dad taught me about systems and how to be a leader of people, not a manager of people.

The main management skills needed for success are: 1) Management of cash flow, 2) Management of systems, and 3) Management of people. And the most important specialized skills are sales and marketing. Communication skills such as writing, speaking, and negotiating are crucial to a life of success.

The main management skills needed for success are: 1.?Management of cash flow 2.?Management of systems 3.?Management of people