The article argues that code cleanliness—careful naming, clear responsibilities, consistent abstraction levels, and purposeful design patterns—boosts maintainability and delivery efficiency, while warning against over‑formatting, premature abstraction, and needless refactoring of legacy code.
The article explains why Codex needs explicit project rules, distinguishes between collaboration rules in AGENTS.md and command‑permission rules in .codex/rules, and provides concrete examples, templates, and a checklist for writing effective, specific rules that keep Codex aligned with team conventions.
The article examines the efficiency trap of AI‑generated code, introduces the open‑source code‑simplifier tool that preserves functionality while cleaning up code, outlines five design principles, provides installation and usage guidance, shares practical tips, and discusses the industry shift from rapid code generation to fine‑grained code governance.
Layui 3 introduces a component‑library approach for backend and full‑stack developers, detailing its project positioning, native HTML/CSS/JS stack, dual component models, directory layout, coding conventions, naming rules, theme colors, sizing, and contribution guidelines.
This guide outlines comprehensive C coding style rules, covering indentation, naming conventions, whitespace, comments, function prototypes, variable declarations, structures, enums, control flow, macros, and documentation, with clear examples to help developers write clean, maintainable, and consistent code across projects.
This comprehensive guide presents 50 practical Python coding best‑practice rules covering naming, function design, object‑oriented principles, exception handling, code style, and project structure, showing how to write self‑explanatory, reusable, and robust code that stands the test of time and team collaboration.
This guide outlines thirty‑two practical C/C++ coding habits—from proper file headers, indentation, and commenting to error handling, const usage, and avoiding macros pitfalls—aimed at improving code readability, maintainability, and reliability for developers of all levels.
This article presents 45 practical coding tips—from naming conventions and formatting to exception handling, thread safety, and design patterns—illustrated with Java examples and real‑world scenarios, helping developers produce readable, maintainable, and robust code.
This article examines the shortcomings of the previous Cursor IDE rule set, introduces a three‑layer architecture for AI‑assisted coding, defines a standardized rule format and execution protocol, and provides best‑practice guidelines and phased rollout plans to ensure consistent, high‑quality code generation.
This article explores the importance of Java code style guidelines, compares major industry standards such as Google Java Style and Alibaba's conventions, and provides step‑by‑step instructions for configuring IDEs and Maven plugins to enforce consistent, readable code across teams.
This guide outlines practical C coding standards covering clear and concise code, consistent naming conventions for variables, functions, constants, enums, macros, and files, proper header protection, include ordering, inline function usage, and effective commenting to improve readability and maintainability.
This article outlines a three‑layer architecture for enterprise‑level Cursor Rules, explains common, language‑specific, and framework‑specific rule files, provides configuration examples for TypeScript and React, and offers step‑by‑step guidance, templates, and solutions to common adoption challenges.
These comprehensive guidelines cover Pythonic concepts, coding conventions, function design, module organization, library usage, design patterns, internal mechanisms, development tools, performance profiling, and optimization techniques, providing developers with practical advice to write clean, efficient, and maintainable Python code.
This guide outlines Uber's conventions and best practices for writing Go code, covering linting, formatting, interface usage, error handling, concurrency, performance, style, patterns, and code‑checking tools to ensure maintainable, efficient, and idiomatic backend services.
The article explains why comprehensive code comments are essential, outlines nine distinct comment types advocated by Redis creator antirez, and shows how each improves readability, maintenance, and collaboration in software projects.
This guide outlines comprehensive JavaScript coding standards—including naming conventions, strict mode, variable declarations, indentation, semicolons, string usage, spacing, comments, module imports, conditional expressions, async handling, destructuring, error handling, function design, and performance tips—to improve readability, consistency, and maintainability across teams.
This article presents a comprehensive guide to frontend development best practices, covering commit message standards, dependency management, import ordering, naming conventions, lint configuration, CSS property ordering, inline styles, code duplication, magic numbers, pure functions, and component structuring, with concrete examples and recommendations for improving code quality and maintainability.
This guide outlines Webman’s latest development conventions, covering PHP version selection, naming rules, memory-resident processes, logging, routing, deployment, controller design, database queries, security measures, and more to help developers write clean, efficient, and secure code.
Effective code comments fall into nine categories—six recommended types such as function, design, why, teacher, checklist, and guide comments, and three to avoid (trivial, debt, backup)—and using the right kind improves readability, maintenance, and AI‑assisted understanding of software projects.
The article introduces PHP Standard Recommendations (PSR) created by PHP‑FIG, outlines their purpose in improving code quality, and summarizes key standards such as naming conventions, autoloading, coding style, logging, caching, HTTP messages, and dependency injection for backend development.
This document defines comprehensive C language coding standards covering clarity, simplicity, testability, safety, efficiency, and portability, offering concrete principles, rules, and suggestions to guide developers in writing maintainable, reliable, and high‑performance code.
These guidelines detail C++ client-side naming conventions using Hungarian notation, modular and component-based development principles, and comprehensive coding style rules—including variable prefixes, class naming, indentation, brace placement, macro safety, and interface design—to promote readable, maintainable, and robust software.
This article explores the essential competencies, coding standards, risk‑management practices, and collaborative strategies that script developers need to excel in modern digital operations, offering practical guidance on fundamentals, readability, security, logging, deployment, and teamwork.
This article presents a comprehensive collection of Python coding principles, best‑practice suggestions, library usage tips, design‑pattern ideas, internal language mechanisms, tooling recommendations, and performance‑profiling techniques to help developers write clean, efficient, and maintainable Python code.
This article outlines nine common Python mistakes in data‑science projects—such as neglecting virtual environments, overusing notebooks, hard‑coding absolute paths, ignoring warnings, avoiding list comprehensions, missing type hints, writing unreadable pandas chains, disregarding PEP guidelines, and not using coding assistants—providing explanations and code examples to help developers improve code quality and productivity.
The article outlines best practices for backend API design in Java, emphasizing a unified ResultBean response format, consistent interface definitions, proper handling of failure cases, avoidance of inappropriate parameters, and the use of AOP for exception handling and logging to improve code readability and maintainability.
This article presents a comprehensive collection of Python coding principles, conventions, library usage tips, internal mechanisms, tooling recommendations, and performance‑optimization strategies to help developers write clean, efficient, and maintainable Python code.
This guide introduces OpenResty—a high‑performance web platform built on Nginx and Lua—and provides detailed Lua coding conventions, including indentation, spacing, line length, variable naming, array handling, string concatenation, function design, module imports, and error handling to write clean, efficient backend code.
This guide explains how to import, configure, and apply the CheckStyle plugin in IntelliJ IDEA, covering common annotation, formatting, naming, logical, and import‑order issues, and provides step‑by‑step screenshots to help Java developers enforce coding standards efficiently.
The article examines the long‑standing debate between tabs and spaces for code indentation, citing a massive GitHub analysis that shows spaces dominate most languages while Go uniquely enforces tabs, and explains the technical, historical, and practical reasons behind these preferences and how IDEs can enforce consistent styles.
This article summarizes key lessons from 'Clean Code', explaining why maintaining clean, readable Java code boosts productivity, reduces bugs and costs, and detailing practical guidelines for naming, class design, functions, testing, and refactoring to help developers write high‑quality, maintainable software.
This article outlines the three pillars—professional skills, thoughtfulness, and experience techniques—that determine a frontend developer's level, provides concrete coding conventions, naming guidelines, refactoring advice, and product‑analysis strategies, and emphasizes continuous learning and technical‑debt management to accelerate career growth.
This article introduces a DDD scaffolding project, explains its theoretical foundations, presents the layered architecture and generation commands, details coding conventions for each module, and addresses frequent questions and solutions for practical adoption.
This article presents 34 practical Java performance optimization guidelines—ranging from proper use of singletons and static variables to avoiding excessive object creation, leveraging final modifiers, preferring primitives, minimizing synchronization, and employing efficient collections—to help developers write faster, more memory‑efficient code.
This article presents sixteen practical Java coding best‑practice tips—ranging from consistent naming conventions and appropriate data structures to proper resource handling and logging—to help developers write cleaner, more efficient, and more maintainable code.
The article outlines nine frequent code‑quality problems—such as inconsistent naming, overly long functions, missing or outdated comments, poor error handling, lack of reuse or modularity, hard‑coded values, insufficient testing, misguided performance tweaks, security oversights, and weak version‑control practices—and offers practical solutions to address each.
This article outlines ten essential characteristics of high‑quality code—robustness, efficiency, simplicity, brevity, testability, reusability, portability, observability, operational readiness, and scalability—illustrates common bad‑code examples, and explains how thorough requirement analysis, design, testing, and continuous iteration produce maintainable, reliable software.
This guide presents 21 practical SQL habits covering performance tuning, safe data manipulation, and coding standards—such as using EXPLAIN, adding LIMIT to deletes, documenting tables, consistent formatting, proper indexing, and transaction handling—to help developers write more efficient, reliable, and maintainable queries.
This article presents 45 practical Java coding guidelines covering naming conventions, formatting, commenting, method extraction, error handling, thread safety, design patterns, database access, and many other best‑practice techniques to help developers write cleaner, more maintainable backend code.
The guide defines backend coding standards and best practices, specifying clear naming conventions for classes, methods, variables and constants, enforcing consistent code style via .editorconfig, recommending unchecked exceptions for simpler error handling, promoting structured asynchronous logging with trace IDs, and outlining performance optimizations such as loop refinement, CompletableFuture concurrency, and proper resource management to prevent memory leaks.
The article recounts a production incident where adding a single log line caused a FastJSON NullPointerException, then reconstructs the scenario, analyzes the JavaBeanSerializer source code, presents serialization flowcharts, demonstrates example code with various @JSONField and @JSONType cases, and proposes coding standards to avoid similar serialization pitfalls.
This article shares practical takeaways from the book "Clean Code", covering why messy code hurts productivity, how to name variables and functions better, essential class design rules, error handling, refactoring tips, and a brief look at concurrency and iterative development.
This article presents a comprehensive collection of Python coding principles, idioms, library usage guidelines, design patterns, internal mechanisms, tooling recommendations, and performance profiling techniques to help developers write clean, efficient, and maintainable code.
This article outlines frequent Python pitfalls in data‑science workflows—such as neglecting virtual environments, overusing notebooks, hard‑coding absolute paths, ignoring warnings, avoiding list comprehensions, skipping type hints, writing unreadable pandas chains, not following PEP guidelines, and not using coding assistance tools—and provides practical solutions to improve code quality and productivity.
This article compiles 45 practical Java coding tips—from naming conventions and formatting to exception handling, thread safety, design patterns, and refactoring strategies—aimed at improving readability, maintainability, and performance of existing codebases while preventing common pitfalls.
This comprehensive guide outlines front‑end development standards—including naming conventions, technology‑stack choices, programming rules, Git workflow, BFF design, front‑back collaboration, IDE settings, testing strategies, and documentation—to improve code maintainability, team efficiency, and project quality.
This article explains essential Java exception‑handling techniques, including cleaning resources in finally blocks or using try‑with‑resources, declaring specific exceptions, documenting throws clauses, providing descriptive messages, catching the most specific exceptions first, avoiding catching Throwable, not ignoring exceptions, and correctly wrapping exceptions without losing original causes.
This article compiles fifty practical Java performance‑tuning recommendations—ranging from judicious use of singletons and static variables to efficient collection handling, memory management, and low‑level optimizations—illustrated with code examples and clear explanations to help developers write faster, leaner Java applications.
This article compiles a curated list of major C and C++ security and coding guidelines—including 360 Safe Rules, Tencent Security Guide, Huawei Secure Coding Specification, Google C++ Style Guide, C++ Core Guidelines, SEI CERT, MISRA, and High Integrity C++—providing brief descriptions and direct repository links for each.
This document presents Ant Financial's comprehensive coding standards covering concurrency control, idempotency, state management, object handling, SQL practices, time handling, exception safety, code quality, architecture design, middleware usage, data quality, production change procedures, emergency response, and client‑frontend considerations to ensure robust, secure, and maintainable backend systems.
This article reviews Alibaba’s Java Development Manual, highlights the latest Huangshan edition’s 11 new coding and design rules—including enum immutability, NPE‑prone ternary usage, security checks, and database practices—while providing concrete code examples and practical insights for Java engineers.
This article explains the essential technical knowledge, resume strategies, interview expectations, and personal development habits that students need to master in order to obtain competitive computer science internships at top tech companies.
This guide explains the importance of shell coding standards, outlines core principles such as correctness, readability and maintainability, defines mandatory and optional rules for file naming, indentation, comments, variable handling, control structures, error handling, and provides concrete examples and best‑practice recommendations for Bash scripts.
The article explains why readable code matters, shows a messy JavaScript example, lists common readability problems, and provides concrete guidelines—consistent style, meaningful naming, proper comments, small files, shallow nesting—along with tooling tips such as ESLint, Standard Style, husky and lint‑staged to enforce them.
This guide outlines comprehensive shell scripting standards—including why they matter, core principles, file naming, encoding, line length, indentation, naming conventions, comment rules, error handling, and best‑practice patterns—to improve readability, maintainability, and consistency across Bash scripts in production environments.
This article shares ten practical habits for developers, from consulting official documentation and thorough testing before delivery to effective logging, mastering Git, prioritizing functional implementation, managing requirements, proactively solving project issues, allocating buffer time, hands‑on learning, and improving English for better access to technical resources.
This article presents a set of coding "military rules" covering topics such as avoiding magic numbers, limiting method parameters, proper resource release, specific exception handling, and precise arithmetic, followed by practical development efficiency tips and resource links for further learning.
This article presents a comprehensive guide to writing more standardized Java code, covering topics such as avoiding "1=1" in MyBatis, iterating Map entrySet, pre‑sizing collections, using StringBuilder, preferring Set for contains checks, proper static initialization, removing unused variables, shielding utility constructors, eliminating redundant exception handling, using String.valueOf, avoiding BigDecimal(double), returning empty collections instead of null, safe equals usage, immutable enum fields, and correctly escaping regex in String.split, each illustrated with clear code examples.
This article presents a comprehensive set of Java coding best‑practice guidelines—ranging from MyBatis query writing, efficient Map iteration, collection handling, StringBuilder usage, to proper enum design and exception handling—each illustrated with clear anti‑pattern and correct‑pattern code examples.
This article discusses the challenges faced by frontend developers in startup companies and offers practical solutions such as coding standards, design guidelines, component libraries, documentation, project infrastructure, collaboration processes, and team culture to improve professionalism, coordination, and productivity.
This article outlines essential Java exception‑handling best practices, covering resource cleanup with finally or try‑with‑resources, declaring specific exceptions, documenting throws clauses, providing descriptive messages, catching the most specific exceptions first, avoiding catching Throwable, never ignoring or double‑logging exceptions, and correctly wrapping exceptions without losing the original cause.
This comprehensive guide translates Google's Python style guide into clear English, covering everything from naming conventions and imports to docstrings, type annotations, and best practices for functions, classes, and modules, helping developers write clean, consistent, and maintainable Python code.
This guide explains why comments are essential for code readability, outlines various comment styles for C/C++—including file, function, variable, spelling, and TODO comments—and provides concrete examples and best‑practice recommendations to help developers write clear, maintainable code.
This article explains why comments are essential for code readability, outlines consistent comment styles, details file, function, variable, spelling, and TODO annotations, and provides practical examples to help developers write clear, maintainable C/C++ documentation.
This article explains practical code quality evaluation standards—coding conventions, readability, maintainability, duplication, and testability—and introduces the five dimensions used by Iceworks Doctor to score projects, helping teams adopt consistent, high‑quality coding practices.
This article presents a comprehensive set of guidelines for writing clean, maintainable, and efficient Bash/Shell scripts, covering shebang usage, comments, parameter validation, variable handling, indentation, naming, encoding, permissions, logging, security, parallel execution, and tooling such as ShellCheck.
The article outlines practical guidelines for naming variables and methods—emphasizing clear intent, avoiding misleading or abbreviated names, leveraging IDE autocomplete, ensuring searchability, and maintaining consistent conventions—to improve code readability, maintainability, and overall software quality.
This article presents a collection of typical Java coding mistakes—such as using "where 1=1" in MyBatis, iterating maps inefficiently, neglecting Collection.isEmpty, improper collection initialization, string concatenation in loops, and more—along with clear, performance‑oriented alternatives and code examples to help developers write cleaner, safer, and faster backend code.
This article examines common pitfalls in code quality, testing, and development efficiency, analyzes their root causes, and proposes concrete, actionable solutions such as performance optimization, stricter coding standards, regular code reviews, improved testing practices, and enhanced team collaboration to boost overall software project success.
This article outlines practical Java coding conventions, explains the importance of automated style checking with Checkstyle, and provides a comprehensive list of development best‑practice tips ranging from naming rules and documentation to tooling, hardware setup, and continuous learning habits.
At Meituan, leaders stress that mastering technical fundamentals—such as coding conventions, design patterns, and testing—through continuous, high‑standard practice transforms ordinary programmers into efficient, maintainable, and scalable engineers, driving higher quality delivery and long‑term value for the business.
This guide explains the importance of shell script coding standards, outlines core principles such as correctness, readability, maintainability, and consistency, and provides detailed recommendations on file naming, encoding, line length, indentation, comments, testing, and safe use of commands to improve script quality and reduce maintenance costs.
This article presents the complete Google Java Style Guide, covering terminology, file naming, encoding, whitespace, braces, line length, import ordering, class structure, naming conventions for packages, classes, methods, constants, variables, type parameters, and Javadoc formatting, providing practical coding tips for Java developers.
This article explains nine essential best‑practice guidelines for handling exceptions in Java, covering resource cleanup, specific exception types, documentation, informative messages, catch ordering, avoiding Throwable, proper logging, and exception wrapping to improve code readability and reliability.
The author reviews the newly released Alibaba Java Development Manual (Taishan edition), highlighting 34 new mandatory rules and 90 revisions, and explains how each guideline—from array syntax to monetary storage and concurrency locking—helps developers write cleaner, safer, and more maintainable backend Java code.
This article explains why maintainable JavaScript is essential for modern web applications and provides concrete guidelines on coding standards, readability, naming, type transparency, loose coupling, and coding conventions such as respecting object ownership, avoiding globals, and using constants.
This article introduces the highlights of the latest (Taishan) edition of Alibaba’s Java Development Manual, outlines new OOP, date‑time, collection, SQL, error‑code and security conventions, and provides a one‑click download link for the complete collection of all seven historic versions.
This article compiles essential readings on Python programming, covering functional programming, performance optimization, testing practices, and coding standards to help developers become proficient and write high‑quality, maintainable code.
This guide consolidates essential shell scripting conventions—including shebang usage, comprehensive commenting, parameter validation, variable handling, indentation, naming, encoding, permission settings, logging, password safety, line continuation, code brevity, quoting, main‑function patterns, scope control, indirect references, heredocs, path resolution, parallel execution, and static analysis with ShellCheck—to help developers write readable, maintainable, and performant scripts.
The article explores how disciplined Code Review fosters better software quality, emphasizing that every line of code should have purpose, encouraging concise, well‑named, and well‑documented code, while highlighting common pitfalls such as unnecessary complexity, poor exception handling, and scattered constants.
This guide presents the complete Google Java style specification, covering file naming, UTF‑8 encoding, whitespace rules, brace placement, indentation, import ordering, class structure, naming conventions, formatting details, comment styles, Javadoc requirements, and practical coding recommendations for clean, maintainable Java code.
The article explains how limiting functions to roughly 24 lines and keeping each line under 80 characters improves code readability, aligns with human memory limits, and works across languages, while offering practical tips, examples, and tooling advice for developers.
This article presents the full Google Java Style Guide, detailing file naming, UTF‑8 encoding, whitespace rules, brace placement, import ordering, naming conventions for packages, classes, methods, constants, and Javadoc formatting, with numerous code examples illustrating each rule.
This article presents comprehensive Java coding standards—including naming conventions, Javadoc documentation, and the use of CheckStyle for automated style checking—along with a list of practical development habits to improve code quality, maintainability, and productivity.
This article presents a concise set of Python coding conventions and practical performance‑enhancing techniques, covering naming, data structures, variable scope, idiomatic expressions, loop optimizations, and recommendations for CPU‑intensive tasks to write faster, cleaner code.
The article explains Alibaba's Java Development Manual rules—covering logging APIs, collection initialization, foreach loop modifications, static SimpleDateFormat, string concatenation in loops, serialVersionUID handling, subList usage, inheritance, isSuccess naming, COUNT(*) versus COUNT(col), and thread‑pool creation—providing the rationale behind each prohibition for safer, more efficient backend Java code.
This tutorial explains how to build a custom PHP_CodeSniffer standard that forbids the use of hash (#) for single‑line comments, covering directory setup, rule implementation in PHP, detailed code walkthrough, execution commands, and interpreting the generated XML report.
The article outlines essential coding guidelines that emphasize optimizing code for readers rather than authors, keeping rules concise, valuing standards without fanaticism, ensuring consistency, providing clear cues for rare cases, and avoiding clever but hard‑to‑maintain constructs.
This article presents a series of Java function coding guidelines—including using primitive types for parameters and return values, avoiding null arrays or lists, encapsulating many parameters into objects, replacing anonymous inner classes with functions, simplifying control flow, and employing temporary variables—to improve code readability, maintainability, and robustness.
The article outlines Java function best practices, recommending primitive types for parameters and returns, returning empty collections instead of null, grouping many arguments into parameter objects, replacing anonymous classes with named methods, using early returns, temporary variables, and limiting parameters to those truly required.
The updated Java Development Handbook, originating from Alibaba's internal guidelines and now a global standard, introduces 21 new rules, revises 112 descriptions, and enhances examples across seven dimensions including coding conventions, exception logging, unit testing, security, MySQL, engineering, and design, offering developers fresh insights.
The latest Java Development Handbook introduces 21 new coding rules, revises over a hundred guidelines, and adds clearer examples on lock handling, switch‑null checks, floating‑point comparisons, collection conversions, and guard statements, while inviting developers to download the free PDF and join a live discussion.
The newly released Java Development Handbook introduces three major upgrades—21 new coding rules, over a hundred revisions, and richer examples—while offering practical guidance on lock handling, switch NPE avoidance, floating‑point comparisons, guard statements, and other common Java pitfalls, all available for free download.
This guide consolidates best‑practice conventions for writing readable, maintainable, and efficient shell scripts, covering shebang usage, commenting, parameter validation, variable naming, indentation, quoting, function structuring, scope handling, heredocs, path resolution, performance tricks, parallel execution, and static analysis with ShellCheck.
This document defines the complete Google Java Style Guide, detailing file naming, structure, formatting, naming conventions, and best‑practice recommendations—including whitespace, braces, imports, annotations, Javadoc, and exception handling—to ensure Java source files conform to Google’s coding standards.
This article presents the complete Google Java Style Guide, detailing terminology, file naming, source file structure, whitespace handling, brace placement, line‑length limits, import ordering, naming conventions, coding practices, and Javadoc requirements, providing concrete examples and tips for writing consistent, readable Java code.
A 2013 developer poll revealed that naming functions and variables is the most challenging task for programmers, leading to a detailed guide on common naming styles, the ideal of "seeing the function by its name," and practical rules with code examples to improve function naming across languages.
This article gathers subtle yet frequent anti‑patterns that new Python developers encounter—misusing range, avoiding list comprehensions, overlooking set/dict look‑ups, variable‑scope surprises, and PEP8 style rules—and offers clear, practical alternatives to write cleaner, faster, and more maintainable code.
This article outlines eight actionable strategies—including investing in education, leveraging existing libraries, mastering data structures, using powerful IDEs, writing clean code, continuous learning, disciplined planning, and humility—to help programmers become more outstanding in their careers.
The article outlines essential Java coding standards and best‑practice guidelines—including naming conventions, documentation comments, use of Checkstyle for automated style enforcement, and general development habits such as meaningful variable names, avoiding duplicate code, and maintaining a clean, well‑organized development environment.
