loading...

re: It's perfectly fine to only code at work, don't let anyone tell you otherwise. VIEW POST

FULL DISCUSSION
 

This is something I've been trying to remind myself about everyday for the past while - that coding only for work is okay and that I don't need to feel bad about it.

I feel like there's an unintended pressure of needing to make coding my entire life and actively contribute, or at least spend large amounts of time on, because it feels like something that's standard as a dev. A lot of it comes from spending time on places like Github, Reddit, Twitter, blogs, YouTube, and other forms of social media where I see so many devs coding outside of work, being passionate about it, and contributing a lot to the community. It's a good reminder that not all devs are the same. We're all different people who work differently where some see coding as a passion while others not so much, like in other kinds of jobs.

That being said, right now I may need to put in a bit more time towards coding outside of work because I want to get better at some skills for the future. So instead of going in with a mindset of feeling like I have to do it, I hope to go in feeling like I want to do it.

 

Coding outside of work is a wonderfully awesome pursuit. The pressure to do so is either misguided or self-manufactured.

I go through periods of lots of coding outside of work and periods of no coding outside of work depending on my motivations and interests at the time.

I personally almost always read about coding or listen to dev podcasts outside of work. I spend a lot of time reading dev.to, of course. But doing so in a lean-back mode as opposed to lean-forward mode is definitely different.

Our brains, motivations, personal goals, energy levels, family-lives, are so utterly variant that being overly prescriptive about how others should manage their careers is a recipe for disaster. I casually take part in open source but I could not fathom being a maintainer of a popular project outside work. It seems hellish to have the kind of responsibility that comes with that. But people do it and love it, even if it burns them out sometimes.

I watched this talk by Sam Phippen about the process of keeping rspec up-to-date with new Rails versions and the pain an commitment it takes blows my mind.

I could see a time in my life in the future where this could be a lot of fun, but at the moment it does not compute. When I was newer to software development I definitely felt the pressure to take part in all these activities, but none of it's all optional.

Code of Conduct Report abuse