85 karma · joined July 29, 2009
Whenever a lock fails, step one or two or three is replace the batteries. That's 4-6 batteries per lock.
As a maintenance/security procedure, once every couple of years, every battery in every lock in the entire building is replaced. Doesn't matter if they are dead, weak or brand new. That's hundreds/thousands of batteries.
That's a lot of batteries. And Duracell has multiple levels of "pro"/"industrial grade" batteries. We buy them by the case.
I'm sure the markup on consumer batteries are huge, but I'd also think the commercial use of double-As must dwarf the consumer market. Smart buy by Warren is my guess.
What's needed in this space is a door lock that winds itself much like a "perpetual" watch. Something that takes the mechanical energy used to turn the door handle and turns it into stored energy that can be used to read the card and unbolt the door.
And there you go. Make this thing :)
http://www.presidency.ucsb.edu/ws/index.php?pid=3731
Of course, he could never use the term "sperm whale". But this is what led to the Endangered Species Act that granted the whales a reprieve. Lang's invention was only a reaction to this. It's still a good read.
google translate: http://translate.google.ca/translate?js=n&prev=_t&hl...
It broke. You fixed it. But, "Can I expect this to work again?" "Reliably?" All I heard was that it was broken.
It sounded a lot like, "something broke, it took a long time to fix."
http://www.novell.com/news/press/novell-unveils-real-time-co...
"You superimpose the notion of cloud on a series of related cloud values." Whoa!
http://blogs.phoenixnewtimes.com/valleyfever/2010/04/correct...
Once in a while it was simply, "Yes, we can do that. No, I don't know how much it's worth. Let's do it and figure it out later." And, with people who had confidence in my work, there was never a problem with this approach. I was often surprised at what people would pay. And as the article mentions, I would never use this approach with someone new or a large enterprise. But with familiars, this always worked out OK for me.
Fascinating to see this model applied to untried, almost purely intellectual work (code).
As with renovations, where you're often busting you're ass against someone with a pickup truck looking for beer money for the weekend. Working with code pits you against every chump with a computer. So how can you differentiate yourself?
Being able to say, "Hey, no problem. I can do that, We'll square up on Monday." is one way. Weekend warriors won't do that.
Sorry to hear that you're stuck on Apple usability, but we've moved on.
I've been using this Mac OS X client for quite some time. It's everything I want in a desktop client. It has become rock soid and is slowly but steadily improving and adding features.