One tiny practice to try is: whenever you're looking at code and you see a loop — ask yourself about its complexity in terms of Big O notation. This comes up all the time in interviews, and having an intuitive understanding of complexity (time and space!) helps you write more performant code.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One tiny practice to try is: whenever you're looking at code and you see a loop — ask yourself about its complexity in terms of Big O notation. This comes up all the time in interviews, and having an intuitive understanding of complexity (time and space!) helps you write more performant code.