Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Arduino Death Clock

github.com

Post reply on HN
Print view View original

31–40 of 64 posts

Re: Arduino Death Clock

#31

Post by kiliankoe »

avian wrote: post #29
sillysaurus3 wrote: post #11

Tangent: I see example.jpg added to the main repo, just for the readme. If you don't want to store binary blobs, there's an alternative: open a new issue, then copy-paste the image into the issue. It'll give you a link that you can use in a readme permanently.

This is another small step to being depedent on GitHub for hosting your project. A “git clone” won’t clone images hosted in the issue tracker.

It won't, but it will still be displayed when rendering the readme, just like if it were hosted on any other webserver. Of course only as long as the webserver is around, but still better than adding several MB to your repo just for a few screenshots.

Re: Arduino Death Clock

#32

Post by frandroid »

sushid wrote: post #21
leggomylibro wrote: post #4

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.

I essentially have something like this on my laptop (Chrome new tab) and it was awkward having to explain to the interviewer who saw that on my screen what it was counting down for.

...did you get the job?

Re: Arduino Death Clock

#34

Post by magnat »

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.

Re: Arduino Death Clock

#35

Post by kirillkh »

magnat wrote: post #34

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.

Perhaps it's better to set it to 2 years, then. A clock that's counting time towards its own death. There is some grim poetry in that.

Re: Arduino Death Clock

#37

Post by majewsky »

kiliankoe wrote: post #31
avian wrote: post #29

Earlier quoted context omitted.

This is another small step to being depedent on GitHub for hosting your project. A “git clone” won’t clone images hosted in the issue tracker.

It won't, but it will still be displayed when rendering the readme, just like if it were hosted on any other webserver. Of course only as long as the webserver is around, but still better than adding several MB to your repo just for a few screenshots.

If it's only a few MB, I'd value the ability to backup the image together with the rest of the repo more than shaving a few MB off the repo.

(Also, hi Kilian. Long time no see.)

Re: Arduino Death Clock

#38

Post by magnat »

After power failure, clock will be 0..10 minutes behind the schedule. If the value written to EEPROM was ahead of actual wall clock by half of timespan between writes (instead of current time), each restart would contribute -5..5 minutes of drift, averaging out to zero over long time and multiple power failures.

One could in fact set it to update EEPROM only once a day, but write time half day ahead of current time. This will prevent wearing out memory for hundred of years while still maintaining decent accuracy.

Re: Arduino Death Clock

#39

Post by struppi »

magnat wrote: post #34

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.

Re: Arduino Death Clock

#40

Post by tomjen3 »

wheresmyusern wrote: post #22
Sukotto wrote: post #19

A variation on this that I love is Tim Urban's "Your life in weeks" visualization. https://waitbutwhy.com/2014/05/life-weeks.html This is a progress bar, not a countdown clock. Personally, I find it super helpful in keeping perspective on the value of my time. I do not mean to detract from OP's work (which is cool), I just thought others reading the comment might enjoy this other article too.

i will never forget when, in early 2016, i saw this for the first time. when looking at the visualization in terms of weeks, i simply cant believe it, even today. i just looked at it again now. it simply cant be so few weeks. it just cant. and yet it is. i cant believe all the time i wasted.

Years ago i made a version with checkboxes, that would check each box as your life progressed. Was an attempt to learn QT, but it made me hate how much time i was forced to waste in schools.
Post reply on HN