View Single Post
  #5 (permalink)  
Old August 21st, 2012, 08:37 AM
xcopy xcopy is offline
Authorized User
Points: 189, Level: 3
Points: 189, Level: 3 Points: 189, Level: 3 Points: 189, Level: 3
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jul 2012
Posts: 11
Thanks: 0
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by stormchaserJohn View Post
Even in the context of the fast-changing environment that is mobile development, the first chapter of what is considered to be an introductory book should not be so riddled with errors/omissions.

It is really bad form - even from a beginning Android developer's perspective - to drop text into the code without an accompanying string resource. It is irresponsible to encourage newcomers to the operating system to take such sloppy "short cuts".

Beginning Android has a long way to go before it becomes a book that I would recommend to anybody else.

The author addresses the lack of proper string resources later in the book when he says he uses a fix-it-later-approach, meaning he cuts corners during development, and cleans up the warnings later in refactoring.

While cleaning up later is a valid approach, one or two sentences early on as to what he's doing and why he's doing it could go a long way to alleviating beginners concerns about the warnings they'll receive.

The gotchas in this book are not insignificant, and they will literally pop up every few pages.
Reply With Quote