Readit NewsCurrently waiting for a new hip, because for some reason I've worn mine out too soon.
Now, I won't say that the fact I'm in pain 24/7 isn't making me sad, but the fact that I don't come outside as often anymore really is not helping.
You want the ability to look at 4-5 sources, vet them, and draw your own conclusions.
Even if your HOA is not gated and doesn't have a clubhouse, not a pool, it is the HOA that is responsible for maintaining the streets and parks.
But... that is normally paid for by tax money. Yet the home owner's taxes in those communities are not lower. So the city is double dipping.
You will not be able to just point the radio in your zigbee stick at your meter. As far as I know, the only device that is even blessed with the keys to do this is the Rainforest/Eagle device. You _still_ have to get permission from your utility, though. PG&E has a web page where you plug in the MAC for the radio and submit it. Only some customers on some rate plans are allowed to access this.
I gave up and went with a power monitor that’s installed in the main breaker box. It uses CT clamps on each circuit to give very accurate and timely readings.
I'll call APS (Arizona) tomorrow to see what is possible.
My electricity reader supports ZigBee.
My provider knows minute by minute my consumption, yet only providers it on THEIR website, in a way that is useless to me.
When you need to be precise, you specify a time and a zone.
When your application has users in different geographies, you need to be precise.
Displaying the date attached to a time is a presentational convenience. Only the time is real.
You celebrate your birthday on January 5th, whether you're in Hawaii or New Zealand.
You might get texts from friends & family earlier and later than that.
Outlook had a funny bug where when you stored a birthday on a certain date (which is then an all-day event), it would shift that all-day event by x-hours when you changed timezones.
But it'll take you very, very far for a very, very long time.
I'm probably doing something wrong, but in my experience the amount of magic that Ruby allows (and RoR and library creators use), create for situations where updating code is extremely risky. It can be mitigated by having an extensive testing-codebase, but those only tell you if your assumptions still hold up, they don't help you in fixing your issues per-se.
And half of these tests are checking that your invariants are being upheld, things that you get for free with statically typed languages.
Your energy-score had to be below a certain limit (where 0 is neutral).
Now, we wanted to install AC, but that would actually bump our energy-score, because the idea is that if you need AC you didn't insulate enough.
Except... when you have such thick walls the house overheated starting mid-spring until mid-fall.