I’m in the course of pursuing a change in my career towards software engineering/architecture. So far I’ve been brought mostly to C#/.NET and Java, though Java attracts me more, even considering that it might be a “dying” language. Still, Scala and Clojure are there, so I thought that they might give a pump at least to JVMs. In your opinion, should I invest in pursuing certifications/jobs in this field, or sticking to C#/.NET is a better path?

  • expr@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    Never do certifications for software engineering. The only certifications worth a damn are security certs and networking certs. If I saw a programming-related certification on a resume, I would completely ignore it since the only thing it tells me is that you paid some money to get a cert.

    While I’m not a fan of Java, it’s most certainly not a dying language and you will be able to easily find employment into perpetuity. If I had to pick, I’d personally choose Java over .NET purely to avoid being trapped in Microsoft-land, especially with all of the bullshit they’ve been up to lately.

    • vfreire85@lemmy.mlOP
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      My biggest concern over .NET is exactly how closed Microsoft-land can be. For what I’ve seen so far, with the notable exception of perhaps Unity, pretty much everything else gravitates around MS and there’s no way of leaving it.

      • folekaule@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        Since unity is c# I think maybe you phrased that opposite of what you meant?

        Anyway, I work in an enterprise environment. We use both Java and .Net, and it largely depends on which group you’re in. Neither Java nor .Net is going away anytime soon.

        You really don’t get to stick with just one thing in a developer career. Learn a little of everything, especially multiple paradigms, and specialize in a few related to the business you work for.

        A key skill is adaptability, learning as you go. If you make yourself too specialized, you’ll set yourself up for being laid off when your skills become obsolete. I have interviewed a few older IT people in that situation, only a few years from retirement.