Comment by nunez

Yeah, but actually implementing those algorithms was extremely key to really grokking them. Testing those edge cases, seeing them fail, fixing them, learning "oh, that didn't fix it", repeat. Yeah, you can do it on paper (which I did), but the whole idea of going through the motions of writing yet another binary search algorithm was to lock in those concepts.

But that isn't the real problem here. Computer Science was always a theoretical concept, really. The meat of the issue is the rug being pulled out from the juniors and mids.

Reading code and writing it are two different skills. I believe that both are needed to maintain a codebase. It is much, much easier to understand what a service is doing when you're actually writing code that supports it, just like it's easier to remember the contents of a report that you wrote versus one that you read.