4 ms·
So, I don't study for interviews because I practice the fundamentals all the time by writing code at varying degrees of complexity. For instance, a silly side p
by mathgladiator 6y ago
So, I don't study for interviews because I practice the fundamentals all the time by writing code at varying degrees of complexity. For instance, a silly side project of mine has me writing my own UIs with canvas. Is this a good idea? Well....
The core challenge is there is the job of understanding the machine and the science, but then there is the task of building products for humans. We only have a good sense of how to measure one and not the other.
The frustration that I have is that knowing the machine and the science is like... less than 5% of the job (and that's being generous). Fortunately, I made a good career in infrastructure where instead of 5% it is more like... 25%... as the architect.
- ljf 6y agoI'm not a developer, so my experience will be different I'm sure. I never study for interviews, but I do research the company. Not days of effort, but if I want the job then at least a few hours. This is as much for me to make sure I understand the company, and what issues I can see from the outside I might want to talk about. I always make and account and make notes of the sign up processes etc. If I'm interviewing someone who hasn't even visited our site at all, that never leaves a good taste for me.