Blog Post #2 - gstapes/gstapes.github.io GitHub Wiki

The Pragmatic Programmer Chapter 1 (Reaction?)

To start off with information that I found interesting/new was that before I read about this first chapter is that I had no clue what Pragmatic meant or it had a general message or morals of how to become a better coder. Going forward I found interesting about the chapter was about how to work in groups. When I think about coding it is mostly alone and not really with the direct guidance of someone else. Just like in sports, each person must think of what is best for the team rather than what is best or easiest for themselves for the team to have prolonged success. This has to do with the whole process of coding through the breakthroughs and the mistakes. There are even points of vulnerability in which a person has to admit to their mistakes to the team which is sometimes a hard thing to do. Going forward other than that is that you should always have a back up plan to fix these mistakes or potential mistakes that could appear later. The latter part is more of covering up the team later, so if the code crashes the team won't have to spend time fixing mistakes that shouldn't be there in the first place.