The title itself is a recipe for disaster. Also this is a semi rant.

Yesterday I was informed that I will have the honour to implement the core functionality - which is an interface layer to use the driver of a very expensive hardware shit - of the software I’ve been working on as a frontend dev.

There are two possibilities for the language: C++ or C#. The one that was proposed/imposed is C#, which I know nothing of, while at least I have some hobbyist experience with C++; when asked if I could take some time to familiarise myself with C# I was basically laughed in the face, saying I will learn on the field and at least some of them have some experience with it.

Should I insist to go with C++, or is that an even worse idea in an already fucked up situation?

  • marcos@lemmy.world
    link
    fedilink
    arrow-up
    30
    arrow-down
    1
    ·
    1 year ago

    If you have “some hobbyist experience” with C++, then you should definitively avoid it and go with C#.

    You should be at least “C++ is a landmine, be careful there” tall before allowed to play with it alone.

    • nitefox@lemmy.worldOP
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      1 year ago

      Yeah, probably. In the end maybe I will end up using c++ cause a coworker is pushing for it (although he knows nothing of the language). Ironically, I’m the one advising not to cause I know I don’t know lol

      • marcos@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        There’s so much hidden rope in it, that will catch you if you happen to pass through. It doesn’t only give you some to misuse.