[supernikio2]

I agree much of this fall under "working for free" but it doesn't have to. I for instance, work as a web developer and really want to get into making games, which is a huge undertaking in itself. It requires deep, productive time of learning and experimentation, and I often find myself drained after work to tackle such activities.

However, I do feel like working through projects like this and coming out the other side with something tangible is a high like no other, and I despite how hard it might be, it's really invigorating and gratifying.

[BaseballPhysics]

Ah but that's a very different thing.

You're treating tech as a hobby and engaging with it accordingly.

This piece literally started with:

> My software developer colleagues often ask me where I do get all the time for reading all the tech books or articles, watching conference talks and listening to podcasts.

Immediately we, the reader, know this isn't about having fun in your spare time or learning and building purely for pleasure.

It's all about achieving, about being that person that other people look to and think "wow, where do they find the time to be so productive??"

If it were as you say, I'd have no issues with the piece at all.

[ncruces]

Wether you consider learning a hobby, a chore, or part of the job description, is entirely up to you, regardless of how close to the topic of paid work it is.