liveBook · Manning

Style guide

Also called coding standard, coding style, coding conventions, style guidelines

A style guide is a documented set of conventions for writing and organizing source code consistently.

How 13 Manning books explain it

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.

Read how Lead Developer Career Guide explains style guide →

"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.

Read how "Looks Good to Me" explains style guide →

Fundamentals of Cybersecurity

A standard is a formally specified requirement or criterion that translates policy requirements into consistent, measurable implementation practices.

How it is used
Turns security requirements into consistent criteria for implementing and assessing organizational practices.
How deep it goes
Defines standards, distinguishes internal from external standards, and explains adoption and certification consequences without giving a procedure for drafting one.
Examples
Uses ISO/IEC 27001 certification and a customer-data standard specifying AES-256 encryption, approved systems, and multi-factor authentication.
What you can do after
Evaluate/understand whether a requirement belongs in a standard rather than a policy, procedure, regulation, or guideline.

Read how Fundamentals of Cybersecurity explains style guide →

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.

Read how Think Like a CTO explains style guide →

Memory Safe C++

A set of rules specifying what software source code may contain and what it must not do.

How it is used
Translates safety-standard requirements into checkable C++ rules for review, analysis, and certification evidence.
How deep it goes
Explains the rationale for restricting constructs and patterns, then compares guideline scope, rule categories, and certification roles.
Examples
Compares MISRA C++:2023, AUTOSAR C++14, CERT C++, HIC++, and JSF C++ by version, domain, rule count, and status.
What you can do after
Evaluate and understand which coding guideline translates a project's governing safety standard into an enforceable C++ subset.

Read how Memory Safe C++ explains style guide →

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.

Read how Go by Example explains style guide →

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.

Read how Coding with AI explains style guide →

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 →

The Coder Cafe

A standard is an agreed rule or specification that guides how software is designed, implemented, or maintained.

How it is used
Guides controlled codebase growth through shared conventions, standards, communication, and incremental maintenance.
How deep it goes
Defines consistency and gives five supporting practices, but does not specify a formal style-guide document or rule syntax.
Examples
Contrasts consistently naming an entity X with inconsistently renaming it Y, and applies the Boy Scout rule to pull requests.
What you can do after
Apply shared conventions and incremental cleanup to keep a codebase maintainable, predictable, and harmonious.

Read how The Coder Cafe 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
Supports interoperability and replaceable components across digital twin architectures.
How deep it goes
Provides a layered framework and practical adoption assessment, including costs, without an implementation walkthrough.
Examples
Uses IFC for building-model exchange and OPC UA for sensor and industrial-device communication.
What you can do after
Evaluate standards for adoption against system needs, industry support, implementation costs, and ongoing obligations.

Read how Digital Twins in Action explains style guide →

Also covered in

What to know first

Related concepts

Questions about style guide

What is style guide?

A style guide is a documented set of conventions for writing and organizing source code consistently.

Which Manning books explain style guide?

Lead Developer Career Guide, "Looks Good to Me", Fundamentals of Cybersecurity, Think Like a Software Engineering Manager, 100 SQL Server Mistakes and How to Avoid Them, Think Like a CTO, Memory Safe C++, Go by Example and 5 more.

What should I know before learning style guide?

Manning books that teach style guide usually introduce software testing, code review, design pattern and maintainability first.

What is the difference between style guide and culture?

A style guide is a documented set of conventions for writing and organizing source code consistently. Culture is the shared values, beliefs, norms, meanings, and practices that shape behavior within a social group or organization.

What kinds of style guide are there?

Kinds of style guide include ISO 20022 and ISO 27001.

What is style guide also called?

Style guide is also called coding standard, coding style, coding conventions or style guidelines.

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.