I have a habit of talking to my code. It freaks out people when I'm intense coding near them but interviewers love it and I don't have to put extra effort to "communicate" 😂
Wait, are you saying not everyone talks to their code?
Code abstraction during coding rounds. Write the code as literal pseudocode and implement each abstraction later, this is especially useful for rounds focusing on OO design, but also applies to leercode rounds. For example if my solution has bfs, my code would have “bfs” as a subroutine. And in my bfs I would have “add neighbors” and “check invariant” as subroutines. So my code ends up being mostly memorable boilerplate with custom implementations to solve the problem. Makes it easy to explain and easy to understand, and you can sometimes get away with saying “do you want me to implement this?”
Haha. This is super important. Always ask "do you want me to implement this"
Propanolol and practice
Tech Industry
Yesterday
1859
Do people underestimate E6 role at meta?
World Conflicts
Yesterday
503
Why I Find Free Palestine Inspiring
World Conflicts
Yesterday
665
Israeli precision-guided munition likely killed group of children playing foosball in Gaza, weapons experts say
Health & Wellness
4d
46457
High performers, how often do you have slack off days?
Personal Finance
Yesterday
492
Biden wants to raise capital gains tax to 40%
Memorizing behavioral scenarios and regurgitating them in every behavioral round for every company to convince them that you have the work ethic of Albert Einstein and the affability of Robin Williams.
Pls explain more!
How many scenarios you have in that list? every company conduct these in different ways