This approach will save you hours if not days and you can still do more practice problems later if you really feel like that's important.
This approach will save you hours if not days and you can still do more practice problems later if you really feel like that's important.
For instance, practicing by knowing the type of problem (e.g. two pointer) then thinking, “alright, how do I apply a two pointer algorithm to this?” Not just looking at the answer and copy+pasting. You’re gonna end up having a bad time doing that. It won’t get committed to memory.
AFAICT you need to go through the physical exercise of typing things out and not typing them out as a computer but typing them out with mental thoughts involved.
I'm sure some of those tools would be useful in industry, it's just I haven't really seen that in 23 years ... but you never know! It's got an acedemic curiosity that I appreciate, it's just its utility is so low generally.
It's bizarre the roadbumps we put in front of new devs. I'd rather see: - someone hack on a big but unknown piece of code. Open source even, and map out what it would take to add a feature, what tests they would write, where the touchpoints are, etc. - pair with someone - are they able to work with people? - fix a bug: go through methodically, especially on non-deterministic failures - lay out a system using objects / functionally / whathaveyou
Or just have me implement towers of hanoi again, ick.