The Pragmatic Programmer: From Journeyman to Master
Read nontechnical books, too.
David Thomas • The Pragmatic Programmer: From Journeyman to Master
EVERY PIECE OF KNOWLEDGE MUST HAVE A SINGLE, UNAMBIGUOUS, AUTHORITATIVE REPRESENTATION WITHIN A SYSTEM.
David Thomas • The Pragmatic Programmer: From Journeyman to Master
Learn at least one new language every year. Different languages solve the same problems in different ways. By learning several different approaches, you can help broaden your thinking and avoid getting stuck in a rut.
David Thomas • The Pragmatic Programmer: From Journeyman to Master
One broken window, left unrepaired for any substantial length of time, instills in the inhabitants of the building a sense of abandonment—a sense that the powers that be don't care about the building. So another window gets broken.
David Thomas • The Pragmatic Programmer: From Journeyman to Master
Another key to their success is that they take responsibility for everything they do,
David Thomas • The Pragmatic Programmer: From Journeyman to Master
[Ber96] Albert J. Bernstein. Dinosaur Brains: Dealing with All Those Impossible People at Work. Ballantine Books, New York, NY, 1996.
David Thomas • The Pragmatic Programmer: From Journeyman to Master
Plan what you want to say. Write an outline. Then ask yourself, "Does this get across whatever I'm trying to say?" Refine it until it does.
David Thomas • The Pragmatic Programmer: From Journeyman to Master
every decision results in a different version of the future. How many possible futures can your code support?
David Thomas • The Pragmatic Programmer: From Journeyman to Master
Instead of excuses, provide options.