Comments on: Clean Code: Book Review

By: Book Club: SOLID Principles (Uncle Bob Martin) at Mark Needham

Book Club: SOLID Principles (Uncle Bob Martin) at Mark Needham — Tue, 15 Sep 2009 15:12:48 +0000

[...] quite like the newspaper metaphor to writing code which Uncle Bob describes in Clean Code and he elabroates on this further in a recent post about extracting method until you drop. I find [...]

By: Coding: Single Level of Abstraction Principle at Mark Needham

Coding: Single Level of Abstraction Principle at Mark Needham — Fri, 12 Jun 2009 07:37:49 +0000

[...] first came across the idea of writing code at the same level of abstraction in Uncle Bob's Clean Code although I only learnt about the actual term in Neal Ford's The Productive [...]

By: Coding: Why do we extract method? at Mark Needham

Coding: Why do we extract method? at Mark Needham — Thu, 04 Jun 2009 10:34:42 +0000

[...] since I've read Uncle Bob's Clean Code book my approach to coding has been all about the 'extract method' refactoring – I pretty much look to [...]

By: Pair Programming: Refactoring at Mark Needham

Pair Programming: Refactoring at Mark Needham — Tue, 26 May 2009 13:50:27 +0000

[...] there are certainly books which explain how to do refactorings on our code a lot of the approaches that I like to use have [...]

By: Finding the value in fixing technical debt at Mark Needham

Finding the value in fixing technical debt at Mark Needham — Sat, 10 Jan 2009 04:07:33 +0000

[...] reading Uncle Bob's Clean Code I've become a bit fanatical in my approach to trying to make code as readable as possible, mainly [...]

By: Corey Haines

Corey Haines — Sun, 04 Jan 2009 14:39:50 +0000

"I also found the following statement revealing as I was under the assumption that experienced developers wrote code like this first time" That is an interesting assumption; I wonder if others have it. I've often thought it would be a neat application to look through your scm repo for a file and watch the evolution of a file/your system's code structure over time. I commit constantly (every time you commit, and angel gets it wings), so there is a lot of crappy, ugly code stored in my repo throughout the process. I'm even willing to leave some not-so-pretty code sitting around, as long as it passes the specs, if I can't seem to see my way out of it at the moment. I'll then either figure it out later, or I'll show it to someone new, and they usually will have an idea.

By: What is a unit test? at Mark Needham

What is a unit test? at Mark Needham — Fri, 10 Oct 2008 13:24:09 +0000

[...] make the former happen but the final word goes to Uncle Bob who suggests the F.I.R.S.T acronym in Clean Code to describe what well written (clean) unit tests should look [...]

By: Test Driven Development By Example: Book Review at Mark Needham

Test Driven Development By Example: Book Review at Mark Needham — Tue, 07 Oct 2008 13:20:50 +0000

[...] How closely will the lessons here link to those from Clean Code? [...]

By: Clean Code: A Handbook of Agile Software Craftsmanship « techtotty

Clean Code: A Handbook of Agile Software Craftsmanship « techtotty — Sun, 21 Sep 2008 17:15:32 +0000

[...] Clean Code: A Handbook of Agile Software Craftsmanship . There’s a pretty good review of the book here http://www.markhneedham.com/blog/2008/09/15/clean-code-book-review/ [...]

By: Alex Hung

Alex Hung — Mon, 15 Sep 2008 11:10:00 +0000

Two other books I'd suggest to read also: Object Thinking, and Code Complete. You've probably heard of and read Code Complete, but Object Thinking is a bit more obscure. However, I think it is has more profound effect on me than Code Complete.