Shop the new tech.book(store)
New! Introducing the tech.book(store), a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry.
> Shop now
Ron Jeffries was the onsite coach for the original eXtreme Programming software development project. He also helped plan and teach the first XP Immersion course. An independent consultant and veteran systems developer, he’s been a leader in the XP movement for more than eight years, speaking at developer events, writing articles, and editing the XProgramming.com Web site.
I am the author, so I'm rating the book three, not because that's what I think it is, but because it's in the middle. I'll see whether I can get a comment added as author or otherwise update the page when Amazon gets back to me.It appears that the online content isn't what at least one reader wanted it to be. It's chronological by date, so that readers can follow along which files changed as we went forward, and it sounds like at least one reader wanted the final version. My mistake: I wasn't expecting that.I'm not sure why -- the point of the book is to follow along on how we develop, not really to provide a handy-dandy XML editor -- but if this reader or any other wants a final snapshot of the files, they should email me at ronjeffries at acm dot org and I'll gladly send them along. And I'll see whether we can add another batch of files to the online content.Thanks for the feedback.
I learned to program back in the dark ages before books came with CDs or websites where you could download the author's code. Back then, if you wanted the author's code, you typed it in from the book. I typed in the code from many wonderful books and I learned to code that way. As I typed, I was paying attention to the code, not just mindlessly hitting the keys. While this taught me what a great programmer's code looked like when it was done, it didn't teach me how that programmer arrived at the solution that was in the book. What I always wanted was to see the author's thought process as he arrived at the finished code presented in the book.With Ron Jeffries' "Extreme Programming Adventures in C#" I finally have that opportunity to watch over the shoulder of a great programmer and watch not only his code but, more importantly, how he thinks. I love that the author is willing to show his dead ends and false starts. And then how he recovers from them. The book is really language agnostic. It's in C# but the lessons are more about programming and thinking about programming than about a specific language. I highly recommend this to all programmers, not just C# programmers.
This book is, instead, a narrative trip through developing a software project using the techniques of eXtreme Programming, writing in the C# langauage, in an effort to learn the .NET environment.
Ron Jeffries has been a leading advocate of (if not the founder of) the eXtreme Programming concept. Rather than talk more about eXtreme Programming itself (he has several books on eXtreme Programming listed on Amazon) he is using a new format in this book to get away from the heavy tutorial/lecture approach used in the other books.
He, pair programming with Chet Hendrickson some of the time, first goes out and buys some C# text books. The first step is to learn a bit about C# so he starts working on some of the examples -- I was glad to see that the first attempts (like most of my own) didn't work, and he got a not very helpful diagnostic -- this sounds like my learning a new language. Then as he says, "I fumbled around in Visual Studio a fair amount." Yup, I understand. A few dozen pages later, "Well, it almost worked, but it didn't." Been there, done that. Another few dozen pages, "Found a bug, Write a Test. But we don't know how to test that particular bug."
I suspect from this you get the idea about this book. It's got a friendly, chatty, open writing style and along the way passes along some pretty deep messages about the subjects of XP, C# and XP. I like the style, it may or may not be your cup of tea.
This is a hard-to-come-by book. I think it's especially useful for someone programmed for less than 10 years or not ever get trained by computer science. The book uses C# which I am very happy with, but it's more like "Extrme Programming Adventures" in any lanaguage.
I learned a lot from the technique delivered by the author, ex. test,test,always write a test before coding (Don't be lazy,it'll bite u back sooner or later if you don't). I can't appreciate this more after three days of practicing that I feel more comfortable to continue my three and half year fluid dynamics project now. Before doing this, I do test but I always test in "kinda of" state. Check it out, see if you code in that state, lol.
Futhermore, the way to write test for GUI application enlightens me too, 'cause I never actually write test for GUI and don't know how. If you have the same problem, the book has a solution for you.
Personally, the nice thing about the book is that the way he wrote the book makes me think he's no better than me when he's coding :) XP is not about how to design and setup the project( which I thought what it was, maybe there's another book for this), but several ways that can help you to code with more confidence without being a master.
It's a pleasure to watch a master at work. It's human nature to enjoy identifying with experts, whether you're picking up tips or just validating your own experiences. If you're a golfer, you probably love to watch golf on TV. If you (as I do) build furniture in your spare time, you'd love Fine Woodworking magazine. And if you are (as I am) a developer using the Extreme Programming methodology, you'll love this book.In "Extreme Programming Adventures in C#", XP guru Ron Jeffries lets you pull up a chair next to him as he takes a small programming project from concept to delivery. Along the way, Ron learns the C# language, pair programs with several partners, makes mistakes, hurts his arm, and writes clean, well-factored code. In short, he acts like a real programmer with a real life that you'll be able to identify with easily. You'll see Test-Driven Design in practice, and watch as a complete customer-test tool is developed as an organic part of the project.The most amazing thing about this book is that Ron checks his ego at the door. He doesn't try to hide his mistakes, but instead celebrates them as learning opportunities. The review at the end of each chapter examines what went wrong and what went right. This book validated many of my own experiences in using the XP methodology. If you're interested in how XP and TDD work in the real world, buy it now.