New book from Erlang Training

So, the guys Erlang Consulting and Training are making a new book.

and on the erlang-questions mailing list:

On Feb 21, 2008, at 1:50 PM, Francesco Cesarini wrote:
Our main goal is to cover Erlang in depth. Make sure that newbies struggling with recursion can easily understand it or developers being exposed to pattern matching for the first time use it optimally. The contents of the book are pretty much outlined by the introductory Erlang courses Jan-Henry and I have been giving in the last decade, and based on the knowledge and experience gained when teaching. We know [where] students struggle...

On Feb 21, 2008, at 4:29 PM, some guy wrote:
It's just that, no matter how good it is, with Joe's book already out there - it's not going to be a must read for me.

On Feb 21, 2008, at 3:17 PM, someone else wrote:
Another book on just the Erlang programming language would not find a place on my bookshelf.

These responses kind of made me upset.

I applaud Francesco, and Jan-Henry in getting another book out there. Obviously they have learned from their history areas where new comers to erlang have troubles, and they're making a book to plug that hole. They are of course asking you to look back on your experience coming into erlang, think about what concepts you had troubles with and let them know, this would both help confirm the topics for their book, and possibly give them new topics that are perhaps different than they have been exposed to because they come from people
who don't buy erlang training courses.

Just because you don't need the book now doesn't mean you dont' have something to add.

And sure, we all have frustrations about the OTP stuff, it seems like it might be very very good, and then again it seems pretty opaque. I encourage anyone reading this who knows more OTP to publish more stuff about it.

[ I know I'm calling myself RoscoeOTPColtrain, but right now I'm more roscoe than OTP, but perhaps I'll get there. ]

As a scripter in the internet era I've always looked for high level tools that help me build scalable reliable systems as quickly and as error free as possible.

As a manager I've grown to look for tools that help reduce the errors caused by teams of varying skill level trying to make deadlines that have little basis in reality.

I believe erlang is a good fit. As mentioned on erlang questions list It's missing libraries, [ we all should be addressing this. ] it's missing the ability to share code easily amongst the community. [ erlware guys are trying to address this. ] It's missing a lot of depth of documentation especially with respects to OTP.

"see the OTP design principles", is it's own running gag around my office. "Hey, where is the coffee maker?!?" "See the OTP design principles."

Erlang provides some great tools to help regular code monkeys do great things, with less errors. It comes at a cost of learning some interesting programing paradigms which of course seem trivial to elitist programing apes.

So, being a procedural and sometimes OO script monkey for most of my life. [ the joy of programing being denied to me cause I always end up managing. :) ] I found once I bridged the concepts of erlang I totally love it. I feel that there are plenty of others out there who are like me that could also feel the same way.

and last, quoting yarivs "damn, I love pattern matching"