The ‘technologies’ will be replaced by their respective icons.

  • Python@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    6 months ago

    I’d love for someone more experienced to chime in, but on first glance the classification of JavaScript/Typescript as backend strikes me as weird.

    That may just be because the team I work with uses a React/Typescript/Java/Postgres stack and we specifically classify the Typescript as part of the Frontend. Maybe it’s different in different companies?

    I’m sure that a Typescript backend could work perfectly fine, it’s just semantics 🤷

    • Shareni@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      6 months ago

      You don’t classify a language, you write what language you used for the task. I’m guessing you’re using Java for backend, and TS only for react?

      • Python@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        6 months ago

        Yup, exactly! So a calculation-only module that doesn’t have a frontend would never have any TS Code in my case.

        The classification of language -> task makes sense! I’m thinking of the weird college courses that wanted Java frontends lol

        But how would you generalize that for a resume? Say you’ve used C# both for making backends and making frontends in separate projects. Would any sort of classification make sense in that case?

        • Shareni@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          6 months ago

          But how would you generalize that for a resume?

          I separate languages and tools/frameworks (not a dev CV so take with a grain of salt). No clue about the c# world, but for js I’d do something like:

          Languages: js, TS

          Frameworks: express, react, etc.

          The key is to hit all of the required keywords, machines and HR don’t know anything else. If a developer looks at your résumé they’ll know that you wrote both ends.