How Data Structures & Algorithms are Actually Used 

this comment says "1h ago" maybe you should teach them devs in google how to develop

@@lukmanalghdamsi3189 it was probably private earlier and he made it public later

I’m gonna assume you’re doing this worldwide as I’m in the UK. I was going to attend some sessions anyway, this would be a surplus. :))

Damn im late unlucky 😢

😂😂

Neko-sama, nowadays, all hail AI and data. Even your position as a royal among cats is threatened by the current datadom.

:D

Maybe, his data structures are miraculous.

He doesnt write algorithm,algorithm write itself for him

😂😂😂

Good question. He sorts by the created_at desc, so it is sorting the data in the DB, and then sorting again in the front-end by the vote count. I suppose that he does so because sorting by created_at date at db is the most common case, so when used the function is used in other places (the home page?), it does not need to be sorted in the front-end. In this case, as he was in the most upvoted posts page, it makes sense to reorder again. Also, he is not paginating the query made, which is kinda weird, because it will bring the whole table, a no-no. Maybe I missed something because I'm not very familiar with that ORM, so if that is the case, please ignore this statement. * It makes sense, but is debatable. Why is that so? Because you are reordering two times. Maybe it is pre-optimization, but a better approach here would be to sort by created_at desc by default, but also have parameters in the function to customize the order by. That way, the reordering only happens in the DB and does not need to occur again in the front-end. **Every approach has its advantages and drawbacks. Maybe the benefit of reordering only once at DB is not worth it because of the trade for complexity in the code. Example: sanity check the passed parameter, map parameters to table columns, how would you handle if you had to order by more than one column, creating indexes in the table so the order by is efficient, etc. If you want to deliver a MVP faster, sticking with his method is a better fit because you don't have to trouble yourself with that kind of thing early on, so this can be refactored latter on.

@@JoaoPedro-qt7dc Hmm I see , thanks for responding !

😂😂😂

😂

🤣🤣🤣

yeah bro i shocked when I saw them, i try a lot to find this types of website where we can see these types of things ,but I did not find it

hey bro, tell me if you found the video

Data Structures are all about ordering and arranging data in different ways... Depending on how you want to display or store data - you could have used different methods. In your case, you were storing the news feeds by date - which is essentially stored in a list (array?) in the database. If you wanted to store data in a different way, you could have depending on the app type and the amount of users using it...

@@centripetal6157 i was storing the data in database and when i select the data it comes back as a list of dictionaries, my query also brings the data in order from the database table before i even load it to list of dictionaries, this is good ( i think ) because I'm not giving any sorting possibilities for the user, it's just get data, load it to list and loop over it to display it

😂

😂

A hash number is unique, no two users can have the same hash # - which makes security better.

@@centripetal6157 and what about a unique number that auto increments? 😂

Well yes, that’s why I showed this lol but to pretend that understanding how they work is unnecessary is just ridiculous.