• @dylan
    link
    27 months ago

    Oh I agree. I’m sorry if I came off argumentative or aggressive myself. I think the difference is the language used. The way this article was written plays on outrage to garner attention and potentially evoke discussion. If it had been framed as “I won’t be doing AoC, and here’s why: I don’t like doing this thing, so doing it without getting paid doesn’t sit well with me” instead if “I don’t like doing this thing, so anybody who uses it as more than just a job is stupid”, it could have led to some interesting and fun discussion.

    I’ve got coworkers who just see developing as a job. Which is cool. I’m glad they can be good at it without being incredibly interested in it. But also for some of us it isn’t just how we get paid. And some devs are just doing it for fun. None of my coworkers have even mentioned AoC. Nobody at work pressures me into coding outside of my job. The only time I’ve been pressured to learn is when I ignored my teams requirement of “equivalent to one hour a week” pluralsight training. Which I missed for the majority of a year as I didn’t want to waste dev time doing training. I love that it’s provided free for every dev, but turning off project mode is challenging for me.

    So I think the discussion could and should be had. It’s an interesting topic to me. I just think it could be done with a little less aggression. Or maybe it was written that way to drive views. Idk, but either way I’m just getting weary with all of the outright negativity towards those who enjoy different things than someone.