liveBook · Manning

Technical frugality

As explained in The Art of Code

Technical frugality is the practice of choosing technologies and architectures that appropriately satisfy a project's actual needs without unnecessary complexity.

Technical frugality chooses technologies and architectures that satisfy real project needs without adding unnecessary complexity, resource use, or maintenance cost. section 8.4.1

Avoid treating every problem as a fit for the tool you know best. Prefer efficient, relevant choices over personal preference or fashionable architecture. section 8.4.1

Simplifying instead of accumulating

Infinite scroll can consume energy and user attention. Gmail’s removal of rarely used “Quote selected text” simplified the interface. Uber’s move from an unwieldy collection of thousands of microservices toward larger macroservices illustrates correcting an over-complex architectural choice. section 8.4.1

How The Art of Code covers it

How deep it goes
Defines the principle, explains its cognitive and economic risks, and illustrates correction through product and architecture examples.
Examples
Uses infinite scroll, Gmail’s removed reply feature, and Uber’s transition from microservices toward macroservices.
What you can do after
Evaluate technologies and architectures by project relevance, efficiency, complexity, resource usage, and maintenance cost.
How it connects
Connects sustainability with dark patterns, hype-driven development, microservices, monolithic architecture, and macroservices.
Cover of The Art of Code
liveBookmanning.com
Read The Art of Code on liveBook Get the book at manning.com

Related concepts

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