Style guide
A style guide is a documented set of conventions for consistently formatting, naming, organizing, or presenting source code.
Lead Developer Career Guide
A rule set governing how source code is written, structured, and maintained within a software project or organization.
- How it is used
- Sets shared coding conventions so developers can locate, review, and maintain one another’s code.
- How deep it goes
- Details naming, braces, comments, documentation, onboarding, review, and revision; stops short of prescribing a complete project-specific guide.
- Examples
- Uses curly-brace placement, function comments, and names for files, directories, modules, functions, and features.
- What you can do after
- Operate/configure it by documenting team rules, reviewing them during onboarding, enforcing them in code review, and updating them with feedback.
"Looks Good to Me"
A style guide is a document specifying conventions for the formatting, naming, and organization of source code.
- How it is used
- Coordinates team code-style decisions and removes subjective formatting disputes from pull-request review.
- How deep it goes
- Explains style guides as automated rulesets and demonstrates formatting enforcement, without descending into formatter internals.
- Examples
- Uses JavaScript brace-style rules, correctly and incorrectly formatted code, and variable-declaration spacing examples.
- What you can do after
- Apply it via ESLint, formatters, local checks, and pull-request gates to enforce agreed coding conventions.
Think Like a Software Engineering Manager
A coding standard is a documented set of rules and conventions for writing source code consistently and maintainably.
- How it is used
- Guides engineering managers in supporting implementation and improving code quality, consistency, and maintainability.
- How deep it goes
- Names convention areas and enforcement methods but does not specify detailed rules for any one language.
- Examples
- Uses naming, formatting, comments, and error handling as convention examples.
- What you can do after
- Apply standards through peer code reviews and automated tools to promote consistency.
Read how Think Like a Software Engineering Manager explains style guide →
100 SQL Server Mistakes and How to Avoid Them
A coding standard is a documented set of stylistic and technical rules for writing software consistently within a project.
- How it is used
- Establishes shared stylistic and technical rules for SQL Server data-tier application development.
- How deep it goes
- Distinguishes stylistic from technical rules and illustrates enforcement consequences, without prescribing one universal formatting convention.
- Examples
- Uses an unreadable stored procedure, alternate SELECT formatting, and cursor-based index rebuilding as concrete cases.
- What you can do after
- Apply shared rules consistently and resist exceptions that undermine maintainability, performance, or security practices.
Read how 100 SQL Server Mistakes and How to Avoid Them explains style guide →
Think Like a CTO
A coding standard is a documented rule set governing the style, structure, and practices used in source code.
- How it is used
- Establishes shared coding conventions so a growing team can keep code readable and maintainable.
- How deep it goes
- Explains why standards matter and how to encourage adherence, without specifying language-level rules.
- Examples
- Uses brittle, untouchable code and a SaaS due-diligence case where absent standards contributed to costly technical debt.
- What you can do after
- Operate/configure it by choosing shared standards, supporting adherence with IDE tools and reviews, and checking that the team follows them.
Go by Example
A programming convention is a commonly accepted practice for organizing or expressing code within a language community.
- How it is used
- Establishes shared Go conventions for writing readable, maintainable, explicit, and testable code.
- How deep it goes
- Works through naming and diagnostic-test conventions, while deferring broader idioms for continued exploration.
- Examples
- Uses url.Parse, uri and u variable names, got/want error output, and cmp.Diff for URL comparisons.
- What you can do after
- Evaluate/understand idiomatic Go by judging simplicity, pragmatism, explicitness, testability, and consistency.
Data Pipelines with Apache Airflow, Second Edition
A style guide is a documented set of conventions for writing source code, including formatting, naming, and layout rules.
- How it is used
- Establishes consistent conventions for readable DAG and Python code.
- How deep it goes
- Defines formatting and naming guidance, demonstrates corrections, and defers thorough clean-coding practices.
- Examples
- Uses PEP 8 before-and-after snippets, Flake8 reports, Black formatting, and consistent DAG dependency notation.
- What you can do after
- Apply it via PEP 8, Flake8, Pylint, or Black to produce and check consistent Python code.
Read how Data Pipelines with Apache Airflow, Second Edition explains style guide →
Coding with AI
A style guide is a set of rules and guidance governing the visual and interaction design of an application or product.
- How it is used
- Guides consistent visual and interaction decisions while designing an application.
- How deep it goes
- Defines colors, typography, spacing, alignment, and page structure, but stops short of implementation details.
- Examples
- Uses quiz entry, question, and results pages with specified colors, controls, spacing, and content.
- What you can do after
- Apply shared design rules and wireframes when laying out application pages.
Shipping Go: Develop, deliver, discuss, design, and go again
A document that defines conventions and rules for writing source code in a consistent style.
- How it is used
- Standardizes team code and automates checks before testing and delivery.
- How deep it goes
- Defines formatting, documentation, patterns, and tests, then shows formatter and CI enforcement without developing a full linting system.
- Examples
- Uses Go formatting, a Makefile check, and a CI pipeline that requires formatting before tests.
- What you can do after
- Apply it via formatters, linters, repository checks, and CI gates that keep team code consistent.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains style guide →
Digital Twins in Action
A standard is an agreed specification for the structure, behavior, or exchange of systems and data.
- How it is used
- Keeps digital twin components interoperable across sensor communication, model exchange, and changing tools or vendors.
- How deep it goes
- Develops a layered selection framework and cost checklist, but stops short of protocol configuration or schema implementation.
- Examples
- Uses IFC for Building Information Modeling exchange and OPC UA for sensor and industrial-device communication.
- What you can do after
- Evaluate/understand whether a standard addresses an integration need and justifies its implementation, training, maintenance, and audit costs.
Related concepts
- culturecontrasts with · Culture is the shared values, beliefs, norms, practices, and meanings that shape behavior and interpretation within a social group or organization.
- interoperabilityaddresses · Interoperability is the ability of independent systems or components to exchange and correctly use information or functionality through compatible interfaces, formats, protocols, or behaviors.
- naming standardconfigures · A naming standard is an established set of rules or patterns for assigning names consistently to software elements, resources, or other artifacts.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.