I know these kinda questions get asked a lot these days, but hear me out.

I’m a junior-going-on-medior software engineer, graduated last year and have been (more or less) teaching programming for four years.

In my search to find meaning in life, I stumbled into programming and found that there was a lot to learn. I loved it. That’s why I eventually chose to switch careers once I musterred enoigh resources to do so. I chose this job because I like learning and I want to keep learning for the rest of my life. I love the way how learning is an integral part of the programming community and how everyone encourages and stimulates it.

AI has changed the job of an swe, that much I understand. That is not a deal breaker for me, as long as there is still a lot of meaningful, worthwhile, marketable things to learn. I am using AI to learn things faster now, but there is an easy pittfall to actually learn nothing from AI. Some say we don’t have to learn anything anymore, I don’t think that is true, but then what is true?

How is AI affecting the learning aspect of this job? Is learning still an important part of the job? Is there still enough worthwhile things to learn? Is it still valuable to learn more?

  • severalkittens@ani.social
    link
    fedilink
    arrow-up
    5
    ·
    5 days ago

    As a swe of 10+ years it’s been a whirlwind. Within the past year my job has gone from primarily writing code to primarily reviewing code, be it llm output or code reviews for the team. I think a lot of the learning still stems from a place of changing your thinking from atomic implementation level to systems level thinking and design. Do design docs, talk about your ideas with the team, foster a culture of ownership where even junior engineers can play with architecting micro services if it makes sense. Just because the fun of implementation has been mostly removed from us doesn’t mean we have to stop learning!