If you’re reading this and you’re learning programming, don’t bother.
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!
Hi, nonprogrammer poking my head in from all. What happened in 2009?
A global recession.
oh huh, really showing my age here heh
Oh don’t worry you’ll get to experience one firsthand in [ checks watch ] about 20 minutes.
https://en.wikipedia.org/wiki/Subprime_mortgage_crisis
My local area was hit bad about a year later than everyone else. But once it hit, houses were close to 1/2 the price of what they were going a year earlier + unemployment was up to about 20%. It was VERY bad and I remember trying to get a job in the middle of it. I got lucky and got something around an hour away while quite a it of my social group moved away.
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.
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
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.
