📖 WIPIVERSE

🔍 Currently registered entries: 91,214건

Common Sense (Benn and Hood book)

Common Sense is a book by Paul Bennun and Chris Hood, published in 1998. It explores the application of practical reasoning and judgement to software development. Rather than focusing on formal methodologies or specific technologies, the book emphasizes the importance of critical thinking, pragmatism, and experience in solving real-world software engineering problems.

The central theme revolves around using "common sense" – defined as sound, practical judgment concerning everyday matters, or a basic ability to perceive, understand, and judge things that are shared by (i.e., common to) nearly all people – to navigate the complexities of software projects. It encourages readers to question assumptions, consider alternatives, and make informed decisions based on the specific context of their work.

Key topics covered include:

  • Requirements analysis: Understanding the actual needs of the users and stakeholders, and avoiding over-specification or misinterpretation.
  • Design: Creating simple, maintainable, and understandable solutions that meet the requirements without unnecessary complexity.
  • Coding: Writing clear, concise, and well-documented code that is easy to test and debug.
  • Testing: Employing a variety of testing techniques to identify and fix defects early in the development cycle.
  • Project management: Applying realistic planning and scheduling, managing risks effectively, and communicating clearly with the team.
  • Teamwork: Fostering collaboration, sharing knowledge, and resolving conflicts constructively.

The book advocates for a balanced approach to software development, recognizing that no single methodology or tool is universally applicable. It stresses the need for adaptability, flexibility, and a willingness to learn from mistakes. Its intended audience is software developers, project managers, and anyone involved in the creation and maintenance of software systems. Common Sense aims to provide practical guidance and encourage a thoughtful, pragmatic approach to the software development process.