It happened again.

I got pulled into a conversation about whether or not it’s appropriate to code after work hours.

“I get paid to code. I’d rather spend my limited free time doing something I enjoy.”

“If I want to learn something new, I’ll get a job that pays me to learn it.”

“Coding is work.”

I get it.

If that’s how you feel, you probably shouldn’t be coding in your free time (except perhaps on an exceptional basis of résumé building).

But not everyone sees coding that way.

I really enjoy coding. For me, it is a pass time.

Given the choice between playing on my PlayStation or adding a feature to a hobby project, or fixing a bug in an open-source project, I often choose one of the latter. Not because I’m obligated. Not because it improves my résumé.

Simply because I enjoy it.

I can get a dopamine hit from completing a level in a video game, or from fixing a bug. Sometimes I choose the former. I often choose the latter.

In fact, it’s this very love of coding that led me into the industry in the first place. And I guess I’ve been fortunate enough not to have had the love of coding killed by my jobs (although there have been times this has been true).

Should you code in your spare time? It’s up to you. I do, because it’s fun. If it’s not fun for you, you probably shouldn’t. And you shouldn’t feel bad about it.