A software engineer explains the pitfalls of organizing code into generic 'utils' modules, using a real-world example of circular dependencies.
Explores common pitfalls in software abstraction like DRY misuse, lasagna code, and util files, offering advice for scalable design.
A quick tip for developers to alphabetize object keys in code to improve readability and efficiency when order isn't important.
The article argues against using barrel files in JavaScript/TypeScript projects, explaining their drawbacks and negative impact on code organization.
An introduction to using Packs (Packwerk) for feature-based code organization in Rails applications as an alternative to Engines.
Argues for naming code components with noun-adjective order (e.g., StreamCreated) instead of adjective-noun for better alphabetical grouping and searchability.
Argues that import path aliasing in JavaScript/TypeScript projects is a band-aid for poor codebase architecture and organization.
A critique and refinement of Onion Architecture, analyzing its challenges and proposing a 'sliced' approach for better code organization.
A consultant outlines six common signs that a software system's architecture lacks visibility and discoverability, hindering developer understanding and maintenance.
A guide to organizing a .NET Dependency Injection container using extension methods for better structure and maintainability.
Argues for organizing code with the most abstract functions first to improve readability and debugging efficiency.
A guide to structuring large-scale React applications using a feature-focused architecture for better scalability and organization.
Discusses the problems with vague module names like 'shared' and 'util' in software architecture and suggests more descriptive alternatives.
Explores methods for enforcing architectural design in modular monoliths to prevent code-model divergence and maintain modularity over time.
Learn 4 essential best practices for writing clean, maintainable, and efficient JavaScript modules, including export strategies and import behavior.
The article argues for co-locating code comments with the relevant code, explaining the maintainability and clarity benefits over separate documentation files.
A guide to using Python decorators for automatic TensorFlow named scopes, improving code organization and TensorBoard visualization.
A software architecture article advocating for organizing code by business features instead of technical layers to improve cohesion and maintainability.
A guide to structuring large Laravel codebases by domain or module, grouping related business logic like contracts and invoicing for better organization.
The article explains the benefits of using a single, large repository (monorepo) for code, citing simplified organization and dependency management.
