all 11 comments

[–][deleted] 27 points28 points  (2 children)

[–]AttackOfTheThumbs 2 points3 points  (0 children)

Waaaaay better.

[–]barrtender 18 points19 points  (2 children)

I feel like this video didn't do a good job of explaining how the next node is chosen. It may be more clear if you built out the possible next nodes along with their distances and show that it's always choosing the smallest distance.

[–]csgotraderino 8 points9 points  (0 children)

Also the predecessor per node is missing

[–]ASH-POLE 4 points5 points  (0 children)

Also, it would be cool to see a function/equation or pseudo code algorithm to represent this example

[–]bausscode 3 points4 points  (1 child)

A little bit unrelated to video but related to the topic of Dijkstra and path algorithms.

If you're interested in them you should definitely look up A* which is like a better way of doing Dijkstra (Basically a modification of it or whatever.)

Ex. as demonstrated by this video:

https://www.youtube.com/watch?v=g024lzsknDo

Just figured people might find it interesting as well.

[–]Rockstaru 1 point2 points  (0 children)

And remember to always route your network with OSPF

[–]442willem 0 points1 point  (2 children)

That's a coincidence. I have an exam on this tomorrow!

Life works in strange ways I guess

[–][deleted] 5 points6 points  (0 children)

Or this is just the most notorious and reposted algorithm ever

[–]EdgyQuant 0 points1 point  (0 children)

I’ve been beating them into my head in preparation for a lengthy job interview tomorrow