Do you have an idea for a future book promotion? Post it here!
Admin notes from Jeanne (edited Paul's post because I can't insert a post and don't want my comments buried amongst all the great suggestions)
I will be e-mailing publishers with suggestions from this thread. I will not be replying to individuals in this thread as I don't want to expose information from the publisher. (did the publisher not want to participate, did the author not want to participate, is the book too old, it was already promoted, etc).
Do keep the suggestions coming though - and "vote" by clicking the thumbs . I can point to the fact that multiple people want a book/topic promoted by pointing here.
as well as the usual lucky draw winners (provided another couple of giveaway books are available),
ask the author to provide a simple theme (CD Collection, Tic-Tac-Toe etc) for people to write/submit
an Android program (with limits to submitted file size), to run in an emulator.
Author is judge, and awards books to best program/s (in his/her opinion).
That is indeed a good suggestion asked by Paul Wheaton
1. How about giving a bunch of books written on Head First Series? I think they have NOT been given much (am not very sure about it though!). And they have a very close relationship with JR/CR (JavaRanch, CodeRanch). Infact I got to know through JavaRanch through Head First Java, Servelt/JSP books.
2. Giving away books in the series of Beautiful Code, Beautiful Testing, Beautiful Architecture etc.,
3. Giving away books in the series of "97 Things a Programmer should know, ..."
For those who want to learn more about Java than they thought they could:
"Programming in Scala" by Odersky, Spoon, Venners
Learning what Scala can do on the JVM provides a whole new look on the features and some of the shortcomings of Java. I particularly liked the full chapter on equals/hashcode/compare and how easily you can make mistakes here.
Then the one book I think every Java develper should have read:
"Clean Code" by Robert C. Martin
There is no way around interpreting and adapting his straight advices in concrete situations, but all in all the book gave me a lot of hints about coding habits to reconsider.