LEETCODE 21 (JAVASCRIPT) | MERGE TWO SORTED LISTS

Hey everyone. Check out this in-depth solution for leetcode 21.

[@indiajackson5959]

I have an interview with Google and your style of teaching the foundations and patterns speak to the mathematician in me!! You deserves more views!!

[@andygala888]

Glad the vids are helpful :)

[@ayshasinara4746]

yeah I agree with you 👍

[@OnEwHoRiDesLinEs]

did you get the job at Google

[@indiajackson5959]

Nope lol@@OnEwHoRiDesLinEs

[@Grahammpatton]

wow this is the best explanation. That really made me realize exactly how simple the solution is. thank you!

[@fernandosalas4885]

The best explanation ever. Thanks

[@JoseLopez-wh7xe]

Excellent, very well explained! I would say that he made it look too easy, he could have left us more so that we could deduce it ourselves, but he left everything explicit. 😊

[@pinpon163]

I don't know if it is me, but it seems that the way the Linked List is implemented for this problem is not very intuitive. I am not talking about your solution, but the two lists they are giving us.

[@kazno4273]

Definitely not intuitive. I'm also struggling to understand the design of linkedNode rather than the question itself

[@berkantasci8811]

Interesting to think this was an exam question in my first year and companies like amazon and google use it in their interviews. Especially because my school was and still is kind of shit

[@JaredFL]

I'm not understanding why dummy is returned instead of prev? Since prev holds the order we set

[@nicolasteofilo]

I'm not understanding too

[@jenniferfan8155]

I have the same question.

[@sammi841017]

I had the same question as well, but then I logged it and think that because prev was only the one we use to track the 'current node value' We get null for prev.next and prev itself is [4]

[@HEBUSTORLL]

Basically dummy is linked and gets the pushes along the way, while prev acts like an index whosz value gets reset every time to keep track of where we're at. Returning prev would be the same as having a for loop, and returning [i]

[@mrawesome1821]

It's a little quiet, but great video. Thank you Andy!

[@quangtrungo6146]

Thanks very much , keep doing bro.

[@kirillzlobin7135]

Maaan you are the legend

[@Meowthrzy]

I'm having a hard time on this problem thanks!

[@stephanieonyekaba8274]

This was very helpful ! can you zoom in a bit for future vids ? The text is kinda small :/

[@anaelennaemeka4078]

Thanks Very much

[@eshw23]

For the first output on leetcode, why the heck does it return the whole list when it is just asking for the head? That makes literlaly no sense.

[@Supersoaker-xy2cr]

damn thanks bro

[@cmdv42]

💯✨

[@Wanderlustclusterfuck]

hey, i have a question. i thought it said you can go from -100 to 100. why did you do -infinity?

[@nid30]

Yes, it is quite unclear what negative infinity is doing there and what is its job?! Someone please clarifyyyy... 😢😢😭😭

[@junjun22able]

@@nid30 It just a dummy, and as he said "You can set to anything". He just set it to -Infinity cause it's the lowest value in JS and just to make sense but actually you can put anything to it like 0, 100, 1000 cause it doesn't matter anyway. You will not returning this node value, only those nodes after it which is the dummy.next. I hope, I explained it well. ^___^

[@nicolasteofilo]

@@junjun22able great explanation

[@Supersoaker-xy2cr]

@@junjun22able so its just a declared head?

[@melanieprevot4926]

Hi, thank you for the video. Just one thing: why prev = dummy but we cannot return prev.next ? Not quite understand dummy part.

[@HEBUSTORLL]

Because the value of prev gets re set on every loop to keep the track. Dummy is a linked node list, so it's like an empty string that you fill as loops resolves, and prev is just the index

[@surajpadalkar1670]

always remember if you lose your head the linked list is useless dummy is for that purpose only never lose the head of linked list as your previous is updated after every iteration it cant store it so to keep track of your head dummy is used

[@_tanzil_]

Am I too newbe to understand 😢

[@exe.m1dn1ght]

i didn't understand one thing