The Pragmatic Programmer Quotes
The Pragmatic Programmer: From Journeyman to Master
by
Andy Hunt23,877 ratings, 4.33 average rating, 1,503 reviews
The Pragmatic Programmer Quotes
Showing 181-210 of 240
“you may not even need to code in order to prototype architecture—you can prototype on a whiteboard, with Post-it notes or index cards.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“Prototyping is a learning experience. Its value lies not in the code produced, but in the lessons learned. That's really the point of prototyping.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“A user interface can be prototyped as a drawing on a whiteboard, as a nonfunctional mock-up drawn with a paint program, or with an interface builder.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“we can build prototypes out of different materials. Post-it notes are great for prototyping dynamic things such as workflow and application logic.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“knowledge isn't stable. It changes—often rapidly.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“As programmers, we collect, organize, maintain, and harness knowledge. We document knowledge in specifications, we make it come alive in running code, and we use it to provide the checks needed during testing.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“Unless you work in a vacuum, you need to be able to communicate. The more effective that communication, the more influential you become.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“There's one technique that you must use if you want people to listen to you: listen to them.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“Make what you're saying relevant in time, as well as in content. Sometimes all it takes is the simple question "Is this a good time to talk about...?”
― The Pragmatic Programmer
― The Pragmatic Programmer
“You're communicating only if you're conveying information.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“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.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“A large part of our day is spent communicating, so we need to do it well.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“we work daily within our teams to advocate our ideas, modify existing practices, and suggest new ones.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“We write code, which communicates our intentions to a machine and documents our thinking for future generations of developers.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“It's not just what you've got, but also how you package it.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“I believe that it is better to be looked over than it is to be overlooked. • Mae West, Belle of the Nineties, 1934”
― The Pragmatic Programmer
― The Pragmatic Programmer
“If you are doing very detailed implementation and coding, read a book on design and architecture. If you are doing high-level design, read a book on coding techniques.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“think critically about what you read and hear. You need to ensure that the knowledge in your portfolio is accurate and unswayed by either vendor or media hype.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“Talking to other people will help build your personal network, and you may surprise yourself by finding solutions to other, unrelated problems along the way.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“The cross-pollination of ideas is important; try to apply the lessons you've learned to your current project.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“The process of learning will expand your thinking, opening you to new possibilities and new ways of doing things.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“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.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“expiring assets.[3] Your knowledge becomes out of date as new techniques, languages, and environments are developed.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“You sketch out an overall shape, paint the underlying environment, then fill in the details. You constantly step back with a critical eye to view what you've done. Every now and then you'll throw a canvas away and start again.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“The scope and quality of the system you produce should be specified as part of that system's requirements.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“the real world just won't let us produce much that's truly perfect, particularly not bug-free software. Time, technology, and temperament all conspire against us.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“Striving to better, oft we mar what's well. • King Lear 1.4”
― The Pragmatic Programmer
― The Pragmatic Programmer
“Don't leave "broken windows" (bad designs, wrong decisions, or poor code) unrepaired.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“There are many factors that can contribute to software rot. The most important one seems to be the psychology, or culture, at work on a project.”
― The Pragmatic Programmer
― The Pragmatic Programmer
“Unfortunately, the laws of thermodynamics guarantee that the entropy in the universe tends toward a maximum.”
― The Pragmatic Programmer
― The Pragmatic Programmer
