Quotes About Business

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.

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

Code formatting is important. It is too important to ignore and it is too important to treat religiously. Code formatting is about communication, and communication is the professional developer's first order of business.

To do Agile right, you had to work in pairs, write tests first, refactor, and commit to simple designs. You had to work in short cycles, producing executable output in each. You had to communicate with business on a regular and continuous basis.

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.

The Entity is pure business and nothing else.

The business rules should be the most independent and reusable code in the system.

The dilemma for software developers is that business managers are not equipped to evaluate the importance of architecture. That's what software developers were hired to do. Therefore it is the responsibility of the software development team to assert the importance of architecture over the urgency of features.

ENTITIES Entities encapsulate enterprise-wide Critical Business Rules. An entity can be an object with methods, or it can be a set of data structures and functions. It doesn't matter so long as the entities can be used by many different applications in the enterprise.

For example, maybe you like Spring. Spring is a good dependency injection framework. Maybe you use Spring to auto-wire your dependencies. That's fine, but you should not sprinkle @autowired annotations all throughout your business objects. Your business objects should not know about Spring. Instead, you can use Spring to inject dependencies into your Main component. It's OK for Main to know about Spring since Main is the dirtiest, lowest-level component in the architecture.

Code formatting is about communication, and communication is the professional developer's first order of business.

Premature Precision Both business and programmers are tempted to fall into the trap of premature precision. Business people want to know exactly what they are going to get before they authorize a project. Developers want to know exactly what they are supposed to deliver before they estimate the project. Both sides want a precision that simply cannot be achieved, and are often willing to waste a fortune trying to attain it.

What would happen if you allowed a bug to slip through a module, and it cost your company $10,000? The nonprofessional would shrug his shoulders, say "stuff happens," and start writing the next module. The professional would write the company a check for $10,000!

The problem is that we view estimates in different ways. Business likes to view estimates as commitments. Developers like to view estimates as guesses. The difference is profound.

Perhaps you thought that "getting it working" was the first order of business for a professional developer. I hope by now, however, that this book has disabused you of that idea. The functionality that you create today has a good chance of changing in the next release, but the readability of your code will have a profound effect on all the changes that will ever be made.

And shall I tell you something else, papa, now that we're talking at last? It was fine. I was fine. Because what was I doing, really, that ten million other girls don't do every night, only they don't have the sense to get paid for it? That was decadent. This was business – kapitalism – and it was fine, and it was like you said, I only had one friend: myself.

If we exaggerate the present and future value of the stock market, then as a society we may invest too much in business start-ups and expansions, and too little in infrastructure, education, and other forms of human capital.

In the end, for all of us who strive to achieve, whether in business or in other walks of life, the end of life is a disappointment. The personal pleasure over a lifetime was mostly in the striving and in one's friendships and interactions. The pinnacle of achievement does not bring happiness, but at best the reflection that the striving achieved some benefit for others, unappreciative and unrelated though those others may

Execution is everything. Even if you start a business with the wrong idea or too many competitors, you can out-execute all the better ideas in the right market.

To obtain financial freedom, one must be either a business owner, an investor, or both, generating passive income, particularly on a monthly basis.

nueve de cada diez negocios fracasan, es porque se enfocan en el producto y no en toda la estructura del negocio.

Lo primero que piensan casi todos los empleados cuando les hablo de llegar a ser empresario y echar a andar un negocio o invertir en bienes raíces, es: "¿Y qué tal si cometo un error? ¿Qué pasará si pierdo dinero? ¿Qué pasará si fracaso?" Esta mentalidad es lo que impide que la gente sea rica.

cuando echas a andar tu propio negocio con base en casa, muchos de los gastos que antes eran personales –gastos después de impuestos–, se convierten de inmediato en gastos de negocio antes de impuesto.

Los ricos no trabajan para obtener dinero, sino para adquirir activos que generen flujo de efectivo.