易读代码的艺术

易读代码的艺术 pdf epub mobi txt 电子书 下载 2025

出版者:东南大学出版社
作者:Dustin Boswell,Trevor Foucher
出品人:
页数:190
译者:
出版时间:2012-6
价格:39.00元
装帧:
isbn号码:9787564134471
丛书系列:
图书标签:
  • 编程
  • coding-style
  • 程序设计
  • Programming
  • 代码优化
  • 软件开发
  • 计算机
  • 代码质量
  • 编程
  • 代码
  • 可读性
  • 软件工程
  • 开发实践
  • 编程风格
  • 高效开发
  • 代码质量
  • 程序员成长
  • 技术艺术
想要找书就要到 小美书屋
立刻按 ctrl+D收藏本页
你会得到大惊喜!!

具体描述

《易读代码的艺术(影印版)》分析了许多的“糟糕代码”(这些代码有很多是出自于他们自己之手),他们试图厘清为什么这些代码如此糟糕以及如何改进这些代码。他们得出的结论是:你必须写出让他人(这里也包括你自己)花费最少时间能够理解的代码。

作者简介

博斯韦尔(Dustin Boswell),毕业于加州理工学院,在谷歌公司从事过五年的Web信息采集基础设施和广告营销计划的研究工作。他先后构建过多个Web站点,目前的主要研究兴趣在于大数据的处理和机器学习领域的相关技术。

富彻(Trevor Foucher),过去十年中先后在微软公司担任Windows及安全相关产品的工程师、经理和技术领导者的职务,现任职于谷歌公司,主要从事谷歌广告营销计划和搜索基础设施的研究工作。

目录信息

PREFACE
1 CODE SHOULD BE EASY TO UNDERSTAND
What Makes Code "Better"?
The Fundamental Theorem of Readability
Is Smaller Always Better?
Does Time—Till—Understanding Conflict with Other Goals?
The Hard Part
Part One SURFACE—LEVEL IMPROVEMENTS
2 PACKING INFORMATION INTO NAMES
Choose Specific Words
Auoid Generic Names Like Imp and retual
Prefer Concrete Names ouer Abstract Names
Attaching Extra Information to a Name
How Lon.g Should a Name Be?
Use Name Formatting to Conuey Meaning
Summary
3 NAMES THAT CAN'T BE MISCONSTRUED
Example: Filter()
Example: Clip(text, length)
Prefer rain and max for (Inclusiue) Limits
Prefer first and last for Inelusiue Ranges
Prefer herin and end for.Inclusiue/Exclusiue Ranges
Naming Booleans
Matching Expectations of Users
Example: Eualuating Multiple Name Candidates
Summary
4 AESTHETICS
Why Do Aesthetics Matter?
BearranRe Line Breaks to Be Consistent and Compact
Use Methods to Clean Up Irregularity
Use Column Alignment When Helpful
Pick a Meaningful Order, and Use It Consistently
Organize Declarations into Blocks
Break Code into "Parafgraphs"
Personal Style uersus Consistency
Summary
5 KNOWING WHAT TO COMMENT
What NOT to Comment
Becording Your Thouyhts
Put Yourself in the Reader's Shoes
Final Thoughts——Getting Over Writer's Block
Summary
6 MAKING COMMENTS PRECISE AND COMPACT
Keep Comments Compact
Avoid Ambiguous Pronouns
Polish Sloppy Sentences
Describe Function Behavior Precisely
Use Input/Output Examples That Illustrate Corner Cases
State the Intent of Your Code
"Named Function Parameter" Comments
Use Information—Dense Words
Summary
Part Two SIMPLIFYING LOOPS AND LOGIC
7 MAKING CONTROL FLOW EASY TO READ
The Order of Arguments in Conditionals
The Order of if/else Blocks
The ?: Conditional Expression (a.k.a."Ternary Operator")
Avoid dogwhile Loops
Returning Early from a Function
The Infamous goto
Minimize Nesting
Can You Follow the Flow of Execution?
Summary
8 BREAKING DOWN GIANT EXPRESSIONS
Explaining Variables
Summary Variables
Using De Morgan's Laws
Abusing Short—Circuit Logic
Example: Wrestling with Complicated Logic
Breaking Down Giant Statements
Another Creative Way to Simplify Expressions
Summary
9 VARIABLES AND READABILITY
Eliminatinfg Variables
Shrink the Scope of Your Variables
Prefer Write—Once Variables
A Final Example
Summary
Part Three REORGANIZING YOUR CODE
10 EXTRACTING UNRELATED SUBPROBLEMS
Introductory Example: find Closest Loeation()
Pure Utility Code
Other General—Purpose Code
Create a Lot of General—Purpose Code
Project—Specific Functionality
Simplilying an Existing Interface
Reshaping an Interface to Your Needs
Taking Things Too Far
Summary
11 ONETASK ATA TIME
Tasks Can Be Small
Extracting Values from an Object
A Larger Example
Summary
12 TURNING THOUGHTS INTO CODE
Describing Logic Clearly
Knowing Your Libraries Helps
Applying This Method to Larger Problems
Summary
13 WRITING LESS CODE
Don't Bother Implementing That Feature——You Won't Need It
Question and Break Douan Your Requirements
Keeping Your Codebase Small
Be Familiar with the Libraries Around You
Example: Using Unix Tools Instead of Coding
Summary
Part Four SELECTED TOPICS
14 TESTING AND READABILITY
Make Tests Easy to Read and Maintain
What's Wrong with This Test?
Making This Test More Readable
Making Error Messages Readable
Choosing Good Test Inputs
Naming Test Functions
What Was Wrong with That Test?
Test—Friendly Deuelopment
Going Too Far
Summary
15 DESIGNING AND IMPLEMENTING A "MINUTE/HOUR COUNTER"
The Problem
Defining the Class Interface
Attempt 1: A Naiue Solution
Attempt 2: Conueyor Belt Design
Attempt 3: A Time—Bucketed Design
Comparing the Three Solutions
Summary
A FURTHER READING
INDEX
· · · · · · (收起)

读后感

评分

《The Art of Readable Code》是一本关于代码可读性的书,很薄,180页,我手中的版本是2012年6月由东南大学出版社出版的影印版,其英文原版则是2011年出版的,已经是一本7年前的书了。一般而言,IT技术的发展之快导致技术书籍中提到的技术很快就会过期,但是这本不同,书中的观...  

评分

评分

“这是一本被低估了其价值的书”,一位朋友在向我推荐这本书时向我如是说。听到这样的评价,笔者在拿到书后立即开始兴奋地阅读,但因为一些琐事,本打算一周内看完写书评的,结果又拖了两天。总体来讲,确实受益匪浅,物超所值,很受用。 作为一名程序员,当看别人的代码时,...  

评分

本书主要观点: 1. 优雅的命名 1.1 命名具备自解释性(解释用途) 1.2 能附加(必要的)更多信息(匈牙利命名法的类型信息) 1.3 命名格式统一,如 kConstName 骆驼命名法或单词下划线 bool变量的is, has, can等前缀 ... 1.4 遵循业界的命...  

评分

很短的一本小书,基本是在编译代码的时候顺便看完的,差不多花了三天的时间吧,看完的整体感受是很实用,增加了对整理代码可读性的欲望。可以说是软实力的提升吧,书里面举的例子都很实用,基本上实战都可以用到,我觉得这本书应该至少阅读两遍吧。 除了这本书以外,还可以考虑...

用户评价

评分

读了英文版,5分。team work/code review必备。

评分

特地买了本影印版的

评分

像coding style这种容易被忽略但在编码中有不小影响力的东西值得多了解。

评分

思路清晰,言简意赅

评分

读了英文版,5分。team work/code review必备。

本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度google,bing,sogou

© 2025 book.quotespace.org All Rights Reserved. 小美书屋 版权所有