#3 Embrace the Uncomfortable - one thing I did a few years ago that might fall into this category (as an American) is start using the 24h clock. It makes working w/ remotes a lot easier because you become good at doing the +12 math and knowing which hour it represents. :)
Resolutions for programmers (2012)
31–40 of 228 posts
Re: Resolutions for programmers (2012)
#32#3 Embrace the Uncomfortable - one thing I did a few years ago that might fall into this category (as an American) is start using the 24h clock. It makes working w/ remotes a lot easier because you become good at doing the +12 math and knowing which hour it represents. :)
Let's make a day be 86400 seconds (already a SI standard), and then you can divide that into tenths, hundreds or whatever. One thousand of a day is 84.4 seconds, which is close to a minute (which is (/ 60 (/ 24 one-day))).
We have metric for measurements in space, but something as simple for day-to-day time measurement would be nice.
Re: Resolutions for programmers (2012)
#33One look at any news site is enough to help you avoid the first 12 resolutions.
Re: Resolutions for programmers (2012)
#34Earlier quoted context omitted.
Save by not investing in standing desk.
Build a standing desk.. Two resolutions - a hobby (learn carpentry) and health benefits!
[0] http://www.huffingtonpost.com/entry/standing-desk-sitting-da...
[1] http://health.usnews.com/health-news/health-wellness/article...
[2] https://www.bostonglobe.com/lifestyle/health-wellness/2014/1...
[3] https://www.washingtonpost.com/national/health-science/stand...
Re: Resolutions for programmers (2012)
#3513. Work on volunteer projects I set this resolution for myself last year, and have been able to work on three projects via http://socialcoder.org/ - feels very fulfilling!
Re: Resolutions for programmers (2012)
#36Re: Resolutions for programmers (2012)
#37"Switch to Dvorak" .. ha :(
I think this one is a waste of time unless you seek a mental challenge. In my experience, it's just not worth getting confused on QUERTY keyboards all the time, and the 5% speedup or so is really not worth it. It's definitely more a cargo cult/challenge than a useful skill.
Re: Resolutions for programmers (2012)
#38Earlier quoted context omitted.
I think this one is a waste of time unless you seek a mental challenge. In my experience, it's just not worth getting confused on QUERTY keyboards all the time, and the 5% speedup or so is really not worth it. It's definitely more a cargo cult/challenge than a useful skill.
I don't think the speedup is worth it, but that wasn't why I became interested in the first place. I'm way more interested in the benefits of a more ergonomic layout for my wrists and fingers. I haven't studied the science of that very carefully, but I'm fluent with both Dvorak and Qwerty and the subjective comfort I feel when typing English with Dvorak is very much worth the effort of learning it, for me. It ticks m…
Re: Resolutions for programmers (2012)
#39# http://people.cs.kuleuven.be/~bart.demoen/PrologProgrammingC...
# http://www.cs.bham.ac.uk/~pjh/prolog_module/sem242.html
# http://www.learnprolognow.org/
I'm getting an itch now, I think I'll give Prolog a second go this new year.
Re: Resolutions for programmers (2012)
#40> Switch from emacs to vim or vice versa. Switch to emacs + evil, or alternatively to Spacemacs: https://github.com/syl20bnr/spacemacs