DEV Community: Divakar Kumar

Build Intelligent Outlook using Azure

Divakar Kumar — Wed, 31 Mar 2021 07:30:58 +0000

What problem are we trying to solve today?

Consider you are working for a company where they restricted access to outlook in your mobile or Consider you don't want to sync professional mail in your mobile. In either cases there might be a possibility where you will miss to respond back to an escalation mail or feedback mails on time .

Proposed solution :

1) We don't want to be disturbed for regular mails
2) We should make our outlook intelligent enough to know that we are only interested in escalation or feedback mails. Right now outlook can't categorize mails based on these sentiments of the contents.

So in this post, we will see how to make our Outlook intelligent enough to send out a message to our personal mobile number whenever there is an escalation / suggestion mails addressing to us.

Prerequisites :

Azure Logic apps
Azure Functions
Azure Cognitive services
Twilio

Architecture :

Steps to implement workflow :

Go to Azure portal : portal.azure.com
Get free azure subscription here : https://azure.microsoft.com/en-in/free/

Logic Apps workflow :

Choose your subscription and create Logic apps
Once logic app is created open the designer view

Select Blank Logic app

Search for Outlook in connectors and triggers and select trigger "When a new email arrives (v2)"

Mention your mail id in "To or CC" condition

In the next step choose Text Analytics as an operation and choose Detect sentiment (v2) as action , so that we can detect sentiment of the content of the mail

In the next step choose Azure function to categorize each sentiment score and in the request body point it to the documents of the sentiment analysis response

Now add condition based on the response of the azure function and if the response is ASAP or NEUTRAL , then send a text message to your registered number in Twilio account

Azure function workflow :

Based on the sentiment score , we will use azure function to categorize the content of mail that we receive.

Preview of the mail that we sent in earlier step:

Request to sentiment analyzer :

Response from sentiment analyzer :

And based on the below code snippet we will categorize the above mail as Negative and will tag it as ASAP message and send response back to logic app

Twilio workflow :

Once we got response from Azure function it will be send to Twilio workflow based on two conditions , It will check if the response is either ASAP or NEUTRAL . In either of these case we will trigger a message to our configured number in the portal as below

Act on negative feedbacks ASAP:

Finally, we made our outlook intelligent enough to send notifications on negative feedbacks from our client

Github Source code:

https://github.com/Divakar-kumar/SentimentWebhooks.Outlook

Further steps:

Please go ahead and fork the repository to make your outlook more intelligent, where you can implement custom logics based on the sentiment score.

☁️ ☁️Free Certification Multi-Cloud (Best of Breed) ☁️☁️

Divakar Kumar — Thu, 27 Aug 2020 19:26:33 +0000

Multi-Cloud (cloud 3.0 - 2019 and beyond)

Architects and engineers out there need to keep pace with the changing environment and While we are talking about strategies in private, public and hybrid cloud, Multi-Cloud is already here!.

According to IBM, 85% of enterprises are in a multi-cloud environment, but only 41% have a multi-cloud strategy. The challenges that the organizations are facing, outweigh the benefits they are accruing from the model.

Why Multi-cloud?

✅ Vendor flexibility

✅ Best of breed

✅ Negotiating power

✅ Failover and disaster preparedness

✅ Data sovereignty

Are you a certified AWS, Azure, GCP, OCI professional?

Aviatrix ACE Program

Recently I came across Aviatrix ACE program that enables us to develop competency in multi-cloud strategies.

The ACE program provides ongoing education that enables architects, engineers, and technical staff to develop advanced competency in native cloud capabilities and provides a framework for applying this knowledge to network architecture and design patterns in order to meet customer requirements.

🎫 Free coupon:
ACEONLINE ( $895 value course )

✔ Register here :
https://aviatrix.com/ace/

📆 Offer validity:
Till October 1st 2020

Demystifying [[environment]] in JavaScript Closure

Divakar Kumar — Tue, 26 May 2020 09:58:21 +0000

Hi all, For those who don't me I'm Divakar, Passionate developer with 5 years of experience in web and mobile development. I learned software development the hard way, following lots of confusing tutorials, failing to understand core concepts and finally having no idea how things work. So I wanted to help the community to
understand it in a better way without any hassle.

Before getting know about the closure i will start with couple of questions

Can you make a function to run only once ?

Can you make a function to memorize ?

By end of this article you will be able to answer those questions.

Closure:

Every function in JavaScript is bound to have a [[ environment ]] or [[ scope ]] hidden property ,that have reference to the current lexical environment of their creation.

Do remember that lexical environment is theoretical and no one can get this object in console and manipulate it directly

Closure is a function that also have this hidden property along with it ,which stores the state of the current lexical environment, by which it can have access to outer variables. This makes closure in JavaScript as one of the most powerful concept.

Usually, a lexical environment gets removed from memory along with all the variables after the function calls finishes . But this is not the case in CLOSURE, it gets tied to the memory even after the function call finishes.

From now on i will be calling this hidden [[ scope ]] or [[ environment ]] property as a backpack.

In the above function , when getCounter() function call gets executed it runs in the execution context ,

Step 1: It searches for counter variable in the local memory of the execution context

Step 2: JS Engine cannot find the counter variable in the local memory of the execution context, now it looks into the backpack - Voila ! we found the counter variable and it picks up

Step 3: It increments the counter and the value gets modified in the backpack ( persistent memory ) as well. So if the getCounter() is called again , then the counter variable value will be incremented to one.

In the above code you could see that each time you initalize a variable with makeNewCounter , there will be independent backpacks available to getCounter and anotherCounter.

Great ! 🎉🎉 Now the next time you use closure , you have clear idea what is happening behind the scenes.

Since now you know about the closure and its actual working behind the scenes try to answer my first 2 questions

Can you make a function to run only once ?

Can you make a function to memorize ?

How a developer should handle Code reviewer?

Divakar Kumar — Mon, 11 May 2020 10:46:15 +0000

I would suggest you to read my previous post before getting into this topic . check here for my previous post

How to become a better Code Reviewer - Part 1 : Code Review

Divakar Kumar ・ May 9 ・ 2 min read

#codenewbie #computerscience #csharp #java

Having said that now you get to know the mindset of a Code Reviewer , so as a developer/ author of the code let's see what are various responsibilities for us in order to deliver a product successfully.

Handling Code Reviewers:

Don't take it personal:

We have a clear idea of how a mindset of a code reviewer is , the goal of him is to maintain our code base quality. So when he/she provides a review comment of your code, think of it as their attempt to help you, the codebase, and Company, rather than as a personal attack on you or your abilities.

1) Don't respond in anger to review comments.
2) If a reviewer's comment is not in a professional or polite or constructive way then talk to him in person or send a private mail to have a discussion about it.

Fix:

If a reviewer doesn't understand a particular piece of code it is obvious that other developers who is gonna work in this code base maybe in future will get to feel the same way. so rather than adding comments in the tool do fix the code. Try to find a simpler way to achieve the functionality.

Think:

No matter how certain you are if a reviewer made a suggestion on your code base take a step back. Think about “Is the reviewer correct?”

If you can’t answer that question, it’s likely the reviewer needs to clarify their comments.

If you have considered it and think that you are right then respond with an explanation that why your way of approaching the solution would be better.

Thanks ! Leave a comment :

Thanks all for reading through this topic. Please leave a comment about your way of handling a code reviewer.

How to become a better Code Reviewer - Part 3 : How to write code review comments?

Divakar Kumar — Sat, 09 May 2020 13:03:55 +0000

When it comes to writing code review comments do make sure that you are polite ,kind and encourage developers .

Respect:

1) Be kind and helpful to the developer whose code you are reviewing.
2) Make sure that you always comment about the code and not about the developer.

Explanation:

1) Always make sure to explain why you are making the comment
2) Try to give a "good/valid" example so that it would help developer to understand. It is always necessary to provide examples.

Guidance:

1) Don't provide the solution or write code for developer rather provide useful information so that it is developer's responsibility to fix a change list.
2) Maintain a balance between pointing out the problems and providing a guidance.

Thanks:

Thanks all for reading through this series . Hope you will be trying to implement this in real time practices and become a better code reviewer. If you like my post please do give feedback below , i will try to change if there are any mistakes in my future posts.

Banner Image Courtesy : Business vector created by freepik - www.freepik.com

How to become a better Code Reviewer - Part 2 : What does a Code Reviewer look for?

Divakar Kumar — Sat, 09 May 2020 12:30:53 +0000

What Do Code Reviewers Look For?

Design:

So what do i mean by design? I refer to design by the overall design of the change list.

1) Check whether all the interactions of code in the change list make sense to you.
2) Check whether the change is from library or the actual codebase.
3) Check whether it integrates well with rest of the system.
4) And also make sure whether it is a good time to add this functionality.

Functionality:

1) Check whether the author of the code have done what he/she was intended to do based on the change list.
2) Think in terms of the end-users and also the developers who is going to use this code in future .

3) Think about the edge cases , looking for concurrency problems , and making sure that there are no bugs that you see just by looking at the code.
4) If you don't have any idea about what is going on , you can have the developer/author of the code to give you a demo of the functionality before going through the code.
5) If any kind of parallel programming is going on in the change list make sure there are no deadlocks or race conditions

Code Complexity:

1) If the author of the code approached more complex way and also in a way it can't be understood quickly then it means that he/she is likely to introduce bugs when they try to modify this code in future.
2) Generics are good but not always. A developer should know when it is likely to be approached using generics and when not to.

Unit Testing:

1) Never approve a pull request that doesn't have corresponding unit test, integration, or end-to-end test. In general , tests should be added in the same change list

2) Check whether tests actually fail when the code is broken , do they make simple and useful assertions , are they separated appropriately between test methods.
3) Tests are equal importance as of to the actual code base , so check for complexity in unit test as well.

Naming:

A valid name is enough to fully communicate what the actual functionality is.

1) Check whether the author of the code uses good/valid name for everything . It can be variable, method,class declaration literally everything.

Comments:

Comments are useful when they explain why some code exists and it should not be a place where to explain everything the code is doing. If the code isn't clear enough to explain itself , then it should be made simpler.

1) Check whether there are clear comments and also whether those comments are actually necessary.

Documentation:

1) Ask for documentation from the author of the code and also ask them to update associated documentation for the code change that they made
2) Also consider whether a part of the documentation need to be deleted or so, when the particular functionality is removed.

Congratulations:

Next Steps:

How to become a better Code Reviewer - Part 3 : How to write code review comments?

Divakar Kumar ・ May 9 ・ 1 min read

#codenewbie #computerscience #csharp #java

Banner Image Courtesy : Business vector created by freepik - www.freepik.com

How to become a better Code Reviewer - Part 1 : Code Review

Divakar Kumar — Sat, 09 May 2020 12:30:33 +0000

Code Review:

Code review has been widely adopted by and adapted to open source and industrial projects. It is a process where someone other than the author(s) of the chunk of code evaluates the code. Most of the companies adopted this process to ensure quality of the code and product.

The purpose of code review is to make sure that the overall code health of codebase is improving over time , having said that this becomes tricky since over time codebase degrade when a team is under significant time constraints and they feel to take shortcuts inorder to complete the tasks.

As a reviewer you want to ensure that codebase stays consistent and maintainable.

Prepare yourself:

Before proceeding with a code review I always prepare myself to accept these things

No Fear The first and most popular is the fear of offending an author of the code. Don't pretend that you didn't see his/her bugs today ,so that tomorrow he/she will ignore your mistakes.This is the kind of attitude this fear produces.
No Perfect code Key point is that there is no such thing as "perfect" code only a "better" code. Don't make the author to change every tiny piece of the code ,before granting the approval.Rather, you should seek continuous improvement in terms of maintainability , readability and understandability of the system.
Mentoring Sharing knowledge is part of improving the code health of system over time. You can leave comments that help a developer to learn something new .

Next Steps:

How to become a better Code Reviewer - Part 2 : What does a Code Reviewer look for?

Divakar Kumar ・ May 9 ・ 3 min read

#codenewbie #computerscience #csharp #java

Banner Image Courtesy : Business vector created by freepik - www.freepik.com

DEV Community: Divakar Kumar

Build Intelligent Outlook using Azure

What problem are we trying to solve today?

Proposed solution :

Prerequisites :

Architecture :

Steps to implement workflow :

Logic Apps workflow :

Azure function workflow :

Request to sentiment analyzer :

Response from sentiment analyzer :

Twilio workflow :

Act on negative feedbacks ASAP:

Github Source code:

Further steps:

☁️ ☁️Free Certification Multi-Cloud (Best of Breed) ☁️☁️

Multi-Cloud (cloud 3.0 - 2019 and beyond)

Why Multi-cloud?

Are you a certified AWS, Azure, GCP, OCI professional?

Aviatrix ACE Program

Aviatrix ACE Program

🎫 Free coupon: ACEONLINE ( $895 value course )

🎫 Free coupon:

✔ Register here : https://aviatrix.com/ace/

✔ Register here :

📆 Offer validity: Till October 1st 2020

📆 Offer validity:

Demystifying [[environment]] in JavaScript Closure

Can you make a function to run only once ?

Can you make a function to memorize ?

Closure:

Can you make a function to run only once ?

Can you make a function to memorize ?

How a developer should handle Code reviewer?

How to become a better Code Reviewer - Part 1 : Code Review

Divakar Kumar ・ May 9 ・ 2 min read

Handling Code Reviewers:

Don't take it personal:

Fix:

Think:

Thanks ! Leave a comment :

How to become a better Code Reviewer - Part 3 : How to write code review comments?

Respect:

Explanation:

Guidance:

Thanks:

How to become a better Code Reviewer - Part 2 : What does a Code Reviewer look for?

What Do Code Reviewers Look For?

Design:

Functionality:

Code Complexity:

Unit Testing:

Naming:

Comments:

Documentation:

Congratulations:

Next Steps:

How to become a better Code Reviewer - Part 3 : How to write code review comments?

Divakar Kumar ・ May 9 ・ 1 min read

How to become a better Code Reviewer - Part 1 : Code Review

Code Review:

Prepare yourself:

Next Steps:

How to become a better Code Reviewer - Part 2 : What does a Code Reviewer look for?

Divakar Kumar ・ May 9 ・ 3 min read

🎫 Free coupon:
ACEONLINE ( $895 value course )

✔ Register here :
https://aviatrix.com/ace/

📆 Offer validity:
Till October 1st 2020