The Pragmatic Programmer
Ethan Rhodes
CS-221-1: Book Report
October 3, 2017
Body
A Pragmatic Philosophy
The Cat Ate My Source Code A Pragmatic Programmer is distinguished among their peers by attitude, style, and the philosophy of approaching problems and their solution. The Pragmatic Programmer takes responsibility for their work, and isn’t afraid to admit ignorance or error. When they take responsibility for an outcome, they’re willing to be held accountable for it. “The Cat Ate My Source Code” isn’t an acceptable answer for them. You won’t find them blaming someone or something else. Instead of making up various excuses, a Pragmatic Programmer will start providing options for a solution. They accept the fact that it’s up to them to find the solution for their mistake. A solid tip from the chapter is called the Rubber Duck method. This method consists of pondering various questions before presenting them to others. For example, if you’re about to tell your boss something is broken, will they say, “Have you tried…?” by implementing this methodology not only does one save their boss trouble, but they also come closer to resembling a …show more content…
Occasionally people will want to horde their resources and over complicate the situation this is what programmers call start-up fatigue. One might run into start-up fatigue despite knowing what needs completed, and how to proceed with accomplishing it. This is where you can emulate the soldiers in the story. The Pragmatic Programmer approach is ensuring their program is developed where and decide what is reasonable to ask for. Like the stone soup, one can always say “of course, it would be better if we added…” This approach draws people in as they start to ask about adding the functionality you were seeking. People find it easier to rally behind ongoing success if you show them a glimpse of the
Ethan Rhodes
CS-221-1: Book Report
October 3, 2017
Body
A Pragmatic Philosophy
The Cat Ate My Source Code A Pragmatic Programmer is distinguished among their peers by attitude, style, and the philosophy of approaching problems and their solution. The Pragmatic Programmer takes responsibility for their work, and isn’t afraid to admit ignorance or error. When they take responsibility for an outcome, they’re willing to be held accountable for it. “The Cat Ate My Source Code” isn’t an acceptable answer for them. You won’t find them blaming someone or something else. Instead of making up various excuses, a Pragmatic Programmer will start providing options for a solution. They accept the fact that it’s up to them to find the solution for their mistake. A solid tip from the chapter is called the Rubber Duck method. This method consists of pondering various questions before presenting them to others. For example, if you’re about to tell your boss something is broken, will they say, “Have you tried…?” by implementing this methodology not only does one save their boss trouble, but they also come closer to resembling a …show more content…
Occasionally people will want to horde their resources and over complicate the situation this is what programmers call start-up fatigue. One might run into start-up fatigue despite knowing what needs completed, and how to proceed with accomplishing it. This is where you can emulate the soldiers in the story. The Pragmatic Programmer approach is ensuring their program is developed where and decide what is reasonable to ask for. Like the stone soup, one can always say “of course, it would be better if we added…” This approach draws people in as they start to ask about adding the functionality you were seeking. People find it easier to rally behind ongoing success if you show them a glimpse of the