Quotes About Discipline

If we all checked-in our code a little cleaner than when we checked it out, the code simply could not rot.

What this team did not realize was that having dirty tests is equivalent to, if not worse than, having no tests.

If you let the tests rot, then your code will rot too. Keep your tests clean.

OO imposes discipline on indirect transfer of control.

Structured programming is discipline imposed upon direct transfer of control.

Object-oriented programming is discipline imposed upon indirect transfer of control.

It is no longer sufficient that every programmer does what is right in their own eyes. Some disciplines, standards, and ethics will come. The decision before us today is whether we programmers will define them for ourselves or have them forced upon us by those who don't know us.

Functional programming is discipline imposed upon variable assignment.

Learning to write clean code is hard work. It requires more than just the knowledge of principles and patterns. You must sweat over it. You must practice it yourself, and watch yourself fail. You must watch others practice it and fail. You must see them stumble and retrace their steps. You must see them agonize over decisions and see the price they pay for making those decisions the wrong way.

The only way to make the deadline—the only way to go fast—is to keep the code as clean as possible at all times.

A craftsman is someone who works quickly, but without rushing, who provides reasonable estimates and meets commitments. A craftsman knows when to say no, but tries hard to say yes. A craftsman is a professional.

To write clean code, you must first write dirty code and then clean it.

Am I suggesting 100% test coverage? No, I'm not suggesting it. I'm demanding it. Every single line of code that you write should be tested. Period.

You should choose a set of simple rules that govern the format of your code, and then you should consistently apply those rules. If you are working on a team, then the team should agree to a single set of formatting rules and all members should comply.

The fact is that making messes is always slower than staying clean, no matter which time scale you are using.

Structured programming imposes discipline on direct transfer of control.

Object-oriented programming imposes discipline on indirect transfer of control.

Functional programming imposes discipline upon assignment.

Each of the paradigms removes capabilities from the programmer. None of them adds new capabilities. Each imposes some kind of extra discipline that is negative in its intent. The paradigms tell us what not to do, more than they tell us what to do.

Ultimately, we can say that mathematics is the discipline of proving provable statements true. Science, in contrast, is the discipline of proving provable statements false.

Clean code is not written by following a set of rules. You don't become a software craftsman by learning a list of heuristics. Professionalism and craftsmanship come from values that drive disciplines.

that the Tenth Party Congress passed a resolution on unity, drafted by Lenin, which banned factions in the party. Reflecting the competition of "platforms" on the trade union issue, which had divided the party in the pre-congress period, it defined factionalism as "the emergence of groups with special platforms and a certain striving to close ranks and create their own group discipline."[485

First, it is essential that you begin with one skill that you can master, and that serves as a foundation for acquiring others. You must avoid at all cost the idea that you can manage learning several skills at a time.

Half of your mastery of power comes from what you do NOT do, what you do not ALLOW yourself to get dragged into.