Hi, it’s me again. In this blog, I am going to talk about the pragmatic programmer article. It is a pretty interesting read as a fellow computer scientist and as another person that will work in the same situation.
In this article, it talked about many various things about the pragmatic programmer. From the article, the author’s stance on responsibility seems to be highly demanding. The author believes that responsibility is taken only when it is part of your work. When a mistake or error happened on your part, you should not leave it aside and make excuse about being inavoidable. But instead, find a solution to fix it.
This article surprised me at some moment, such as the story they told. One of the interesting stories is the stone soup story. It has many moral and meaning in it. I am surprise something simple like that can move others. The story talked about three soldiers who made a stone soup and tricked the whole village into making a giant pot soup with different ingredients such as carrot, meat, potato, etc. The message here is that when you work alone on something, it might not work well. However, if everyone works together, the project would work. Sometimes, trickery is a need in teamwork.
There are also moment I disagree with, such as when the article talked about the email case, where the recipient replied with “I’ll get back to you soon”. In that situation, I believe that option might sounds like the recipient care but in fact, that is just giving the sender a hope that they would reply. Hope would not help the sender’s feeling of anxious, the recipient should reply immediately or reject the email, so the sender can decide on doing what next.
After reviewing the article, there are some parts I would like to practice during the group project. For example, viewing the whole picture during the group project. This is important because sometimes group member could stray off from the research topic and ends up not being on the same page. That is why focusing on the whole picture of the project is needed.