DEV Community

Cover image for Day 682 : Stop

Posted on

Day 682 : Stop

liner notes:

  • Professional : Went to bed late last night forgetting that I wanted to get up early to attend a meeting that was set to be friendlier to our Far East team members. I rather attend the meeting live than find time to watch the recording. Especially since Thursdays are meeting heavy days. I've really got to stop staying up late. Regardless of all that, I actually got quite a bit done. I'm super tired though. haha

  • Personal : Last night, I went through some tracks. Also played around with the authentication I set up for the starter project I deployed. I think I may be able to get some sort of authorization working as well. Then I did some research into database options. Yeah, spent a lot of time researching.

A brown and white alpacas looking at the camera standing in a green field with some shurbbary behind them in Waiheke Island, New Zealand

So, I did some more research and it looks like the functionality I was going to use a database for could be accomplished with another service I was going to use anyway. Going to try and code some stuff up and see if I can get it working. If I can, it would be one less thing to set up. Again, I want this to be as simple and straight-forward as possible since other people could be using it. Also want to go through tracks for the radio show and maybe watch an anime or 2 before going to bed.

Have a great night!

peace piece
Dwane / conshus /

Top comments (0)

An Animated Guide to Node.js Event Loop

Node.js doesnโ€™t stop from running other operations because of Libuv, a C++ library responsible for the event loop and asynchronously handling tasks such as network requests, DNS resolution, file system operations, data encryption, etc.

What happens under the hood when Node.js works on tasks such as database queries? We will explore it by following this piece of code step by step.