@@MrSvitS1337 Of course the content is great and thank you @WeCoded for your initiative and recording... I am commenting only the "aggressive eagerness" to as the interviewer to extract info from the man. And btw its only my perspective
I'd say that's fine. Had many like that and have been guilty myself. Sometimes, the candidate can go a very long time on a specific topic, and the interviewer does not want to spend more time than necessary. Not all questions are intended to be answered thoroughly
@@VakhtanGG i like the way you are seeing this. I can put myself it both positions. Though my reflection is that the interviewer is intermittently stuttering him with the answers he wants to listen to… btw good luck to y’all who’s having an interview
@jayTzanTG15 Sure, he does stutter him. But you get used to it pretty fast. Just stop when stopped. On the flipside, less you talk, fewer mistakes you make lol
Consider if you are calling an API in constructor, the angular keeps the reference of the component object and use it somewhere else. When the same object is used somewhere else then contructor will not be called because angular will reuse already initialized object. So the API call will not be sent in the new place. Remember that angular will still call the lifecycle hooks for it.
