liveBook · Manning

Quality

As explained in Lead Developer Career Guide

The degree to which software satisfies requirements and achieves desirable properties such as reliability, maintainability, and correctness.

Software quality is a project priority: deliver clean, maintainable work without sacrificing it to meet deadlines. Supporting it takes good engineering practices and realistic workloads. section 12.2.2

Practical ways to protect quality include:

  • Uphold coding standards, conduct code reviews, and test thoroughly. section 12.2.2
  • Estimate tasks with the team and work with project managers to ensure resources are adequate; burnout can undermine the quality of products and services. section 12.2.2

Reusable prototypes

A CSV-handling library or a React starter project can be reused across projects. Building prototypes this way encourages well-structured, understandable, maintainable code, and sharing them can invite useful feedback. section 4.2.3

How Lead Developer Career Guide covers it

How deep it goes
Connects quality to standards, reviews, testing, maintainability, and workload, without describing a scoring method.
Examples
Uses a reusable CSV library, a React starter project, and workplace examples of deadlines, resource constraints, and burnout.
What you can do after
Practice quality-focused delivery by reviewing code, testing thoroughly, and planning realistic workloads and resources.
How it connects
Links quality with coding standards, code reviews, software testing, maintainability, and project planning.

Also explained in

Compare how 10 books explain quality →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Lead Developer Career Guide. The section links point to the parts of the book it draws on.