Live data from Hacker News

Resolutions for programmers (2012)

matt.might.net

21–30 of 228 posts

Re: Resolutions for programmers (2012)

#22
# Keep a hobby project or fork an open source project and work on it when ever you find time. # Once in a year take one month off from work if possible and visit new places. # Go for a solo trip and spent time with yourself and nature. # Go for volunteering in some rural schools. And spend time with kids. # Publish a book.

Re: Resolutions for programmers (2012)

#23
post #9

Earlier quoted context omitted.

It's a bit like learning a language, you'd need some almost immediate application to make it past the first steps of a book or course (and/or make that gained knowledge stick). And while it's easy enough to travel to some country where they speak a language you just learned, that's often harder when it comes to mathematics and IT. 3D maths and game development worked out somewhat in the past (I forgot most of it thou…

I was going to say, a lot of the Math I learned in High School and then never applied to anything I re-learned more recently when I started mucking around with computer graphics and game dev (especially trig, matrices, vector math, etc.) I'd love it if people had suggestions for other engaging ways to apply math while programming!

I highly recommend Jeremy Kun's blog - Math and Programming (http://jeremykun.com/). His posts are always awesome.

Re: Resolutions for programmers (2012)

#24
post #13

"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)

#25
post #7

Don't let past death marches and shit-projects affect new projects mentally. It's harder than you think.

This is a good point. Many people quickly become cynical and lose their passion for making things. Instead of thinking of the possibilities they change and only think of all the blockers. Recapturing that naiveté is what is required to just get some projects off the ground.

Re: Resolutions for programmers (2012)

#26
post #16

I would put stay healthy and invest in your health (chair, standing desk, exercise, food) as the #1 for any programmer for next year, and the years after. It's all too easy for us to forget about the long lasting effects of sitting in front of a computer that are hard to later undo.

Save by not investing in standing desk.

Build a standing desk.. Two resolutions - a hobby (learn carpentry) and health benefits!

Re: Resolutions for programmers (2012)

#27
post #24
post #13

"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.

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 me off a little bit when people discount it as "definitely" a "cargo cult" thing. If you don't like it, that's fine.

Re: Resolutions for programmers (2012)

#29

#8. I'm currently waiting to see what comes back from fsck on a 4TB drive connected to a Raspberry Pi (don't ask). Drive is 390 days old according to SMART and reporting unrecoverable read errors. Most of the stuff was in other locations but I know there was one repo I was waiting to push... waited too long, I guess.

I was going to say, if these are in priority order, move #8 to the top if you're not already doing it! That way you get the benefits of it moving forward :)

This is going offtopic, but if you're going to do backup/NAS, check your logs! I'm going to see how much I have to learn to set up monitoring on my home network. An error from Windows (coming from Samba) that I dismissed as a Samba problem was actually an early warning of the drive failure.

Edit: ouch.

  root@kiwi:/media/files2# ls -lah
  total 12K
  drwxrwxrwx  3 nobody backup 4.0K Dec 22 22:19 .
  drwxr-xr-x  5 root   root   4.0K Dec 30 20:19 ..
  drwx------ 32 root   root   4.0K Dec 31 00:54 lost+found
Post reply on HN