This article explains how developers struggling with inconsistent and unclear naming in Java and Vue projects can use a self‑built AI naming assistant—available as a lightweight web app and an IntelliJ IDEA plugin—to instantly generate clean, convention‑compliant identifiers from simple Chinese descriptions.
The article shares the author’s struggle with inconsistent naming in front‑end Vue and back‑end Java code and introduces a self‑built AI‑driven naming tool—available as a lightweight web app and an IntelliJ IDEA plugin—that instantly generates clean, convention‑compliant identifiers.
The article describes the frustration developers face with unclear method and variable names, presents an AI‑driven naming tool with both a web app and an IntelliJ IDEA plugin, and explains how the tool quickly generates clean, convention‑compliant identifiers across front‑end and back‑end languages.
This article presents ten practical Go code‑review guidelines—covering error handling, premature abstraction, concurrency, scope, safety, early returns, file organization, declaration order, semantic naming, and purposeful comments—to help teams write more reliable and maintainable backend code.
This article explains how different Java boolean naming conventions affect JSON serialization across fastjson, Gson, and Jackson, demonstrates the resulting inconsistencies with code examples, and recommends using a plain "success" field with an isSuccess getter to ensure reliable cross‑library behavior.
This article traces the historical reasons why the letter ‘X’ appears in Unix‑related operating system names, explains how Linus Torvalds adopted the name Linux, and reveals the roles of MINIX, Freax, and early contributors in shaping the modern Linux ecosystem.
This article explains why clean code matters and provides practical guidelines on naming, class design, function design, and testing—including principles, refactoring examples, and tool recommendations—to help developers write more readable, maintainable, and robust Java code.
This article explains the concepts of external and internal code beauty, introduces essential frontend tooling such as ESLint, Prettier, Stylelint, husky, lint‑staged, EditorConfig, and CSSComb, and shares practical habits on documentation, naming, and commenting to help developers produce elegant, maintainable code.
This article explains why clear naming is crucial for maintainable software, identifies common pitfalls such as lack of intent, poor thinking, and bad habits, and provides concrete guidelines, examples, and refactorings—especially for Java—to help developers choose expressive, searchable, and consistent identifiers.
This article provides practical, experience‑based naming guidelines for software development, covering precision, readability, abbreviation policies, language‑specific conventions, design‑pattern naming, and a comprehensive code‑term glossary to help developers choose clear and maintainable identifiers.
This article reflects on key insights from Robert Martin’s *Clean Code*, covering the distinction between dirty and clean code, the art of naming, effective commenting, function design principles, and the essential role of testing, offering practical examples and personal reflections for writing more readable, maintainable software.
This article explores the core principles of clean code—including effective naming, purposeful comments, single‑responsibility functions, proper abstraction levels, and essential testing practices—illustrated with concrete code examples and actionable guidelines for writing more readable, maintainable software.
This article distills key lessons from the book "Clean Code", covering expressive naming, purposeful functions, minimal and meaningful comments, and rigorous testing practices, illustrated with concrete code examples to help developers write more readable and maintainable software.
Effective naming in software development, illustrated with real code examples and visual metaphors, transforms ambiguous code into clear, self‑documenting logic, improves readability, reduces errors, and aligns with best practices such as modeling, meaningful differentiation, and consistent style, ultimately enhancing maintainability.
The article explains why English is essential for global codebases, outlines naming conventions for classes and methods, shows common pitfalls with inaccurate translations, and proposes a collaborative glossary to improve readability and maintainability of software projects.
This article explains practical JavaScript naming conventions—covering camelCase, constant capitalization, acronym handling, meaningful and expressive names, verb consistency, boolean naming, and class naming—while providing numerous code examples to illustrate good and bad practices for clearer, maintainable code.
This article explains how abstract thinking underpins software design, illustrates abstraction with visual and code examples, shows the pitfalls of duplicated code and forced casts, and offers practical habits—reading, summarizing, naming, and domain modeling—to strengthen a developer's abstraction skills.
This article explains why clear, meaningful naming is essential for maintainable front‑end code, showcases common bad naming patterns, and provides practical naming rules, conventions, tooling tips, and examples for JavaScript, CSS, and project structures.
This article explores the core principles of clean code—from effective naming and expressive functions to purposeful comments and rigorous testing—illustrating how disciplined practices like meaningful identifiers, single‑responsibility functions, and the FIRST testing criteria can dramatically improve code readability, maintainability, and reliability.
The article examines the recent push to rename Git's default "master" branch to "main", exploring the motivations behind the change, community reactions, potential impacts on existing projects, and the broader discussion about terminology in software development.
The article explains how to write clean, expressive code by defining dirty versus clean code, presenting expert guidelines on naming, commenting, function design, and testing, and illustrating each point with concrete good and bad code examples.
This article distills key principles from "Clean Code", covering how expressive naming, well‑structured functions, and disciplined testing together raise code readability, maintainability, and reliability, while providing concrete examples and actionable guidelines for everyday programming.
This article presents practical JavaScript clean‑code guidelines—including intention‑revealing naming, single‑purpose functions, pure functions, proper async handling, and linting standards—to help developers write more readable, maintainable, and error‑free code.
A developer survey of 4,500 programmers reveals that naming variables, classes, and functions is perceived as the biggest programming challenge, highlighting its impact on code readability, design quality, and maintenance, and underscoring the art and difficulty of choosing concise, meaningful identifiers.
Clip is an automation operations tool that replaces traditional IP‑based server management with a flexible String naming scheme, offering C/S architecture, an SDK with multiple commands, and real‑world case studies that demonstrate reduced complexity and risk for large‑scale infrastructures.
