HomeGroupsTalkMoreZeitgeist
Search Site
This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.

Results from Google Books

Click on a thumbnail to go to Google Books.

The Art of Readable Code (Theory in…
Loading...

The Art of Readable Code (Theory in Practice) (edition 2011)

by Dustin Boswell, Trevor Foucher

MembersReviewsPopularityAverage ratingConversations
1472188,112 (4.06)None
As programmers, we've all seen source code that's so ugly and buggy it makes our brain ache. Over the past five years, authors Dustin Boswell and Trevor Foucher have analyzed hundreds of examples of "bad code" (much of it their own) to determine why they're bad and how they could be improved. Their conclusion? You need to write code that minimizes the time it would take someone else to understand it -- even if that someone else is you. This book focuses on basic principles and practical techniques you can apply every time you write code. Using easy-to-digest code examples from different languages, each chapter dives into a different aspect of coding, and demonstrates how you can make your code easy to understand. Simplify naming, commenting, and formatting with tips that apply to every line of code; Refine your program's loops, logic, and variables to reduce complexity and confusion; Attack problems at the function level, such as reorganizing blocks of code to do one task at a time; Write effective test code that is thorough and concise, as well as readable. - Publisher.… (more)
Member:paulmarculescu
Title:The Art of Readable Code (Theory in Practice)
Authors:Dustin Boswell
Other authors:Trevor Foucher
Info:O'Reilly Media (2011), Edition: 1, Paperback, 206 pages
Collections:Your library
Rating:
Tags:None

Work Information

The Art of Readable Code by Dustin Boswell

None
Loading...

Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

Showing 2 of 2
This is an excellent book that focuses on one thing and describes it well. This book is not about grand methods of software engineering or code architecture. It is, as the title indicates, about writing readable code. Boswell and Foucher cover the small things that can be done to make code easier to read, and they discuss why their suggestions generally make code more readable.

The content here is not unique. Much of it can be found in [b:Code Complete|4845|Code Complete|Steve McConnell|http://d.gr-assets.com/books/1328830405s/4845.jpg|8419] or [b:Clean Code|3735293|Clean Code A Handbook of Agile Software Craftsmanship|Robert C. Martin|http://d.gr-assets.com/books/1347436688s/3735293.jpg|3779106]. Rather, it is the narrow focus that makes this book valuable. It joins my short list of technical books that all programmers should read, even those who don't read technical books just for fun. ( )
  eri_kars | Jul 10, 2022 |
I took this book to help me establish important habits of writing code. I would recommend this to anyone whose daily work involves programming or software development.

Let me try to summarize in few paragraphs:

The fundamental theorem of code is that it is code written must be easier to understand.

To make surface level improvements in our code, we want to define variables, functions with precise words, information packed comments and formatting in such a way that readability is easy.

We want to make sure to pack enough information to be clear, precise in naming variables i.e. Kill(), Pause() instead of Stop(). At times, other programmers might misconstrue names from our programs, we want to make sure we think of other programmers and how they would interpret our code.

Comments are invaluable and should be used only when it helps in understanding the code better. We follow standard left to right value variable while using control flow and minimize as much as possible for using deep nested loops. In case of complex expressions or giant expressions, as much as we can minimize mental stack for other programmers, it is easier to maintain, code is less likely to create bugs.

As much as possible, the essential functions can be implemented from pertinent programming library so that we write less code. Each function needs to contain one task at a time and organize as much modules, functions as possible.

I have a summary of entire book, if you do want it, PM me.

Deus Vult,
Gottfried ( )
  gottfried_leibniz | Jun 25, 2021 |
Showing 2 of 2
no reviews | add a review
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Canonical title
Original title
Alternative titles
Original publication date
People/Characters
Important places
Important events
Related movies
Epigraph
Dedication
First words
Quotations
Last words
Disambiguation notice
Publisher's editors
Blurbers
Original language
Canonical DDC/MDS
Canonical LCC

References to this work on external resources.

Wikipedia in English

None

As programmers, we've all seen source code that's so ugly and buggy it makes our brain ache. Over the past five years, authors Dustin Boswell and Trevor Foucher have analyzed hundreds of examples of "bad code" (much of it their own) to determine why they're bad and how they could be improved. Their conclusion? You need to write code that minimizes the time it would take someone else to understand it -- even if that someone else is you. This book focuses on basic principles and practical techniques you can apply every time you write code. Using easy-to-digest code examples from different languages, each chapter dives into a different aspect of coding, and demonstrates how you can make your code easy to understand. Simplify naming, commenting, and formatting with tips that apply to every line of code; Refine your program's loops, logic, and variables to reduce complexity and confusion; Attack problems at the function level, such as reorganizing blocks of code to do one task at a time; Write effective test code that is thorough and concise, as well as readable. - Publisher.

No library descriptions found.

Book description
Haiku summary

Current Discussions

None

Popular covers

Quick Links

Rating

Average: (4.06)
0.5
1 1
1.5
2
2.5
3 2
3.5 3
4 10
4.5
5 8

Is this you?

Become a LibraryThing Author.

 

About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 207,072,828 books! | Top bar: Always visible