A candid conversation with an overseas AI student reveals that while China excels in model development and engineering speed, it still lags in creating distinctive AI terminology and standards, prompting a call for Chinese engineers to shift from followers to innovators.
The article examines the history and criteria of Chinese mathematical terminology, highlighting well‑translated terms like "微积分" and "向量", exposing misleading translations such as "数学归纳法", and offering guidelines for creating clear, concise, and unambiguous mathematical names.
The article explains Huawei's IPD (Integrated Product Development) workflow from a project perspective—covering concept, planning, development, and release stages—and provides a detailed glossary of IPD‑related terminology used throughout the product lifecycle.
This article investigates why programmers refer to code as “scripts,” examining humorous misconceptions, historical translation quirks, the word’s original meaning, scripting language characteristics, and web‑page placement to provide a comprehensive understanding of the term’s evolution.
The article explains how the terms “neural network” and “deep learning” originated, why they were once treated as distinct branches of AI, and how historical biases and naming politics eventually merged them into a single research direction.
The article argues that the vague term “user” misleads software design, illustrates the problem with airline reservation, Unix, and SaaS examples, shows how it creates security flaws like the Confused Deputy issue, and urges precise terminology early in projects to avoid costly rework.
The article explains how the vague term “user” leads to flawed requirements, security vulnerabilities such as the Confused Deputy problem, and costly redesigns, urging developers to adopt precise terminology like “traveler”, “agent”, or “member” early in a project.
This article dissects the often‑confused Chinese payment terms clearing, settlement and clear‑settlement, explains their international definitions, legal meanings, institutional usage, and how different contexts and business models shape their interpretation, offering a clear framework to avoid misunderstandings.
This article presents a comprehensive English glossary of MySQL terminology, translating Chinese explanations of commands, data types, constraints, and control structures into clear English definitions for developers and database learners.
This article compiles the most frequently used programmer abbreviations, explaining their meanings and contexts, and presents them visually so both newcomers and seasoned developers can quickly decode the shorthand that permeates modern software development discussions.
The article warns that using the vague term “user” in software design creates security flaws and conceptual confusion, illustrated with ticket‑booking, Unix, and SaaS examples, and advises defining precise concepts like “team” and “member” early to avoid costly redesigns.
The article explains how the vague term “user” creates design flaws and security vulnerabilities across domains such as airline booking systems, Unix environments, and SaaS platforms, and argues for precise terminology to avoid costly rework and confused‑deputy attacks.
GitHub announced that starting October 1 new repositories will default to the "main" branch instead of "master", a change driven by social concerns and industry-wide efforts to replace terminology perceived as discriminatory, with many other tech companies following suit.
Linux developers, led by Linus Torvalds, have approved a proposal to replace racially sensitive terms like master/slave and blacklist/whitelist with neutral alternatives, reflecting a broader industry move toward inclusive language in code and documentation.
The article examines the controversy sparked by Google’s VP withdrawing from Black Hat USA 2020 and the push for neutral terminology in cybersecurity, exploring historical origins, community reactions, and recent industry changes toward inclusive language.
The article explains how the vague term “User” leads to poor requirements, hidden security flaws like the Confused Deputy problem, and costly redesigns, urging developers to adopt precise terminology such as “team” and “member” early in a project.
Using the vague term “user” to describe diverse actors—passengers, agents, services, or system accounts—creates ambiguous models that lead to design flaws and serious security risks such as the Confused Deputy problem, urging developers to adopt precise terminology like “team” and “member” from the start.
The Redis community is urging a rename of the master‑slave replication terminology due to social concerns, but the project's lead highlights significant compatibility costs, outlining short‑term compromises and long‑term redesigns while balancing technical feasibility and community expectations.
This article presents a comprehensive bilingual DevOps glossary compiled from the DevOps Handbook, offering standardized English‑Chinese terminology, a change log, and open‑source contribution instructions via GitHub for continuous improvement.
This article demystifies common product‑manager terminology—from PD vs. PM and blue‑ocean vs. red‑ocean strategies to C2C models, entry barriers, PDD, CRUD, PDCA, KPI, and MVP—providing designers with a concise reference to improve cross‑functional communication.
