PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

3 Books on Clean Code Every Developer Should Read

hackerone.com | blog | #books | #code-quality | #developer-education | #agile | #clean-code | #software-craftsmanship
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

A reading list of three classic clean code books, including Robert C. Martin's Clean Code and Steve McConnell's Code Complete. Written decades ago, their guidance on maintainable code still holds.
Published
Collected

Related coverage

blog · hackerone.com
Shell Script Pitfalls and ShellCheck Solutions
HackerOne reviews common shell scripting mistakes—unquoted variables, unsafe eval, globbing and word splitting pitfalls—and shows how ShellCheck catches them while teaching safer scripting habits.
blog · hackerone.com
Ensuring Software Documentation Quality with Spelling Linters
Spelling mistakes undermine documentation quality. This overview of spelling linters like cSpell covers custom dictionaries for jargon and CI integration that catch errors early.
blog · hackerone.com
Unraveling Cyclomatic Complexity: A Guide to Simplifying Your Code
Explains cyclomatic complexity, McCabe's 1976 metric counting linearly independent paths through code, how high scores hurt testability and maintainability, and how to simplify tangled functions.
blog · hackerone.com
The Fallacy of Overreliance on Traits in PHP: Unmasking Poor Class Design
Overusing PHP traits papers over weak class design—violating the single responsibility principle, obscuring dependencies, and complicating testing. It contrasts traits with dependency injection.
blog · hackerone.com
Common PHP Pitfalls: Understanding Array Behavior and Comparisons with Python and JavaScript
HackerOne explains PHP's copy-on-write array semantics, which differ from the reference-based arrays of Python and JavaScript and can trip up developers moving between these languages.
blog · hackerone.com
Incremental Changes in Code Reviews: A Strategy for Efficiency and Clarity
HackerOne argues for incremental changes over sweeping updates: small diffs cut reviewer cognitive load, align with Agile, integrate faster, and make error tracking and collaboration easier.
Back