The Android Adventure Begins

So I've decided to get serious about Android development.  I still see it as a new technology, but it's really starting to spread its wings, and I'd love to get in on the ground floor, or, I suppose, as close to the ground floor as I can get with a technology that's been around for 5 years.

I've tinkered with some Android development over the past few months -- messing around with a prototype app at work -- but, up until now, my knowledge has come from cutting/pasting/tweaking existing code, and Googling "how do I [something] with Android?"  I've realized that this is a frustrating approach to learning any language, as you end up reading questions posed by people at the same knowledge level as yourself (close to none), but answered by people who seem to have vast expert-level knowledge, whose tips and advice fly right over your head.  I ended up with rough ideas of how to perform the specific tasks I was looking for, but I wasn't getting any closer to having a solid understanding of the Android language as a whole.


So today I went out in search of a book to help guide my way, and by "went out," I mean I went to Amazon.com (c'mon, who goes to book stores anymore?).  After scanning reviews for a while, I settled on "Professional Android 4 Application Development" by Wrox (as of this writing, the Kindle edition is $24.74).

I'm just getting started with this book, but I'm already pretty fired up about tackling an interesting new (ish) language.  Not only do I hope to enhance my marketability, but I also hope to be able to create some cool editions to my own phone.  It should be fun.

Addendum:

Since this is my first blog post, I guess I should lay out a mission statement of sorts...

This blog is intended to be an amalgam of my experiences with software application development:  musings on particular coding issues, code samples, and anything else related to development that might pop into my head.  I hope that it not only helps me to keep track of my growth as a developer, but also acts as a helpful resource to other developers who might be tinkering in similar areas.  For the record, I don't expect this first post to help anyone, except for maybe Amazon if anyone reads this and decides to buy the same book I bought.  So, you're welcome, Amazon.