More about algorithm questions vs system modeling: I'm thinking that 1) getting good at algorithms takes less time, than getting good at system modeling. — On

More about algorithm questions vs system modeling: I'm thinking that 1) getting good at algorithms takes less time, than getting good at system modeling. — One will see one's mistakes sooner, within minutes, compared to system modeling, in which case one would need to stay at a workplace for months or years, to see how a system design eventually turned out to be a mistake? But 2) it's also harder to get good at hard algorithm questions — most people won't get that good at it, also with weeks and months of practice. And they still wouldn't have any real chance in a Google coding interview. And in that way, algorithm questions make sense? They give more information about the person's ability to think and learn — good for the company — and takes less time for the candidate to get good at (weeks or months — compared to working for years?), good for the candidate? (I'm someone else than GP) PS. I wonder what the electrician was up to? :- ) and the other one