The challenges and related solutions for remote Work

Ugizwenayo-Divine — Fri, 31 Jan 2020 07:09:12 +0000

Remote work is doing your work anywhere, you do not need to be in the office as it is remotely, you can work from anyplace that's make you feel comfortable.

As the remote work need some resources, The challenge I've been facing during remote work is the problem of connection, the internet is not always on our side, sometimes it goes slow or not working at all.
As remote work really need an internet,if it goes down then remote work will fail and that's will reduce the productivity of the team.

Everything can not be done remotely, there are some cases where you need to be onsite I can say. Through remote work, it will be difficult to deal with those problem(cases).

Sometimes we need help that can not be given through remote where you need to interact more with your teammates.

As there are some challenges, also there are related solutions.
For the problem of an internet on my part I had to first make sure that I have sufficient connection at least 15 minutes before the meeting with teammates.
You can check your connection by doing different tough or high connection needing staff like watch music on YouTube to make sure the internet will not deceive you.

Regarding the help that needs to be face to face with teammates, we had to use screen sharing , screen shoots to better explain what needs to be done or solved.

By concluding remote work leads to high productivity as everyone works from where he feels comfortable and at anytime that please him.

Event loop in nodejs

Ugizwenayo-Divine — Fri, 24 Jan 2020 02:19:11 +0000

Nodejs is a single threaded application. That means it executes instructions or all requests with a single thread.
In node js all request or operations are served by one thread that means there is one operation being executed at time.

So event loop is what allow nodejs to perform non-blocking operations.
Given it uses one thread in serving many requests, the request does not have to wait the completion of the first request, that's where event loop come into existence and allow one request to release the thread while waiting for I/O operations.

When there is a request, single thread is used to serve it but does not have to wait its completion once there are some executions being done for that request to complete like waiting for I/O inputs ,the single thread is serving another request.
Once the first request is done with other executions(I/O input are available) there is this event queue where messages notifying that data are now available go. Then the single thread will return to serve the first request.

This event loop allows non-blocking operations by offloading operations to the
kernel whenever possible.The event loop manages events(requests) by taking the first request on list and send it to be served or handled by the only one thread, also if the request is not using the thread that's when it offload event to the thread.

references:
https://nodejs.org/uk/docs/guides/event-loop-timers-and-nexttick/
https://nodejs.dev/the-nodejs-event-loop
https://blog.risingstack.com/node-js-at-scale-understanding-node-js-event-loop/

DEV Community: Ugizwenayo-Divine

The challenges and related solutions for remote Work

Event loop in nodejs