Day 40I forget what it's called, the 6 signs of grief or something? I think I'm permanently on the anger phase, so might as well put that anger to good use. I worked out, angrily, then went back to leetcode.
I did question https://leetcode.com/problems/insert-into-a-binary-search-tree/. This should have been a leetcode easy tbh, not sure why it's medium.
Second question is https://leetcode.com/problems/number-of-dice-rolls-with-target-sum/. This took more time than needed. I'm a little disappointed in that. It's some good ol dynamic programming but I would have past the time limit and possibly failed during a real interview.
I kinda scoured the internet for system design questions that I was asked yesterday. I still think mine was pretty good so I'm jut confused man... I don't get it. I'm try to be as unbiased as possible and look at the things I could have improved on.
- I forgot the JSON notation when discussing how the APIs would send and receive messages, but I don't think it was a big deal. I just remember it uses curly brackets and commas, but maybe not knowing the exact threw them off.
- I did have to change up my data modelling after I first drew it up and used different table, but I thought afterwards it was sound and made sense. They didn't have to tell me what to do, I just figured out this might not be the best and changed it up, and they seemed satisfied (maybe not because of the rejection... dem poker faces)
- I didn't go through all the functional requirements and missed one of them, although the interview seemed to be okay with that when I somewhat insisted, so I didn't push it further. Last thing I want to do is annoy the interviewer.
- I should have drawn more arrows connecting different parts of my system design. Hard to do that while talking at the same time. I thought the diagram still looked good, but I cannot take chances like that anymore. Everything needs to be super clear.
- I think I should take time drawing a diagram to explain a basic use-case. Like user A logs into the system, hits these points in the service, and gets back information
- The interview did hint on what type of database to use, and maybe I should have been more confident. I more-so described the pros and cons of each type, but I should have made it clear that I was going to go with one.
That's all I can think of.