Ask HN: Recommended Books/Articles on clean code design.

9 pointssafetyscissors14y ago5 comments

Hi Everyone,

I've been having a problem lately where I feel like my code I feel like my code base is in disarray and I get to the point where I feel dirty.

I was wondering if there are any books out there to help me improve my coding style to a more organised structure and also how to make it easier to understand for myself and others.

Thank you :)

Ask HN: Recommended Books/Articles on clean code design.

9 pointssafetyscissors14y ago5 comments

Hi Everyone,

I've been having a problem lately where I feel like my code I feel like my code base is in disarray and I get to the point where I feel dirty.

I was wondering if there are any books out there to help me improve my coding style to a more organised structure and also how to make it easier to understand for myself and others.

Thank you :)

5 comments

5 comments · 4 top-level

munaf14y ago· 1 in thread

The Art of Readable Code is excellent.

http://www.amazon.com/Art-Readable-Code-Dustin-Boswell/dp/05...

swanson14y ago

I respectfully fully disagree with recommending The Art of Readable Code. Particularly, I take issue with the advice on comments, as well as the strange point that sometimes 'goto' is acceptable.

While there are some good sections on things like naming variables and "code aesthics" that kind of advice is not going to dramatically improve your code quality and I think most developers achieve better results with something like Clean Code or Code Complete.

swanson14y ago

The first step is to be aware that you aren't writing succinct, manageable code - so you are already making progress :)

I'd recommend these books, mixed with some searching around for best practices for whatever specific framework/language/toolkit you are writing code with.

Clean Code

http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman...

Refactoring to Patterns

http://www.amazon.com/Refactoring-Patterns-Joshua-Kerievsky/...

vermasque14y ago

An alternative or supplement to books would be to do static code reviews with someone. They can give feedback that a book can't. For example, ask the reviewer what would make the reviewed code easier to understand.

Also, you could look up open source projects in the technology stack that you use and compare their code base to yours. In other words, follow a good example if it exists.

jackkinsella14y ago

I highly recommend Refactoring, by Martin Fowler.

j / k navigate · click thread line to collapse