> Also, putting the emphasis on the interviewer understanding the candidates code instead of the other way around is never going to be popular
It's also hard to scale it, make it objective, and keep the efficiency high (most developers prefer not spending their time on either side of the interview table)
There is another advantage to the "algos". If you can learn algorithms then perhaps you can learn other things as well.
Every new job I've had involved quite a lot of learning in a very short period of time.
Learning whatever language, and whatever standard library is almost always trivial. They're usually not all that different, well documented, some with textbooks even.
Learning to navigate and reason about the huge number of undocumented, often arbitrary, system architecture decisions, design decisions, code layout, etc. etc. that make up real code bases.
> Isn’t the time spent memorizing leetcode similar to the time spent building a side-project?
The nice thing about leetcode it is easy to bound the time to what you can handle. I do one puzzle a week and set a timer for 20 minutes. Then I get the answer and browse the forum. It's basically the equivalent of solving the Sunday crossword for me, and it keeps my algorithm skills sharp. Probably no worse than burning a lunch hour on HN.
Totally agree. I read the article as, when I am on my M1 I often experience memory pressure related issues. Not, because of my M1 I often experience memory pressure related issues.
It's very likely future software updates can help address these issues.
Honestly, the machines haven't had wide deployment in the field for all that long for Applications as huge as Photoshop. It takes time to discover, fix, and redeploy things like Photoshop. And it's not like Photoshop never leaked memory on an x86.
It's also hard to scale it, make it objective, and keep the efficiency high (most developers prefer not spending their time on either side of the interview table)
There is another advantage to the "algos". If you can learn algorithms then perhaps you can learn other things as well.
Every new job I've had involved quite a lot of learning in a very short period of time.
Learning whatever language, and whatever standard library is almost always trivial. They're usually not all that different, well documented, some with textbooks even.
Learning to navigate and reason about the huge number of undocumented, often arbitrary, system architecture decisions, design decisions, code layout, etc. etc. that make up real code bases.
That's hard. Really hard.