Swapnilmj > Swapnilmj's Quotes

“You Can't Write Perfect Software. Did that hurt? It shouldn't. Accept it as an axiom of life. Embrace it. Celebrate it. Because perfect software doesn't exist. No one in the brief history of computing has ever written a piece of perfect software. It's unlikely that you'll be the first. And unless you accept this as a fact, you'll end up wasting time and energy chasing an impossible dream.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“The editor will be an extension of your hand; the keys will sing as they slice their way through text and thought.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“Don't be a slave to history. Don't let existing code dictate future code. All code can be replaced if it is no longer appropriate. Even within one program, don't let what you've already done constrain what you do next -- be ready to refactor... This decision may impact the project schedule. The assumption is that the impact will be less than the cost of /not/ making the change.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“The greatest of all weaknesses is the fear of appearing weak.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“Names are deeply meaningful to your brain, and misleading names add chaos to your code.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“Great software today is often preferable to perfect software tomorrow.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“In an article in the April 1999 CACM, Robert Glass summarizes research that seems to indicate that, while code inspection is effective, conducting reviews in meetings is not.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“Kaizen" is a Japanese term that captures the concept of continuously making many small improvements.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“Tools amplify your talent. The better your tools, and the better you know how to use them, the more productive you can be.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“In some ways, programming is like painting. You start with a blank canvas and certain basic raw materials. You use a combination of science, art, and craft to determine what to do with them. 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. But artists will tell you that all the hard work is ruined if you don't know when to stop. If you add layer upon layer, detail over detail, the painting becomes lost in the paint.”
― Andrew Hunt, The Pragmatic Programmer

“The amount of surprise you feel when something goes wrong is directly proportional to the amount of trust and faith you have in the code being run.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“Programmers are constantly in maintenance mode.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“One hundred years from now, our engineering may seem as archaic as the techniques used by medieval cathedral builders seem to today's civil engineers, while our craftsmanship will still be honored.”
― Andrew Hunt, The Pragmatic Programmer

“Every day, work to refine the skills you have and to add new tools to your repertoire.”
― Andrew Hunt, The Pragmatic Programmer

“Don't leave "broken windows" (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered. If there is insufficient time to fix it properly, then board it up. Perhaps you can comment out the offending code, or display a "Not Implemented" message, or substitute dummy data instead. Take some action to prevent further damage and to show that you're on top of the situation.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“Have you noticed how some project teams are efficient, with everyone knowing what to do and contributing fully, while the members of other teams are constantly bickering and don't seem able to get out of each other's way? Often this is an orthogonality issue. When teams are organized with lots of overlap, members are confused about responsibilities. Every change needs a meeting of the entire team, because any one of them might be affected.”
― Andrew Hunt, The Pragmatic Programmer: From Journeyman to Master

“Entropy is a term from physics that refers to the amount of "disorder" in a system.”
― Andrew Hunt, The Pragmatic Programmer