0 views collected around this technical thread.
Learn why organizing Python code with functions, modules, and packages is essential for maintainable, scalable projects, and follow step‑by‑step examples that cover basic syntax, practical tips, package structures, dynamic imports, and a hands‑on mini‑project to build your own utility toolkit.
This article explains the fundamentals of Python modularization, covering basic concepts, various import styles, practical use‑case examples, and best‑practice guidelines such as avoiding circular dependencies and using clear package structures to improve code maintainability and scalability.
This article explains why import statements can fill an entire file, examines the problems caused by excessive imports, and presents practical techniques such as module re‑export, require.context, dynamic import, webpack ProvidePlugin, Vite plugins, TypeScript namespaces, aliasing, and Babel plugins to keep import sections concise and maintainable.
The article presents a front‑end API management approach that organizes CRUD functions into unified export statements, object‑oriented modules, and a central mapping table, demonstrating how these patterns improve code readability, maintainability, and development efficiency for large backend‑driven projects.
This article explains how a Python team managing a codebase of nearly 28,000 modules introduced a layered architecture, enforced it with Import Linter, tracked technical debt, and discusses the benefits and drawbacks of such a structure for large‑scale backend development.
This article explains why code architecture matters, compares Clean, Hexagonal, Onion and COLA patterns, describes their layered structures and separation‑of‑concerns principles, and provides a practical Go project layout with concrete code examples to illustrate how each layer interacts.
This article provides an in-depth analysis of Remesh, a frontend framework implementing Domain-Driven Design (DDD) principles, exploring its core concepts, advantages, and practical implementation.
The article argues that complexity in software systems cannot be eliminated but only shifted, emphasizing the inevitability of leaks, the limits of local consequence, and the practical value of layering and eliminating duplication to make frequent changes easier and code more understandable.
This article presents a practical methodology for handling complex business scenarios by combining top‑down process decomposition with bottom‑up domain modeling, illustrating the approach with a retail product onboarding case, code examples, and guidance on capability sinking and model‑driven design.
The article argues that complexity in software systems is unavoidable and must be consciously placed, managed, and reduced through thoughtful architectural decisions, prioritizing high‑frequency changes, eliminating duplication, and accepting that perfect local consequences are impossible.
This article explains the importance of clear responsibility separation in application layering, reviews Alibaba's recommended layer structure, proposes an optimized layering model, and discusses domain model conversions to improve code maintainability, reusability, and team collaboration.
The article presents clean‑architecture best practices for Go microservices built with trpc‑Go, recommending a four‑layer pyramid (gateway, logic, repo, entity), strict dependency inversion, interface‑based injection, gomock testing, centralized JSON configuration, and a three‑phase rollout to replace tangled packages and global imports while avoiding DDD complexity.
This guide explains how to adopt a multi‑project modular architecture for Android apps—distinguishing components from modules, outlining vertical and horizontal design layers, showing ARouter‑based navigation and communication, and detailing a top‑down, bottom‑up migration process used to refactor the vivo official app.
The article thoroughly examines Vue 3’s Composition API, explaining its motivation over the Options API, detailing its function‑based design and TypeScript advantages, addressing concerns about complexity, and offering practical guidance on when and how to adopt it for cleaner, more maintainable component logic.
This article presents a practical methodology for handling complex business logic by combining top‑down process decomposition with bottom‑up domain modeling, illustrating the approach with a detailed product‑on‑sale use case, code examples, and guidance on avoiding over‑reliance on tooling.
This article shares practical guidelines and a detailed directory layout for organizing Go projects, illustrated with the gobox-demo template, covering configuration, source code organization, controller/action separation, service layer structuring, and best‑practice recommendations for clean, maintainable backend development.
This article explains the BEM (Block‑Element‑Modifier) naming convention, why it is needed for style isolation, readability and maintainability, outlines its syntax and common patterns, and provides practical guidelines for page, shared, and local component naming in modern front‑end projects.
This article details the design of a reusable Java backend framework called lyyzoo, covering coding standards, Maven module hierarchy, dependency management, core utility classes, and Spring configuration for web, JPA, and transaction support, providing a comprehensive guide for building enterprise applications.
The article reflects on a decade of programming experience to demystify object‑oriented programming, arguing that OOP should be taught as a practical tool for reducing complexity rather than an abstract doctrine, and discusses how to organize functions into classes, avoid misuse of inheritance and design patterns, and focus on solving real problems.
This article presents a detailed analysis of the evolution from MVC to MVP in Android hotel‑business development, illustrates common pitfalls such as bloated controllers and context loss, introduces Ctrip's extended MVCPI pattern with weakly‑typed IView, Presenter and Interactor components, and provides concrete code examples for each architecture.