Filed under Design

Nativist Nonsense and Idiotic Idealism

Hard to see when blinded by ideology

I very much appreciate, understand, and value design aesthetics and well built technology. I’m also an amateur philosopher in my free time, so I can appreciate ideas, ideals, and ideologies in themselves. All of this is all well and good, but what I don’t get is people who get so wrapped up in some design or technological ideology that they blind themselves to what is good apart from that. Let me give you some examples that I have heard and seen many times in my career in one flavor or another:

  • Blindly preferring some piece of software or technology purely on the basis that it is “open” or even “standards based.”
  • Blindly preferring some piece of software or technology purely on the basis that it is made by your pet favorite company.
  • Refusing to install or use some piece of software or technology on the basis that it is made by some company you don’t like.
  • Refusing to install or use some piece of software or technology on the basis that it is “open” or “free.”
  • Irrationally assuming that because some company had a challenge with a bug, virus, security, privacy, free-ness, openness, whatever, then everything that company does thereafter is tainted and to be avoided.
  • Irrationally assuming that because something is “native” that it must be better than a non-native alternative.
  • Refusing to code in some language on the basis that you don’t like it/it’s not your preferred one.
  • Prejudging a piece of software because it is built on <insert name of technology stack you don’t like>.

And there are a host of other, even less defensible positions that otherwise quite intelligent people take in relation to design and technology. Especially for people who are supposed to be professionals in technology and/or design, this sort of blind prejudice and ideology-based thinking is inanity; it is out of place, unbecoming, and simply unacceptable.

Most of us in design and technology are not paid to promote ideologies; we are paid to produce things. At the end of the day, the things that make us more productive and solve each particular problem best are the things we should be using. There are good ideas everywhere, and if we blind ourselves to them, we are injuring our careers and doing an injustice to those who pay us with the understanding that we will make the best thing for them in the most productive way possible.

Sure, you can have your preferences. Sure, you can espouse best practices and design philosophies that make sense to you. Heck, you can even advocate for them. But just don’t let those loom so large in your mind’s eye that you cannot see the good in things that don’t align with them. Don’t get so stuck on a technology or a framework or a practice or a pattern or a principle that you choose it when there are better options available for the problem at hand. Everything is not a nail, no matter how superior you think your hammer is. Don’t let your ideals become prejudices that instead of fostering awesomeness rather become a roadblock for you and those you work with and for.

And this extends, importantly, to people as well. Don’t treat those who don’t share your ideals with disdain. Don’t imagine for a second that because you adhere to some ideology (“craftsmanship” or “big ‘D’ Design” or whatever) this makes you more professional or better than they are. I’ve even heard people judge other professionals by when they purportedly clock in and out, as if having a healthy work-life balance somehow makes you less professional or capable!

In our line of work, it is the output, the products of our efforts, that matter most, not how we get there, and there are most definitely many paths to good outcomes. The judges of these outcomes are our clients, our customers, our markets, our users–not us. And the primary criterion in judging a good outcome is most certainly not how well our work aligned with any given ideology, however well-intentioned it may be.

Tagged , ,

Antipattern: Forms Over DB

Any experienced business software developer knows that CRUD makes the world go round. For those who don’t know, that stands for Create, Read, Update, Delete. It’s the bread and butter of many business apps, the transactional ones that exist to, essentially, manage business data. Oodles and oodles of apps exist to do just this, and that’s it.

It’s fine, in and of itself, because it works, as a bare minimum. It’s also fairly boring to code,as a developer. It gets tiring writing the same code over and over and over again. So, these smart folks who get bored with basic CRUD start inventing ways to make their jobs more interesting.

What this looks like are things like auto-generating CRUD forms “scaffolding” from a database. It looks like ORM–object-relational mapping, where the objects are similarly generated from a DB. And all sorts of variations on these themes.

The problem is that in an effort to not get bored, to not “waste time” with boilerplate code, these solutions miss the mark. The intelligence and creativity of these highly skilled individuals is being squandered. The essential problem lies in the requirements themselves.

When you conceive of software as, essentially, a portal to edit database records, the potential of that software is immediately and fundamentally warped and diminished. It presumes an antiquated interaction model, one in which the database is some angry pagan deity. The people must bring their offerings of information, feed it to the all powerful database, hoping that at some later point, they can return and request some meager insight from the oracle (pun intended).

It is an immensely impoverished and impoverishing view of how software can help people do business. We need to move beyond these primitive interaction models. We need to understand the flow of business activities–from a human perspective. Instead of looking for points in a business process into which we can inject these artificial, software/database-oriented data offerings and petitions, how can we make software feel like it is part of what people are trying to accomplish? Their goals are most assuredly not to create, read, update, and delete records in a database. Their goals are to achieve some human end, and they put up with CRUD type interactions as a means to an end.

The closest thing I’ve seen in the dev side of things to a more human-oriented design was SOA. At least it attempted to frame the design in terms of what people were trying to accomplish. Domain driven design also heads in the right direction, and to some extent, so does “object thinking” that tries to focus more on behaviors and less on data and properties.

But a more robust approach to understanding and formulating a high quality software design is one that follows one of the many UX/Design approaches. There are many, many resources out there for devs and BAs to learn how to improve their design process and “learn UX”; I myself have written much along these lines and given many presentations. I tried to distill this into practicable principles recently in my UX for Devs Manifesto. My company has released a currently free interaction design tool that any dev or BA should be able toque kilt pick up and leverage in an improved design process.

There’s no good reason for us to be continuing with the Forms Over DB antipattern today. In addition to warping software design from the get go, it also leads to other “efficiencies” like auto-generated validation with its inscrutable error messages and subpar input interactions. The good news is that there is a better way, both to get to a better result and to offer a more interesting, more intellectually challenging software design problems that keep us from getting bored and wasting those energies on ways to more efficiently create poor user experiences. Further, we are more empowered today than ever to craft awesome, well-designed software thanks to the technologies and tools available to us today.

Just say no to this antipattern. Work with your managers and BAs to fix the status quo of requirements that engender this antipattern. It can be done, and everyone will be better off for it.

–written from my iPad mini in a session on scaffolding ;)

Tagged

Flatland? No Thanks

“When you launch an app on your mobile device, the device essentially becomes that app.” via Max Rudberg – ✎ Flat UI is not the only way forward

This is a great, keen observation, and it correlates to why having clean, minimalist design makes a lot of sense for the hardware of mobile devices. These are windows onto many worlds. As such, for them to blend away into near invisibility is precisely what they should do–so that you can immerse yourself in any one of those worlds without distractions from the window itself. The more invisible the window, the better.

But for the world experienced through the window, it would be as if you were forced to live in Flatland, if you were limited to flat, minimalist design. Even though it is a deception, it is a beautiful deception for a piece of software to make you truly feel you are a part of the story it is telling, the story it is helping you to become a part of.

Tagged

Yes, Ditch Traditional Wireframes, But Not for Code

Just Say No To CodeI just ran across Ditch Traditional Wireframes in UX Mag. I agree with the basic premise–that static, especially high fidelity, wireframes should be eschewed, but the conclusion I draw about what to do instead is a bit different.

The author of that article, Sergio Nouvel, propounds the wonders of just jumping right into code by doing HTML-based prototyping after nailing down initial concepts with other low fidelity options. The problem is that Nouvel does not identify the drawbacks from such an approach:

1) Despite the relative ease that frameworks like Bootstrap and Foundation provide, jumping into code has the immediate effect of warping the designer’s mind. I don’t care how disciplined you are, when you start dealing with code, your brain is forced to start thinking from the code perspective. It is not acceptable to switch at the interaction prototyping phase from a human-centric focus to a code-centric focus.

2) Especially in non-WYSIWYG environments, you are forced into imagining what tweaking this bit of markup, CSS, or JavaScript will have, then you do it, and then you verify it. And you often find it’s not quite what you had in mind, and repeat. With that, you end up wasting a little time here, a little time there, a little time everywhere fighting with the technologies just to do the simplest things.

3) It forces the designer to learn to code. That is a double-edged sword, as I discussed not long ago in To Code or Not to Code.

4) To be truly easy to maintain and change takes a LOT of planning up front. Even developers struggle with this, and they’re all about reuse and minimizing effort for changes. To pretend that just using code means things are automatically easy to maintain is just wishful thinking. Sure, maybe changing a font color, but changing shared navigation, layouts, etc.–things that are far more pertinent to rapid design iteration–are not easy changes in code. At all.

5) Interaction prototyping is not the same thing as production coding. To pretend that the code a designer writes in a prototype is going to be good for the real product misses several key considerations:

  • Devs are notorious for being picky, and rightly so, about their code (see the last point about code reuse). The chances they’ll just run with prototype code are quite slim, especially if that code relies on prototyping frameworks.
  • The focus of a good interaction prototype should be the interactions, not to have clean, well-layered/encapsulated/maintainable production code. If you use code for prototyping to have “build the real thing,” you’re missing the point of interaction prototyping.
  • Using HTML prototype code as production code only applies, and only sometimes, for Web apps, and simple ones at that.
  • What about statefulness and data? Are you really going to spend time on that in your prototype?  Anything beyond a basic informational Web site needs this sort of thing.

6) Worrying about responsive design at the interaction prototyping phase is premature. We’re in the higher point of the hype cycle for responsive design. Yes, it is nifty for some design needs. But it is hardly a panacea, and more importantly, it (like code or tech) should not be the big thing you’re worried about when doing interaction prototyping.  Why? Because from a user experience point of view, it’s just not that important.  Many of your users will never know if your site is responsive, and very few will care, as long as they get what they want from you.

7) How are you going to share your prototypes? Using HTML means you’re going to need to secure a hosting place, deploy it, and ensure it is accessible for people. And you have to keep updating that. One more thing you have to learn to jack with just to get some design ideas fleshed out and tested, one more thing in your way when you should be simply focused on exploring and evaluating design concepts from a human perspective.

So what should you do instead of static wireframing? Why interactive prototyping, of course! :) Before you shake your head and say it is too hard or too cumbersome, I suggest you try Indigo Studio. Full disclosure: I had a hand in making it, but the reason we made it is because we think it addresses some real needs, such as:

  • The need for rapid exploration of design ideas from a user-centric perspective.
  • Being able to do rich interactions and animations without worrying about code or learning to code.
  • Integrating stories and human contexts into your digital design.

And guess what, Version 1 is totally free, forever.  There is no obligation, no time bomb.  So yes, definitely, ditch traditional wireframing, but not for code. It is good for some needs, but when you’re doing interaction prototyping and design exploration, that’s not the time to saddle yourself with all those ancillary concerns.

Give Indigo Studio a Try!  I recommend watching the videos–they give a good idea about how Indigo Studio is different and tries to address these needs.

Tagged , ,

BookBook Initial Thoughts/Review

For some time, I’ve been thinking about having an iPhone case that looked like a book. This is, in part, because of the looks you get at church if you use an iPhone, like I do, for devotional material (prayers, in particular).  I’m also a history geek and love the “old book” aesthetic, so I thought I’d give the BookBook a try.

The, theoretically, nice addition with this one is that you can use it as a wallet as well.  So, I just got mine in the mail yesterday, and here it is.

BookBook Side

BookBook Top

As you can see, it doesn’t stay closed on its own very well.  Now, I generally try to keep the bare minimum in my wallet anyways, but I had to skimp even more.  We’re talking: driver’s license, health insurance card, AAA card, one credit card, and one debit card.  I also have maybe 5 bills of cash.

Even though it fits, you can see it doesn’t really fit well.  That said, with some pressure, it almost fits in terms of the binding, i.e., it is about as thick as the spine of the book.  It is and feels fairly bulky in my front pocket, where I always keep my phone.  But it’s not uncomfortable.  It is noticeable even when standing, and I don’t wear tight pants. ;)

Things I like:

  • The look – obviously, that’s my main reason for getting it. It looks great, just like an old book.
  • The feel – it feels (and I believe is) real leather. Also, for reading emails, etc., it’s kind of nifty to hold it like a book.
  • The smell – it smells like leather.
  • Eliminating separate wallet. Now I just need to get rid of my keys. :)

Things I don’t like/will have to be tolerated:

  • Bulkiness – as shown/discussed above. I don’t think I can get away with much less in the wallet side, and even without that, it is still fairly bulky itself.
  • Using as a phone – I don’t want to wear the spine/binding, so for me, the only option is to pop it out for this. It’s not hard to get out, but still, it is weird to have to take it out to make a call.
  • Difficulty of access – this is extension of the phone thing; it is not exactly easy to get cards out, or cash, or put it back. (It is leather, so it should break in a bit/get easier.) Also, if you want to switch to left hand or use both to type, it’s a bit awkward for sure.

At this point, I’m not really sure about it. It’s the first of this kind of phone case I’ve tried, and most of the issues have to do with the class of case, rather than this specific one, which is quite snazzy/feels well made.  Will try it for some days at least and see if I can adapt w/o too much bother.

UPDATE 2 January 2013:

I’ve been using it for three weeks now, and I’m more happy with it now than I originally was.  Here are pics from today.

BookBook Vintage Brown from Front

BookBook Vintage Brown from Back

BookBook Vintage Brown from Open Side

You can see there is some wear. Twelve South says, naturally, that this wear just adds to the character. I’ll say that at least it doesn’t take away from it. Looking like a vintage book, you might expect it to show some wear.

Now, about my main concerns:

  • Bulkiness – I did use a wallet app to get rid of one card. It still sits open (as you see). This isn’t really any better or worse, but I will say that I have come to really appreciate not having to carry a separate wallet. This is more convenient for a wallet, too, as it is usually more easily accessible (e.g., sitting in the car in a drive thru–it is easier to get to because I often either have it out or have it in my front pocket).
  • Phone – It is a bit awkward, yes. But maybe less so than I anticipated. I find myself using speakerphone when I can, but in situations where I need to answer normally, I’ve gotten adept at holding it open to my head.  Probably looks a tad silly, but for short calls, I do that.  If I intent to talk for a while, I pop it out, which once you get the technique, is fairly easy to do. I have a couple accessories that don’t want the case, and I regularly pop it out for those as well.  No biggie, but it is as expected a tad more cumbersome.
  • Access – as mentioned, it is actually easier and often faster to access my wallet than before. As expected, the leather did break in, so the cards come out easily enough now, and cash isn’t hard to get either. The big win in this aspect is how quick I can get to the wallet stuff.  And it is a bit easier to show my ID to people as well.

About the pluses, well, the main thing is that it is really quite nice to hold, to look at, and to smell (though of course it is less smelly now). I’ve had quite a few compliments on it, even some jealous comments. I have found it is actually easier to hold for taking pics/video in landscape–the case gives you more to grip on without worrying about blocking the lens. As one person pointed out, people endure far more annoying things than the drawbacks of this case in service to aesthetics/style, so I can’t really complain. I find myself quite satisfied with it overall, and mostly I don’t think about or mind the cumbersome aspects. I do enjoy it and am keeping it as my case for the foreseeable future.  As always, your mileage may vary.

Installing Nest in a 100-Year-Old House with Radiator Heating: A Guide/Review

Nest Learning Thermostat on Amazon.com
Just thought I’d share my experience with a great product–the Nest Learning Thermostat. Given that I own an over 100-year-old house with radiator heating (and no central air), I was dubious about this working for me. After doing a fair amount of research, it came down to this one or the ecobee. The ecobee (main model) was more expensive and, frankly, just doesn’t look as good. Let’s face it; the Nest has been designed, by real designers, and it is obvious. Other thermostats on the market are clunky gear head boxes.

I have noticed that things that appear to be well designed often are. Not only that, if people go through the trouble to do great industrial design, they usually at least try to do great software design, and maybe even full on service design, and in this, the Nest does not disappoint. Everything from learning about the Nest ahead of time on their Web site to the out-of-the-box experience to the install to the setup to the ongoing usage (with apps for devices and a matching Web control site) has been designed, and designed well (and kudos to Amazon for 1-Click Prime ordering and one-day delivery–a day ahead of time).This is just one of those products where they have really pulled it off. And who’d have thunk it–for something as “simple” as a thermostat.

I used their online compatibility checker to verify that it’d work with my system. I have one of those old-fashioned Honeywell round thermostats.

Honeywell CT87K Front

But it turned out that after popping off the front, it was a relatively new model, the Honeywell CT87K, made for heat only systems.

Honeywell CT87K Inside

See the old wires?? Wrapped in like cloth or something. I told you it was an old house. :)  Anyways, zooming in I was able to see the R and W letters by the wires, so I could plug that into the compatibility checker, and voila, they said it was good, and they even give you a wiring diagram up front to show how you’ll hook it up. Pretty snazzy!

I thought I’d give it a whirl, and so I clicked the little 1-Click button, and a day later (two days, ahead of time, thanks to Thanksgiving), it shows up. (Even the box is kinda cute.)

Nest Box

You take off the plastic wrap, slit the tape holding it shut, slide off the cover, and open up.

Nest Unboxing 1

Lift out the Nest (has a little plastic circle on it), lift off the first layer, you see the booklet, lift that out, and you have the next layer of goodies.

Nest Unboxing 2

You see their chubby little screwdriver, the Nest back, and two mounting screws.  Slide out the booklets; there are three.

Nest Unboxing 3

You have the install guide, the setup guide, and a “concierge” card (if you need to bail on a self install, a nice security blanket). What you see above is the first page, that tells you high level steps for uninstalling your old thermostat. What’s cool about it is the built-in stickers to label your current wires as you take them out. Given the variety of systems out there, and no standardization on colors, this is the only way to do it. So be careful! For me, of course, it was simple–two wires. But I labeled them anyway!

BEFORE MOVING ON, CUT THE POWER TO YOUR THERMOSTAT. For me, the thermostat wires come from the boiler, so the circuit to break was the boiler’s circuit. I verified this using my handy dandy Greenlee GT-16 Adjustable Non-Contact Voltage Detector, which I bought some time ago for other amateur electrician work on this old house. I can detect voltage in the air on the max sensitivity, so what I usually do is check it before trying to disconnect. Dial it back until it detects only when you’re near the hot wire. BTW, don’t take my word for it–I am not an electrician; YMMV.

Nest Install Voltage Detector

Now that you’ve cut power, you can label the wires safely.

Nest Install Label Wires

Even though the old plugs only say R and W, Rh and W1 were the only/closest option, and it matched the wiring diagram from the compat checker.

Now, niftily enough, the screwdriver they include has a small enough head on it to reach in those holes on the right and unscrew (loosen) the wire clamps. Simply pull them out at that point. I cheated and used my drill to quickly remove the two screws holding it onto the wall. I carefully pulled it off the wall at that point, to avoid ripping any extra paint off (the painters got mighty close to it). It revealed the green wall beneath the new cream paint. Here’s the whole old thermostat.

Nest Install Remove Old Thermostat

It probably took you more time to read this than it did to get the old one off.  Now for the install. I walked the Nest’s back over and looked at where it would install. The hole is in the center on the Nest; on the old one you can see it was to the left. Bottom line, this meant I couldn’t cover up the old green with just the nest, and since I didn’t have any putty or paint handy, it was back to the Nest box for the decorative backing plate. Lift up the last layer in the box to reveal the backing choices; they have an option to mount on electrical boxes as well. I just needed the pretty plate to cover the ugly wall stuff.

Nest Install Backing Plate

Again, I cheated with my cordless drill (Makita 18V Lithium Ion, BTW, if you need a recommendation).  Would be more annoying (not impossible) to use their included screwdriver.

Nest Install Back

Now, I used my old, somewhat crappy level to install this. It didn’t quite come out straight, as you can see.  Then I noticed the built-in level, and also, the screw holes have a little play, so I loosened the bottom one and realigned using their level. Hey, look, it also aligned with the nearby wall edge at that point, too!

Nest Install Back Leveled

Oh yeah, I plugged in the two wires into the matching slots. One of the cooler but maybe non-obvious features of Nest is that it runs fine on your 24VAC line. Many new/digital thermostats require a “common” lead that provides dedicated power. Not so with Nest–no extra wiring needed. Even my ancient two-wire system works fine with it!  Just use their compat checker to verify yours.

My wires are tough (they were made back when men were men, wires were wires, and little furry creatures from Alpha Centauri were little furry creatures from Alpha Centauri); they are not huge but not thin either, so I used needle nose pliers to straighten them. A more obsessive person may have grabbed some electrical tape to cover up more of the exposed wire. Me? I don’t sweat the small stuff. It will soon be covered up.  We’re almost there! Next step, grab the pretty Nest and plug it on.

Nest Install Done

NOW, you can go flip the switch back on. My breaker box is in the basement, but no worries, when I came back up, it was waiting for me.  Time to setup. You say “Hi” to it, and confirm your language, then on to the coolest part of the gadget–it is Wifi connected. Seems to have a decent antenna, too.

Nest Setup SSID

I also thought the interface for entering the password is cool. The Nest slides so smoothly. Feels solid, and dialing it to enter the password was strangely reminiscent of using a rotary phone. (Yes, I remember using them, although they were definitely on their way out by that time.) Hello, nostalgia. And it wasn’t that hard either. They seem to have put thought into how fast you turn, inertia, and that sort of thing. Nice.

Nest Setup Wifi Password

After a short connecting message, it confirms, we have lift off!

Nest Setup Wifi Connected

Just a few more steps.

Nest Setup Steps

BTW, I glanced through the setup manual. It is super thin and easy to follow. You don’t really need it though at this point–just follow the prompts. After confirming I only have heating installed, it just needs to ask a few questions about it.

Nest Setup Heating Source

(For the record, I have oil. sigh. Maybe someday it’ll be different.)

Nest Setup Heating Type

Radiators, yup. That’s us. I had NEVER seen them in person before I moved up here to NJ. But I like them a lot better than forced air, I have to say. I like the feeling of the warm, radiant heat. When you keep the house cool-ish like we do, forced air sometimes feels more like air conditioning than heating–blowing around 66 degree air. Radiators always feel warm, reminding one of a fire. (And I love fires!)

A few more questions–zip code and number of thermostats. Now I get to my favorite question. When was this house built?

Nest Setup House Age

What? No 1910s?  Come on!

Next up, naming this Nest; wish I could do a custom name, but they just have some preset to pick from. Ah well. Can’t have everything!

Last, it asks a couple simple questions about temps and lets you know it’ll try to learn/calibrate for some time.  And.. we’re done!

Nest Setup Done

As before, it likely took you longer to read my account than it will to set your Nest up in real time. In fact, I bet Nest is annoyed with me because this may make it seem more complicated than it is. :)  Really, we’re talking <30 min end to end, and it felt great and easy!

At this point, I was pretty pumped, because I wanted to go control it from my phone.  But first, to the Web site.  I quickly signed up, and it detected the nest on the network. Too cool!  I walked over to it again, and it said this.

Nest Setup Added Account

Too cool!  In no time, I was managing my thermostat remotely.  THE POWER!!!

And the app is nifty. It seems to gradually reveal complexity (another great UX principle). Just tonight I discovered some new things that weren’t there before. Still, it is quite simple and pleasing. I like how it incorporates local conditions in the background.  For instance, now it’s like so.

Nest Control Home

I won’t bore you (more) with all the settings and stuff. The interface is quite nice and, in my estimation, easy to learn and use. And hey! Will you look at that!? I guess you can have everything–it let me rename my thermostat here.

Nest Thermostat Control

Note that when you hover over it, you can simply click the up arrow or down arrow to increase/decrease your thermostat setting.  You get the same basic interface on the phone and tablet (I use iPhone and iPad, FTR). There of course they smartly don’t rely on hover to see the up/down arrows. ;)

I am a little obsessive. Sometimes. About some things. I try to fight it, but it gets me sometimes.  I quickly set up a schedule (even though it wants to learn it by you turning it up and down). I mean, I don’t want to run downstairs in the morning to turn the heat up–I want it done for me! This is a minor criticism, but I guess it works for “most” people who wouldn’t otherwise set up the schedule.

In the Web interface, this is easy enough. Add a setting, then copy and paste it to the other days. OMG. Like, I programmed the three thermostats at my last place, and what a friggin pain!  No wonder they say 90% of people don’t do it.  I dreaded changing the temps, too, cuz it meant clicking and switching through about 100 fiddly switches.  This took me 30 sec.  Wow.

Nest Schedule

And yesterday, I discovered my new favorite feature–the energy records. I can see my obsession will not soon end.

Nest Energy

You can selectively drill into daily details to see just when Nest was powering on that monster of a furnace against your schedule for the day.  I think I’m in geek-homeowner love!

Now, time will tell if this does help me save money. I can’t see how it won’t. I mean, last winter (our first in this old house), I just left it on a constant 66-7ish setting on the dial, more or less. If nothing else, being able to have it turn down during the evenings should save a good chunk of change.  And considering how much this old house costs me per month to heat, trust me, in like two months it will probably pay for itself.

So that brings us to the final consideration. Is the Nest worth $250? Well, from the research I did, learning thermostats can save 10-15% on average. You can do the math based on your usage. But that’s just part of the story. This is one grand toy, after all, no? :)  So a great toy that can save you money?  Is it worth it?  I think so.

If you’re on the fence, I strongly suggest going for it. It’s awesome. Go order the thing, yo! (Don’t forget to check your compatibility first.)

P.S. Nest didn’t pay me for this review. I’m just totally psyched about it. It took probably 6x the time to put together than installing it took. (Don’t worry–I was watching Burn Notice in the background with the wifey for most of it.) But if you use my links to buy, I might get some small Amazon affiliate commission.  So that’d be a nice thing if you found this helpful.

Tagged , ,