I think the crazy thing is people think redis is the only thing that catches in memory.
You could throw a bunch of your production data in SSAS tabular and there you go you have an in memory cache. I've actually deployed that as a solution and the speed is crazy.
yeah the name of the game now is just to avoid any company that has shitty recruitment. you can tell in an instant if they are worth your time or not, which I'd say in Canada is about 90% a waste of time.
someone who actually wants to hire will want you and wants to do whatever they can to get a good candidate.
Realistically its just the blind leading the blind. People have forgotten that a interview process was designed to avoid false positives, and that the companies who were most selective were providing top 1% comp and had brands that could carry that weight. If you are google and you were handing $500K in RSUs on top of $300K+ in salary, you better damn pick the right candidate...
For some random SMB in shipping or something to be bashing people over the head with 10 step-leetcode-full-panel-10-hour-systems-design interviews they just don't get it. For starters they probably don't even have the talent to properly evaluate the prospect. So who are they helping?
I don't really think this is true? This might be true for developers that only work for companies and never in their own time maybe.
My portfolio site is just one of the sites on my personal website that also hosts many of my projects. It wasn't much work to setup, and it provides organization and sharing capability so there's motivation to make it anyways.
>This might be true for developers that only work for companies and never in their own time maybe.
I'd argue that that is indeed the majority. Maybe they have some work from school days, but very few devs are making portfolio pieces years into the industry once they can flesh out their "Employment" sectiion.
IME you only need a portfolio as a non-junior if you are making a lateral move.
That is the world we live in from my experience. This is one of the reasons I decide to switch to management at 40 years old earlier this year - If I lose my job I don't really want to be grinding leetcode.
if your interviews are easily cheatable you should probably fix the interviews. back in the day when i was in university we were allowed to use any resources for exams cause you couldnt cheat easily.
anyone I know who actually got a job through leetcode style in the last 2 years cheated. they would get their friends to mirror monitor and then type the answers in from chatgpt LOL
im not doing any coding challenges that aren't real world
if i see anything remotely challenging i dip out. interviewing is just a numbers game nowadays so i dont waste time on interviews if they seem like they're gonna burn me out for the rest of the day. granted i have 11 years experience
You could throw a bunch of your production data in SSAS tabular and there you go you have an in memory cache. I've actually deployed that as a solution and the speed is crazy.