this post was submitted on 19 Feb 2024
148 points (93.5% liked)

Asklemmy

43942 readers
522 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

By employed I mean get a job in the industry either offline or online. Ideally something that would highly likely remain in-demand in the near future.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] pkill@programming.dev 9 points 9 months ago* (last edited 9 months ago)

Vue.js, it's the simplest of the popular frontend frameworks

You can learn a hellton about sysadmin and DevOps by running a home lab and aiding that with some courses and maybe one cert or two but I wouldn't splurge on certs that readily.

Golang, Express.js, Nest, Flask, SQL (a must), maybe Spark if you dare. Any popular and expressive framework/language for full stack/backend, except for Rails and PHP, those are dying technologies despite their still relatively high popularity in some countries.

Maybe Flutter, Swift or React Native if you want to get into mobile dev.

Just go to a job board, then to learnxinyminutes.com, pick something and start with building small, then medium sized, then maybe more complex projects or contributing to FLOSS written using your tech of interest (but please, PLEASE don''t treat OSS contributions primarily as a way to get a job. Pick something you use instead. Try to figure out how you would implement something, do that and don't let the impostor syndrome win if it uses a tech you're familiar with whenever you want to open an issue on a git forge.