Reading Weeks in School
For the Reading Weeks in School I read a couple of chapters of The Pragmatic Programmer by Andrew Hunt and David Thomas.
Thomas/Hunt writes about what distinguishes Pragmatic Programmers. He writes that it's a special way of approaching problems and their solutions.
Thomas/Hunt has the opinion that learning is a continuous and ongoing process.
Thomas/Hunt believes that the most meaningful points of the pragmatic philosophy are taking responsibility of one’s own actions and taking charge of one's own career. By admitting ignorance or error, and by being honest and direct are the ways to be a professional.
Thomas/Hunt informs that it's non-beneficial to make excuses, that we should make options instead of blaming someone or something else. For example making backups of done work is important.
Thomas/Hunt makes a point that if disorder increases in software it is called software rot, and neglect accelerates the rot faster than any other factor. It is also said that bad designs, wrong decisions and poor code should not be left unrepaired.
Thomas/Hunt explains a term "start-up fatigue" by telling a story about soldiers needing food supplies from villagers where everyone were guarding their resources. According to him people find it easier to join an ongoing success. He continues to say that it's often the accumulation of small things that breaks morale and teams. In the real world however we rarely get truly perfect code but you can discipline yourself to write software that is good enough he says.
Thomas/Hunt thinks that keeping up with releases of work related text like books is a good thing. When you learn new things it makes you more interesting as a worker for companies which need your expertees. Talking to other people will help build your personal network so that would be good as well. But you need to remember to think critically about what you read and hear.
According to what I have read I would recommend this book for anyone interested in computer programming languages.
Hunt, A., & Thomas, D. (1999). The pragmatic programmer: From journeyman to master. Addison-Wesley.
This was a engaging summary of said chapters. However I would have loved to hear your thoughts about todays situation (as this was written in 1999), if it is still up to standard. Overall engaging read for me, thank you!
ReplyDeleteHello, I think a lot of the things the author talks about are quite universal. Continuous learning, not leaving things unrepaired, not making excuses etc. I think a lot of people might benefit from reading, not just computer science students.
ReplyDeleteNice summary! You highlighted the main ideas of The Pragmatic Programmer really clearly, especially about taking responsibility and continuously learning. I also liked your point about software rot and how small issues can add up.
ReplyDeleteYour summary shows how important good habits are in software development. It sounds like the book offers practical advice not just for coding but for building a stronger mindset. Great recommendation!
ReplyDeleteYour summary highlights several key ideas from the book very clearly, especially the focus on responsibility and continuous learning. I found your point about “software rot” interesting, because it really shows how small issues can grow.
ReplyDelete