0 views collected around this technical thread.
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 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 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 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.
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 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.
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.
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.