Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
[TDD] Re: If you could get your colleagues to read just one book on TDD, which would it be?
|
I found goos to be not so much a "how to write tests" book, but more of an illustration of how code can evolve when using TDD. ?My main criticism?with the book is that it is easy to lose the big picture of the application (lots of snippets, few diagrams).
A former co-worker of mine recently uploaded a chapter by chapter implementation of goos?(with Mockito) to git hub that helped me maintain a clear view of the big picture. I also recommend watching Uncle Bob's TDD videos on cleancoders.com after doing the bowling kata. -Bob Graffagnino ________________________________ From: robi.yagel <reuven.yagel@...> To: testdrivendevelopment@... Sent: Tuesday, April 30, 2013 2:43 PM Subject: [TDD] Re: If you could get your colleagues to read just one book on TDD, which would it be? ? Two books that I can recommend: Osherov, The Art of Unit testing jbrains, Responsible Design for Android - on going work, somewhat builds on GOOS --- In testdrivendevelopment@..., John Carter <john.carter@...> wrote:
|
|
Keith Ray
The following are some books I recommend to developers new to Agile software development.
toggle quoted message
Show quoted text
This book is new, pretty complete, and easy-to-read about adopting agile software development: The Agile Samurai This book covers the same ground as the Agile Samurai book. It's a little more in-depth. Most of it is now free on-line, but you can buy the book from Amazon: The Art of Agile Development. This book is about test-driven development in C: Test Driven Development for Embedded C This is the original TDD book in Java: Test-Driven Development The original book on Refactoring. If you have legacy code, you also need to this book: Working Effectively With Legacy Code. C. Keith Ray On Apr 30, 2013, at 8:46 PM, Bob Graffagnino <rkgraff@...> wrote:
I found goos to be not so much a "how to write tests" book, but more of an illustration of how code can evolve when using TDD. My main criticism with the book is that it is easy to lose the big picture of the application (lots of snippets, few diagrams). |
|
Dennis Traub
On Wed, May 1, 2013 at 10:24 PM, Keith Ray <keith.ray@...> wrote:
**I believe that this is one of the most essential books, no matter if you have to deal with legacy code (everyone has eventually, anyway). |
|
Dennis,
On 5/1/13 4:29 PM, Dennis Traub wrote: On Wed, May 1, 2013 at 10:24 PM, Keith Ray <keith.ray@...> wrote:You should pair that with The Mikado Method (mikadomethod.org)**I believe that this is one of the most essential books, no matter if you - George -- ---------------------------------------------------------------------- * George Dinwiddie * Software Development Consultant and Coach ---------------------------------------------------------------------- |
|
On Thu, May 2, 2013 at 1:03 PM, George Dinwiddie <lists@...>wrote:
You should pair that with The Mikado Method (mikadomethod.org)Now THAT is a Very Good Find! An Excellent Book! Thanks, just what I was hoping for! -- ------------------------------ This email, including any attachments, is only for the intended recipient. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If you are not an intended recipient, you may not use, disseminate, distribute or reproduce such email, any attachments, or any part thereof. If you have received a message in error, please notify the sender immediately and erase all copies of the message and any attachments. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission nor can we guarantee that any email or any attachments are free from computer viruses or other conditions which may damage or interfere with recipient data, hardware or software. The recipient relies upon its own procedures and assumes all risk of use and of opening any attachments. ------------------------------ |
|
I came up with an easy way to generate Mikado diagrams programmatically using Ruby-Graphviz. ?One of the co-authors of the book (Ola) liked it. ?Here's an example. ?The Mikado has two direct prerequisites ("1" and "3"), and prerequisite 1 has a further prerequisite ("2"). ?Outputs to a "mikado.png" file.
require 'graphviz/dsl' digraph :G do ? mikado[:label => 'The Mikado', :shape => 'doublecircle'] ? mikado << prereq_1[:label => 'Prerequisite 1'] ? mikado << prereq_3[:label => 'Prerequisite 3'] ? prereq_1 << prereq_2[:label => 'Prerequisite 2'] ? output :png => 'mikado.png' end ? Al ________________________________[Non-text portions of this message have been removed] |
to navigate to use esc to dismiss