Quotes About System

I give money to everybody, even the Clintons, because that's how the system works," Trump said in 2016. Those might have been the most honest words ever to come out of his mouth.

Markets need rules for determining the degree to which economic power can be concentrated without damaging the system.

Romney is right: free enterprise is on trial. But he's wrong about the question at issue in that trial. It's not whether America will continue to reward risk taking. It's whether an economic system can survive when those at the top get giant rewards no matter how badly they screw up while the rest of us get screwed no matter how hard we work.

First, forget politics as you've come to see it as electoral contests between Democrats and Republicans. Think power. The underlying contest is between a small minority who have gained power over the system and the vast majority who have little or none.

It is no great feat for an economy to create a large number of very-low-wage jobs. Slavery, after all, was a full employment system.

Duplication is the primary enemy of a well-designed system. It represents additional work, additional risk, and additional unnecessary complexity.

The unit tests are documents. They describe the lowest-level design of the system.

Every system is built from a domain-specific language designed by the programmers to describe that system. Functions are the verbs of that language, and classes are the nouns.

A system that is comprehensively tested and passes all of its tests all of the time is a testable system. That's an obvious statement, but an important one. Systems that aren't testable aren't verifiable. Arguably, a system that cannot be verified should never be deployed.

What if the decisions have already been made by someone else? What if your company has made a commitment to a certain database, or a certain web server, or a certain framework? A good architect pretends that the decision has not been made, and shapes the system such that those decisions can still be deferred or changed for as long as possible. A good architect maximizes the number of decisions not made.

A use case is a description of the way that an automated system is used. It specifies the input to be provided by the user, the output to be returned to the user, and the processing steps involved in producing that output. A use case describes application-specific business rules as opposed to the Critical Business Rules within the Entities.

The goal of software architecture is to minimize the human resources required to build and maintain the required system.

Good software systems begin with clean code. On the one hand, if the bricks aren't well made, the architecture of the building doesn't matter much. On the other hand, you can make a substantial mess with well-made bricks. This is where the SOLID principles come in.

Architecture represents the significant design decisions that shape a system, where significant is measured by cost of change. —Grady Booch

It is the volatile concrete elements of our system that we want to avoid depending on. Those are the modules that we are actively developing, and that are undergoing frequent change.

Recall that the goal of an architect is to minimize the human resources required to build and maintain the required system.

Which kinds of decisions are premature? Decisions that have nothing to do with the business requirements—the use cases—of the system.

The architecture of a system is defined by a set of software components and the boundaries that separate them.

The component structure cannot be designed from the top down. It is not one of the first things about the system that is designed, but rather evolves as the system grows and changes.

the history of software development technology is the story of how to conveniently create plugins to establish a scalable and maintainable system architecture.

Run with More Threads Than Processors Things happen when the system switches between tasks. To encourage task swapping, run with more threads than processors or cores. The more frequently your tasks swap, the more likely you'll encounter code that is missing a critical section or causes deadlock.

In an ideal system, we incorporate new features by extending the system, not by making modifications to existing code.

Components are the units of deployment. They are the smallest entities that can be deployed as part of a system.

The architecture of a software system is the shape given to that system by those who build it. The form of that shape is in the division of that system into components, the arrangement of those components, and the ways in which those components communicate with each other.