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

3 Development Anti-Patterns Disguised as Best Practices

hackerone.com | blog | #best-practices | #testing | #software-engineering | #dry | #anti-patterns | #database-design
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Albert Row challenges three 'best practices': blind code reuse, never duplicating data, and strict DRY, arguing denormalization and duplication in tests are sometimes the right engineering call.
Published
Collected

Related coverage

blog · hackerone.com
The Discipline of De-Duping Code
PullRequest reviewer Alvin Lee argues code de-duplication is a discipline rather than a line-count exercise: DRY habits make code easier to debug, maintain, and modify over time.
blog · hackerone.com
Common Best Practices for Cutting Build Times
Practical ways to cut build times: fail builds fast, fix flaky tests, optimize hotspots surfaced by coverage data, run only relevant tests, and prune low-value test cases.
blog · blog.trailofbits.com
The Tao of Continuous Integration
Brittle, slow, flaky CI erodes development velocity. This essay argues CI needs a clear purpose, examining trivial tests, unreliable runs, and coverage theater, and how to build CI that earns trust.
blog · hackerone.com
Evaluating and Choosing Between Monorepo vs. Polyrepo Approaches for Code Management
Compares monorepo and polyrepo strategies: centralized dependencies and atomic cross-project refactoring versus finer access control, independent versioning, and CI scalability.
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
Setting Up CI GitHub Workflows for a New Python Project
A tutorial on setting up GitHub Actions CI for new Python projects: automating linting, testing, and security checks on every push to catch issues early and enforce a consistent quality bar.
Back