This article compiles 75 concise Python coding recommendations covering style, idioms, core language features, standard libraries, design patterns, internal mechanisms, tooling, and performance optimization to help developers write cleaner, more maintainable, and efficient Python code.
The article outlines frequent pitfalls in Java API design—such as inconsistent return formats, neglecting error cases, irrelevant or overly complex parameters, and missing essential response data—and advocates using a standardized ResultBean to improve readability, AOP integration, and automated testing.
This article explains the importance of establishing personal PHP coding standards, covering benefits such as increased efficiency, readability, professionalism, and team collaboration, and provides detailed guidelines on file and folder naming, class and method conventions, indentation, comment styles, directory structure, and overall code style best practices.
Understanding and applying solid methodologies—such as design patterns, coding standards, and domain‑driven design—constitutes the core of software development best practices, helping programmers evolve from “wild” coders to professionals who write clean, maintainable code and continuously improve through disciplined practice.
Learn ten practical techniques—from effective commenting and consistent indentation to avoiding redundant comments, grouping code, naming conventions, applying the DRY principle, limiting nesting and line length, and organizing files—to dramatically improve the readability and maintainability of your code in any project.
Alibaba unveiled its Alibaba Java Development Specification (P3C) scanning plugin at the Hangzhou Cloud Expo, detailing its automated IDE checks, multi‑level issue reporting, batch fixes, installation steps for IDEA and Eclipse, and its ambition to become a global open‑source coding‑standard.
This article presents a detailed roadmap for aspiring front‑end engineers, covering essential fundamentals, design principles, development techniques, networking basics, server‑side knowledge, database skills, and soft‑skill practices, while providing practical code examples and resource recommendations.
This article presents thirty practical Java coding guidelines covering naming conventions, class design, method granularity, encapsulation, documentation, error handling, and performance considerations to help developers produce clean, robust, and maintainable software.
This article outlines ten crucial Java programming best‑practice rules—ranging from adding comments and avoiding hard‑coding to proper GUI design and unit testing—to help developers write more readable, maintainable, and high‑performance code.
This article explains why using a return statement inside a Java finally block should be avoided, illustrating how it suppresses exceptions and overrides earlier returns, and cites the Java Language Specification and JVM behavior to highlight the risks for developers.
The Alibaba Java Development Manual, now in its 1.2.0 version, offers a comprehensive, industry‑tested coding standard that covers layout, examples, rule corrections, and new content, aiming to boost code quality, development efficiency, and future international adoption.
This article provides a comprehensive English interpretation of Alibaba’s Java Development Manual, detailing mandatory and recommended naming conventions, constant definitions, formatting rules, OOP guidelines, collection handling, concurrency practices, control statements, and comment standards, all illustrated with clear code examples and practical explanations.
This guide presents a comprehensive, step‑by‑step overview of Python coding standards—including indentation, line length, documentation order, spacing, comments, naming conventions, and practical coding tips—helping developers write clear, maintainable, and PEP8‑compliant code.
This article presents practical JavaScript guidelines for naming variables, structuring functions, and avoiding common pitfalls, illustrating each bad pattern with concise code examples and showing the improved, more readable alternatives to help developers write cleaner, maintainable code.
This discussion post examines whether code should be commented, citing the book *Refactoring* and emphasizing that needing comments often signals the need for refactoring, while good variable names can serve as implicit documentation, and stresses the importance of clear interface comments.
This guide summarizes key resources on functional programming, performance optimization, testing strategies, and coding standards, showing how mastering these four areas can transform any Python programmer into a highly effective and sought‑after developer.
The article argues that comments often degrade code readability, identifies two common comment‑related problems—poor naming and overly long methods—and proposes a zero‑comment approach that relies on accurate naming, short methods, and self‑describing code, illustrated with C# examples.
This article outlines practical PHP coding standards—including line breaks, spacing, naming conventions, PSR guidelines, and useful habits like method‑chaining layout and array formatting—to help developers write cleaner, more maintainable backend code.
The article explains why developers need to understand operations—covering resource usage, fault handling, platform basics, and essential ops tools—so they can write maintainable code, avoid common pitfalls, and collaborate effectively with ops teams for reliable, high‑performance services.
This article explains why consistent PHP coding standards—covering line breaks, spacing, naming, and habits like method chaining and array formatting—are essential for readable, maintainable code, and offers practical examples and tools to enforce them across a development team.
The author recounts how strict coding standards at Google transformed his view, showing that uniform indentation, naming, and comment styles dramatically improve code readability, speed up understanding across teams, and outweigh common objections about creativity, flexibility, or perceived waste of time.
The article presents a comprehensive philosophy on software development, emphasizing the importance of repeatedly refining code, structuring it elegantly, modularizing with clear functions, avoiding unnecessary comments, and adopting simple, intuitive practices to improve readability and maintainability across any programming language.
This guide explains twelve practical principles—from declaring a proper DOCTYPE and using UTF‑8 encoding to externalizing CSS/JS, correct nesting, meaningful naming, and validating markup—that help developers write clean, maintainable, and standards‑compliant HTML code.
The article argues that strict coding standards often hinder creativity and teamwork, explaining why the author abandoned them in favor of trusting developers' judgment and focusing on results rather than imposed rules.
The article argues that without clear evaluation standards, software architecture debates become subjective, and proposes using the achievement of the architect's design goals—especially maintainability—as the primary metric for judging a good architecture.
This article recounts how Tencent’s advertising team introduced and scaled a rigorous code review process—starting with the Rietveld system, adopting Google C++ coding style, and establishing metrics and ownership—to improve code quality, knowledge sharing, and engineering efficiency across multiple departments.
