The job market is very hard right now. It feels like 2009 all over again. It took until 2014 to recover in my local area.
And there is a LOT of new devs getting pushed out. Crazy.
nice project!
I had just graduated, fresh engineer and super happy I landed a pretty good starting engineering job in a great company. I was quite lucky. Engineers dropping like flies, becoming taxi drivers, or whatever they could find to sustain their families. All investments everywhere were dwindling. Thankfully oil prices were high regionally so some remained.
Doesn’t seem that bad to me, but I’m not a junior, or in the US.
US has been in a rough spot on the tech side as all the big tech companies kicked off a layoff spree (assumed by many to chase profitable quarterly reports).
With Trump and Elon screwing with the federal government, even stable government jobs are now hurting.
I applied to 600 jobs last year, had 30 interviews, and only had 1 job offer that was revoked after Emperor Elon took over. Things have been completely hellish for me.
600?? Did you automate it or something?
Contributing to big project can earn you more recognition than doing little project from scratch.
You know JS ? Contribute to some libs.
Found a bug in chrome ? Report the bug, learn a bit of C++, and submit a patch to fix it.Cyou count to 100? Learn quantum physics, compute the odds for each ball, and win the lottery. Easy peasy. I don’t know why these kids can’t thrive here in the future.
/s
In all seriousness, learning c++ or any language is good advice but it may only be easy or even possible if you have a certain background of concepts. We tend to overlook those, and remember achieving a certain skill without the full picture
I contributed a feature to the .NET JIT without knowing C++.
I really dont know C++, I have at most wrote 300 lines while following a tutorial 6 years ago.
I honestly don’t think that doing these cool things improves your odds of getting hired. Junior Devs don’t really touch these parts of a platform, let alone lead development on them from scratch.
A valuable engineer, to me, is someone who writes clean, maintainable code and follows common patterns. That’s also something which has to be learned by trial and error to actually see the value of.
And how would you demonstrate clean code and check for maintainability or patterns? How can you gauge the value of their trial and error?
Look at their code, look at their work. It is a point of reference for potential and actual scenarios.
This would absolutely increase their odds.
Sure, look at their personal projects. I’m just saying the maintainability and quality of the code and speed of iteration is more of the point than how impressive the math is behind an ML algorithm. I’ve just seen a lot of ML engineers/data scientists who really suck at writing maintainable code
“Maintainable code and common patterns? But I prefer code-golfing my if-statements into one, long sequence of characters.” -coworker standing atop the Dunning-Kruger peak
Rad video. Watch listing it so I can never watch it ever. That list must be in the hundreds now.
If you’re reading this and you’re learning programming, don’t bother.
