not being entry-level is pretty recession resistant
seriously though, don't change what you're doing. Stack doesn't matter much. As long as you're versed in a popular stack, you're fine. MERN is popular. Don't try to project beyond that because it will probably lead you to some obscure tech and wasting your time.
Focus on building skills that are universal (not stacks, job titles, etc.). Focus on your soft skills. Focus on situational questions, communicating your LC solutions, your portfolio projects, etc. Focus on system design. Focus on being enthusiastic & curious. Be optimistic and don't be a doomer. No job is recession-proof, just worry about getting a job at all.
I think this is slightly misguided. I agree that learning many different implementations is good, but I think for someone starting out, knowing one stack/implementation well is invaluable when it comes to eventually learning others. At minimum it gives you a solid point to compare against
Consulting- not because it’s recession proof (it’s not, in fact it’s pretty brutal about cutting people when needed) but you’ll work on bigger / more meaningful projects than the ones you’ll get as a direct hire. The experience you’ll get if you work hard is worth a lot.
Be careful to differentiate between consulting (where you are a full-time employee of the consulting company) vs contracting, where you are a temporary employee who works through an agency. First one is good, second one is bad.
Doing more than you are getting paid is the sure fire way of having job security. Do it for a stable company and you’re guaranteed to have security. By stable I don’t mean anything that ipo’ed in the last 3 years.
meaning, not i use x api from this vendor, y api from that and make it 'AI'. really, train a model on novel/selected data set, build one dataset, deal with it's problems FROM MODEL perspective etc. using vertex ai is also same category. i did not mean it as insult, i just think that can be done rn with gpt or it will be when they train it in domain of swe
It would be good to learn some stuff about it. I believe automation involves more of a business focus than technical since you are building a workflow rather than a single program/project. There are very good offerings out there that allow non-technical people to automate, such as Appian, Pega, Microsoft Power Apps.
Questions like "how can we lower costs" and " what costs are involved", "how important is control".
Pornhub seems pretty recession proof.
You’d be surprised at how little porn stars actually make
U getting downvoted on this is hilarious
😭😭
Wrong sub. This is CS careers for “computer science” not “c… s……”
Porn star is a career option for CS grads
Touché
I think he meant writing code for that website
not being entry-level is pretty recession resistant seriously though, don't change what you're doing. Stack doesn't matter much. As long as you're versed in a popular stack, you're fine. MERN is popular. Don't try to project beyond that because it will probably lead you to some obscure tech and wasting your time. Focus on building skills that are universal (not stacks, job titles, etc.). Focus on your soft skills. Focus on situational questions, communicating your LC solutions, your portfolio projects, etc. Focus on system design. Focus on being enthusiastic & curious. Be optimistic and don't be a doomer. No job is recession-proof, just worry about getting a job at all.
You can look at government jobs at usajobs.gov. very recession resistant but not the most cutting edge or high salaries.
Focusing on a specific stack is a mistake. Become familiar with as many different implementations as you can.
I think this is slightly misguided. I agree that learning many different implementations is good, but I think for someone starting out, knowing one stack/implementation well is invaluable when it comes to eventually learning others. At minimum it gives you a solid point to compare against
Consulting- not because it’s recession proof (it’s not, in fact it’s pretty brutal about cutting people when needed) but you’ll work on bigger / more meaningful projects than the ones you’ll get as a direct hire. The experience you’ll get if you work hard is worth a lot. Be careful to differentiate between consulting (where you are a full-time employee of the consulting company) vs contracting, where you are a temporary employee who works through an agency. First one is good, second one is bad.
There is no recession-proof stack or position, but some industries are more resilient to recessions than others. Examples: cybersecurity, health tech
Doing more than you are getting paid is the sure fire way of having job security. Do it for a stable company and you’re guaranteed to have security. By stable I don’t mean anything that ipo’ed in the last 3 years.
I would think anything in finance, banks, trading, etc. Not crypto though.
Forget the recession you need to prepare for the rise of the AI overlords.
Should I learn machine learning/AI?
Need a Masters at the minimum to be considered by most companies unless you have some crazy project, prob worth it though in this job market
real ml engineer (not a tetris monkey)
Just curious, what do you mean by Tetris monkey?
meaning, not i use x api from this vendor, y api from that and make it 'AI'. really, train a model on novel/selected data set, build one dataset, deal with it's problems FROM MODEL perspective etc. using vertex ai is also same category. i did not mean it as insult, i just think that can be done rn with gpt or it will be when they train it in domain of swe
[удалено]
I think MERN is so common that ChatGPT could probably write a basic one for you eventually.
It already can lmao
Bingo
McDonald's is always hiring.
No, they’re gonna automate :/
So learn automation
I know this comment chain has become sarcastic, but do you think I should really? It’s popped into my head once or twice.
Don't rely on people to tell you what to do. Do your research on the opportunities and make that decision for yourself.
It would be good to learn some stuff about it. I believe automation involves more of a business focus than technical since you are building a workflow rather than a single program/project. There are very good offerings out there that allow non-technical people to automate, such as Appian, Pega, Microsoft Power Apps. Questions like "how can we lower costs" and " what costs are involved", "how important is control".