As an individual I can decide which platform I would like to target with my
shiny new application, but when working for a company we have to target both
industry leaders at the same time. Although I like a good challenge, I am
really glad the mobile world now only consists of iOS and Android.
When I first started looking at building consumer applications, Blackberry
was still in the picture. My enterprise mobile experience consists of all
Microsoft technologies, but that was in a different lifetime using Windows
CE, Pocket PC, and Windows Mobile.
This book is a great book for looking at how some of the most commonly used
functionality compares across the Android and iOS environments. I have listed
the table of contents below to give you an idea of what topics are covered.
Part I: Overview of Mobile App Development
1. Why Mobile Apps?
2. App Design Issues and Consideratio... (more)
As an enterprise and software architect the one thing I hate most about my
job is documentation, yet the importance of doing documentation on sizable
projects is what I find myself preaching about the most.
One reason I understand the importance of documentation is that I came from
an electronic engineering background. As an electronic engineer 93% - 97% of
my time was consumed doing proof of concepts and documentation. Almost all of
that time was documentation.
It was just my luck that my boss was an English grammar teacher before moving
into engineering. My documents came back v... (more)
Finally a book from an industry leader that has the guts to write about the
real world of Agile software development. If I had to pick one word to
describe this book, it would be 'truth'.
This book is going to raise the blood pressure of some of the Agilists out
there. If you think you may be one of those, do yourself a favor and keep at
the forefront of your mind that the author points out all the good in Agile
too. He is not telling a one sided story. When reading a strongly opinionated
book like this, we tend to only see the things the author is pointing out as
our flaws, or ... (more)
When the agile movement re-cast the roles of the SDLC they did so with small
projects as the baseline of their experience. A typical minimal SDLC method
includes subject matter experts (those who execute the current workflow
activities), a Project Manager, a Business Analyst, a Software Architect, UX
specialists, Developers, DBAs, and Testers. A Scrum Team consists of a
Product Owner, the Development Team, and a Scrum Master. The typical SDLC
method responsibilities for activities, and the skills needed to get them
done, went from 8 roles down to 3. For small projects that is gre... (more)
As with Nathan's book WPF 4 Unleashed books, this book is a pure pleasure to
read. It is in full color, the content is laid out in an easy to read style,
the author's writing style makes it easy to read, and the content is all
valuable. There is no fluff like you find in a lot of the books written
Part I of the book starts out with an awesome chapter on the anatomy of a
Windows store app and then has a great chapter introducing XAML. The book is
broken down into a total of 7 parts. I have listed them below along with the
chapters they contain.
Part I: Getting Started