March 2015 Summaries

Seven programming books have stood the test of time and are considered classics in the industry. `The Mythical Man-Month` by Frederick Brooks provides essential insight into managing complex projects, while `The Art of Computer Programming` by Donald Knuth offers a comprehensive coverage of computer programs and their writing. `Introduction to Algorithms` by Thomas Cormen et al. provides a clear and rigorous explanation of algorithms in computer science. The book `Code: The Hidden Language of Computer Hardware and Software` by Charles Petzold aims to demystify the connection between code and underlying hardware, while `Working Effectively with Legacy Code` by Michael Feathers helps developers interact with older code to produce better applications. Peopleware: Productive Projects and Teams by Tom DeMarco and Timothy Lister emphasizes that applications are about people, not technology, and provides insights into managing teams. The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt and David Thomas explains the difference between skilled and average programmers and offers tips for improving coding practice. These books have been widely used in college courses and remain relevant today.

Part three of a series on "Coding by the Book" highlights seven classic programming books that have remained influential over time, offering insights for both new and experienced programmers. These include "The Mythical Man-Month" by Frederick Brooks, Jr., known for its timeless advice on managing complex projects, and Donald Knuth's "The Art of Computer Programming," an encyclopedic resource on the development of modern computer programs and algorithms. "Introduction to Algorithms" by Cormen, Leiserson, Rivest, and Stein provides a concise exploration of algorithms in computer science. Charles Petzold's "Code: The Hidden Language of Computer Hardware and Software" demystifies the connection between code and hardware, while Michael Feathers' "Working Effectively with Legacy Code" offers guidance on improving and understanding older codebases. "Peopleware" by Tom DeMarco and Timothy Lister emphasizes the importance of team management in application development, and "The Pragmatic Programmer" by Andrew Hunt and David Thomas provides practical tips for advancing from a basic coder to a master programmer. Written by John Paul Mueller, the post underscores the relevance of these books in the evolving field of programming, while also clarifying that the views expressed are personal and not necessarily aligned with New Relic's commercial solutions.

Many people who want to learn coding still rely on books as a resource, and for good reason - books can provide comprehensive explanations and sample code that can help you learn just about anything. To get the most out of your book-learning experience, it's essential to read thoroughly, focus on understanding the material, download and work with the source code, single-step through examples using a debugger, and experiment with the code to master it. By following these techniques, you can optimize the learning process and reach key milestones such as understanding language basics, performing specific tasks, and building simple applications. With persistence and practice, you can develop the skills needed to become a proficient programmer.

Learning to code effectively from books involves several strategic approaches, as highlighted in a blog post by John Paul Mueller, an experienced author and technical editor. He suggests that while there are numerous ways to learn programming today, books remain a valuable resource for in-depth understanding and reference. To optimize learning from programming books, it is crucial to read thoroughly, focusing on both the explanatory material and coding examples. Attention and focus are essential, as is downloading and experimenting with provided source code to reinforce learning. Using tools like debuggers to step through code examples can deepen understanding by revealing how applications operate at a fundamental level. Mueller also emphasizes experimenting with the code to grasp the language's full functionality, gradually leading to the ability to create original applications. Achieving proficiency in a programming language involves reaching key milestones, such as mastering language basics, understanding specific tasks, and building progressively complex applications. These strategies, combined with consistent practice, can help learners effectively use books to reach a level of skill desired by employers in the software development industry.

This post is first in a series we call "Coding by the Book." Its companion posts are 5 Tips for Learning How to Program From a Book and The 7 Books Every Software Developer Should Read. Yes, it’s true: dead trees can still be a great resource for learning how to write code or sharpening your skills as a developer. The best place to start assessing a programming book is in the table of contents, where specific topics should appear. Next, scan through chapters to see how they're organized and if multiple approaches are offered. Check out section introductions for signs of fluff or lack of detail. A good index is essential for finding relevant information. When buying a book, avoid relying on title or cover alone, as this can lead to poor choices. Look for reviews from reputable sources, but be aware that opinions may vary and some reviews may not reflect actual reading experience. Choose books based on the value they offer, not just the publisher's reputation. Finally, beware of bestsellers, as marketing dollars can influence rankings rather than quality or applicability.

In the first installment of the "Coding by the Book" series, John Paul Mueller highlights the enduring value of books for learning programming and improving development skills, while offering guidance on selecting the right ones. He advises examining the table of contents to ensure relevant topics are covered, evaluating the organization and depth of chapters, and checking for a comprehensive index. Mueller also stresses the importance of considering the author's expertise and warns against choosing books based solely on titles, covers, publisher reputation, or bestseller status, as these factors do not necessarily guarantee quality. Instead, he suggests using personal judgment and gathering information from reviews, while being cautious of potentially biased opinions.