51–60 of 64 posts
i wanted to make one of these but in the form of a watch you wear on your wrist. its interesting how some people are fascinated with these kinds of countdowns and others hate looking at them. me and my other cs buddy both think its interesting -- he has the tim urban poster on his wall. another friend of mine doesnt even want to look at it.
when you see something that often (daily) you could think it is real (for the good or the bad).
ATmega's EEPROM has a lifetime of 100k write/erase cycles. The program stores current time every 10 minutes, giving it ~2 years of lifetime. It looks like the clock will die long before you.
Why does the thing store the current time every 10 minutes? Seems like it needs your DOB, and whatever the current clock time is - and even a few minutes of drift isn't going to be a problem for an application like this. If it's ever connected to the tubes, it can adjust its clock from a time server.
i wanted to make one of these but in the form of a watch you wear on your wrist. its interesting how some people are fascinated with these kinds of countdowns and others hate looking at them. me and my other cs buddy both think its interesting -- he has the tim urban poster on his wall. another friend of mine doesnt even want to look at it.
perhaps we should implant them in everyone, then monetize their time left..... http://www.imdb.com/title/tt1637688/
ATmega's EEPROM has a lifetime of 100k write/erase cycles. The program stores current time every 10 minutes, giving it ~2 years of lifetime. It looks like the clock will die long before you.
Totally off-topic, except for the EEPROM: A colleague once told me about a bug in it's audi where it would write the current volume of the radio to an EEPROM after every volume change. So, after a few years, the car stopped remembering the last volume setting when turning the radio off and on, because the EEPROM died.
Cool - it'd be fun to wear one of these on your sleeve, and glare meaningfully at it when people start droning on about nothing in a meeting or whatever. Although, it'd also be some embarrassing morbid irony if you run into an accident somewhere.
ATmega's EEPROM has a lifetime of 100k write/erase cycles. The program stores current time every 10 minutes, giving it ~2 years of lifetime. It looks like the clock will die long before you.
I’ve seen a similar low-tech version of this clock (sorry I can’t find a link). You setup two jars. Fill one with 365 * (years of life left). In the morning you move a single bead from the full jar to the empty one. It’s supposed to help you visualize “spending” your days, and encourages you to live them more deliberately.
I recall reading about this technique as used by Chris Crawford, a veteran video game developer with a lofty goal. (Intriguing article if you have the time.) https://kotaku.com/30-years-later-one-mans-still-trying-to-f...
> Chris Crawford owns 29,216 small plastic beads. Each bead is one of eight colors, and there are 3,652 beads in each color group. One bead represents a single day in Crawford's life. Each color group, therefore, represents one decade. The yellow beads are his childhood. The black beads are his teens. The greens are his inexperienced twenties, the oranges his restless thirties, the navy blues his settling forties and so on, all the way up to bead 29,216, which will represent his eightieth birthday.