this post was submitted on 24 Apr 2024
-13 points (37.7% liked)
Programming
17537 readers
122 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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?
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?
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.