And you are here why?

So you’re building out a fairly complex component — one of those things that, try as you might, you really can’t simplify any further. Consider what happens when you start building out your tests for this component. You get all your really basic unit tests done quickly — things like • “ make sure this function returns a positive integer ” • “ validate that the user count is never zero ” and so on. The fun begins when you start layering on functionality. For example your widget’s state includes a whole bunch of opaque internal structures with a variety of bit-patterns, hashes, and whatnot — and your widget does…stuff…based on these structures. Your tests very rapidly end up containing depressingly long sections of code, all designed to say stuff like // set up my widget var widget = new Object(); widget.hash_start_section = "deadbeef"; widget.constructor_type = 1337; . . // continues forever... And that’s on a good day. On a bad day, you do horrible stuff like seriali...

Stephanie Rieger writes about Mobile Users , and largely debunks some of the most obvious arguments about what to put in (or not put in) your mobile app.  The article is well worth the reading, but to summarize Mobile users are not always on the go .  Just because its called a "mobile" phone doesn't mean that its only used when you are mobile! Think about how you use your phone - in fact I bet that you are reading this either on your phone, or as you read this on your computer, your phone is sitting right there next to it .  It is not now, and arguably never has been, only a " I'm in a hurry " device. KISS everywhere :  Given the form factors, it behooves you to design your mobile apps so that they are simple, easy, elegant, blah, blah, bah.  But then again, you should do the same for your desktop apps! Complexity isn't going away : Yes, there are some things that are just too complicated to be done easily and simply.  Thats ok, life is like th...