Forthcoming: Pro Ruby

Apress has listed a new Ruby book, Pro Ruby, among its forthcoming titles.

Pro Ruby shows how to combine Ruby and agile methodologies into a unified, powerful package.

I do have a special interest in this book, because I'm writing it. (Which is why I have blogged less than usual lately.)

I don't want to give anything away prematurely, but I can tell you two things about the book:
  1. It does not have a Hello World example
  2. There is a sample application, but it isn't an online shopping application
There will be some time before Pro Ruby hits the book stores. When it does, I hope you like it.

Comments

Kallokain said…
You are first on the reviewer list. I've only written about a third of the book yet though, so there will be some time before it is ready.

Could you please send me your email address, so I can let you know when the book is ready?
June 17, 2006 8:56 AM
Anonymous said…
Well,I wud love to be on the list as well..subramanyam86@gmail.com
July 08, 2006 1:16 PM
gnupate said…
Henrik,
congrats on the book. I noticed it on the APress 'Rails Roadmap', but somehow didn't connect you with it.

Good luck!
August 02, 2006 9:09 PM
Anonymous said…
How's it going? I noticed that APress doesn't list it anymore... I hope you'll get it finished!
May 15, 2007 4:50 PM
Kallokain said…
APress dropped the book awhile ago. When my wife and I got a son last August, my writing speed dropped to virtually zero for awhile. This made APress drop out.

I think they had also begun to realize that the book they had contracted me for wasn't, and never had been, intended to be a book about Ruby programming. It was intended to be a book about Ruby projects.

Yet another factor was that APress uses a functionally organized production process. This does not mesh well with the more flow oriented process I wanted to use to write the book. (Using a functional process to write a book about how to use flow oriented processes was frustrating to both me and APress, I think.)

I am still working on the book, but I am in the process of reorganizing everything. To make the book shorter and more focused, I am dropping the Ruby parts, and focus on the methodology. (There might be a Ruby book if I ever get this one off the ground.)

My writing speed is still very low. It has gotten a little better though. I ditched the word processor APress wanted me to use, so I can write without getting upset all the time. (I am using TextMate and Lout. I would have preferred FrameMaker, but my Mac won out over my PC. Using Lout is a good learning experience though.)

I have also learned to coordinate being a writer and being a daddy. The daddy bit has the highest priority, so don't expect the book to be ready anytime soon. I might publish excerpts though.
May 22, 2007 8:23 AM
Post a Comment

Popular posts from this blog

Waterfall vs. Agile: Battle of the Dunces or A Race to the Bottom?

Image
The major software methodology wars since the mid 1950’s. Someone was wrong on the Internet, so here we go… In a recent HBR article, It’s Time to End the Battle Between Waterfall and Agile , the author sets up a false premise: There is a war between Waterfall methodology and Agile. The war must end. And finally, you can combine the approaches to get the best of both worlds. This sounds good, but the article is based on a misunderstanding of both Waterfall and Agile. Also, there is no war between Waterfall methodology and Agile. There can’t be, because Waterfall methodology does not exist! Waterfall is a name for large projects that failed in the 1960’s. Waterfall was never a methodology, but a failure to apply the methodologies that existed back then. As I will show towards the end of this article, at least one of the “successful” Waterfall projects mentioned in the HBR article was neither successful, nor a Waterfall project. I got invaluable help from Alistair Cockburn. He fact che...
Read more

Performance Evaluations, Business Strategy, and Agile Methodologies

Image
It is performance evaluation time in many companies. This can be stressful, both to the people being evaluated, and the people doing the evaluation. In companies adopting agile software development methods, the tension can be extraordinary. Individual performance evaluations run counter to agile philosophy, which emphasizes team performance over individual performance. However, managers and corporate leaders need to take a few steps back, and consider the impact performance evaluations have on the organization as a whole. Especially now, in the midst of a recession, it is important to look at a companies current policies to see if they can be improved, or if they are actually holding the company back. So, how can a manager evaluate policy? Performance evaluation policies can serve as an excellent example. I'll confine myself to discussing the so-called ‘rank and yank’ methods. These are performance reviews were employees are ranked using a forced ranking system. It usually looks so...
Read more

Agile Requirements Structures, Part 1

Image
If you have worked in large Agile projects or programs, you may have noticed that there is often quite a bit of confusion about requirements, what the requirement types are, their purpose, how to write them, how to use them, and above all, what not to do with them. There are many causes for this confusion. Here are some of the more common I have seen: Nobody in the organization has read up on the requirements model it is using, so everyone makes their own interpretation. The organization deviates from a standard requirements model, but nobody knows which standard model the organization is deviating from, and/or there is no agreement about how they deviate from it. The organization has not documented its own requirements model very well. The organization mixes two or more different requirements models, often without realizing it. The organization has documented its requirements model, but finding the documentation is an epic project in itself, on par with when Henry Sta...
Read more