“The Pragmatic Programmer” Is Essential Reading for Software Developers

Among their recommendations:Get really good at a plain text editor like Vim or Emacs (pg. 73)Add some custom commands and configurations to your shell and get fast at using the command line (pg. 77)Use source control, like git, to make rollbacks, collaboration, and sharing easy (pg. 86)Practicing the fundamentals in your coding language(s) of choice, so code flows from your fingertips without thinkingWriting CodeOver 100 pages into the book, and we’re finally ready to start talking about code.The Pragmatic Programmer is the source of many tidbits of coding advice that you’ve probably already heard.The concepts of “lazy” and “shy” code come from the book, writing functions that are strict about what they’ll accept and promise as little as possible in returnBest practices for handling errors and exceptionsWriting clean, thread-safe code that anticipates concurrency for large-scale applicationsCarefully choosing and considering the tradeoffs of how you structure and store dataUsing Big-O notation to estimate algorithm runtimeHow to write good tests that give maximum coverageWhen should you refactor code?.What makes spending time on a refactor worth it?I can’t possibly summarize all the advice the middle 100 pages of the book delivers..It ranges through all aspects of coding, but none of the advice gets too granular or language-specific.This book was written in 1999, but despite changes in technology, most of the recommendations hold up two decades later.Project ManagementWe wrap up the code-specific section of the book, and by now there’s plenty of valuable content to finish the book right here..But Hunt and Thomas don’t stop.There’s still a hundred pages left of valuable project management and planning advice from these veteran developers.Setting expectations and requirements ahead of the projectGetting your team to buy into the pragmatic cultureWriting documentation and communicating with the team and usersThis is the kind of advice that gets more valuable the more projects you’ve worked on..You start to realize how insightful their advice is once you have a history of working on projects that had unclear requirements or bad communication.Constant ImprovementThe Pragmatic Programmer is one of those books you keep on your shelf as a reference..You can refer back to it many times and learn something new from it at different stages of your career.If you’re serious about becoming an expert developer, then this book is a must-read..It’s the kind of book that sets apart people who are good coders from the best of the best.Ideas for how to make this post better?.Comment below, and I’ll add your thoughts into the post.. More details

Leave a Reply