This is how serious I got this BST shit. Back to the roots, back to the fundamentals 🫡

feels like it, tbh xD

Ooooookay, seems like I got something, now there will be the reason for leetcode. Let's see how it goes. On top of that I would need to recall Linux internals, which is quite interesting topic.

During my prev interview at AWS, I was asked: "your server runs out of memory (disk), you deleted file, but there is still no memory, what can be the reason, and how to fix?"

Cool, so eventually I have finished 4 mocked interviews that people wanted to try. All of the were free, and interesting for me as interviewer.
We had 2 algo/DS interviews and 2 System Design interviews.
Formal feedbacks are sent, eventually I'm done.

Thank you for this experience, hope it was helpful. I was trying to do it as close as we are doing it at Microsoft.

What I realized - I like to be interviewee MUUUUUUCH more than interviewer, idk why and how it works.

Now some interesting stuff happened on AWS side as well. So leetcode is going full flight.
Now the commitment is 3 problems per day.

Daily challenge for today:
https://leetcode.com/problems/find-minimum-time-to-reach-last-room-ii/description/?envType=daily-question&envId=2025-05-08

good to practice shortest path

On Saturday or Sunday we are streaming, btw, so we can review BST deletion, and system design.

I'm thinking about changing our System Design approach on stream to the following:
We stop implementing MVP of system design solution in C#, instead - we are doing white boarding only, and maybe code some essential parts to make sure it will work.


After that we are reviewing other's system design solutions and analyze our mistakes (OR DETECT MISTAKES OF OTHERS 😁😁😁)

I have to accelerate guys, have time until Jun. LETS GOOO

Interesting...😁

GN

https://leetcode.com/problems/minimum-equal-sum-of-two-arrays-after-replacing-zeros

daily, fairly easy, try it, took about 5-10 minutes

Do you remember this part in the book "Designin Data-Intensive Applications by Martin Kleppmanns" about how twitter approached home timeline feature?

What they basically did, that instead of querying DB for all the tweets you follow - they are doing push approach, so you are basically reading from queue that is getting inserted when your followee pushes new tweet. One thing that for celebrities they left "query" approach.

I found the conference where it is explained with data, all path, problems, etc, very interesting:
https://www.infoq.com/presentations/Twitter-Timeline-Scalability/

LETS GO

motherfuckers, prev time 3 years ago they didn't have it I remember

Today we are streaming, usual schedule 20:00 Prague time. Leetcode, System Design + discussing AWS screening 😁😁😁

Started:

https://www.youtube.com/watch?v=bRofQ83SLb4&ab_channel=andreyka26_se
https://www.twitch.tv/andreyka26_

https://www.youtube.com/watch?v=G3cpafmjZ1c&ab_channel=andreyka26_se

got connection dropped, created new stream

Lets hack Pentagon