DEV Community: Enakshi Pal

Users - The Guide to your Product Success.

Enakshi Pal — Tue, 17 Sep 2024 13:09:41 +0000

Whenever we use a new product, the first thing we see is...

“How cool is the new feature? How eye catchy and engaging it is?”

Building eye-catchy features is cool BUT, behind every successful product lies one simple question.

Is this product really solving the PROBLEM?

We create products to solve real problems for real people. It's not about adding in as many features as we want. It's about understanding our users’ daily struggles and making their lives easier.
When we focus on solving pain points, we build products/features that truly connect with users.
And the first step in that journey starts by knowing our users.

Why Users (Not Features) Are the Heart of Every Product?

It’s really tempting to dive into product development with flashy features, but wait!

What problem are we solving for our users?
People use apps or services mostly to look for a solution. And that solution can only come when we understand the pain points they experience daily.

This is where User personas help us move ahead with the solution.

But, What Are User Personas?

You can think of user personas as detailed profiles that represent your target audience. They help you go beyond the generic assumptions and get into the mindset of your users—their challenges, goals, and pain points.

The main ingredient to add before creating the user personas, is to identify the pain points.

How do we do that?

The BASICS.

1. Do the Talk!
Talk to your users. Whether it’s a one-on-one interview or a quick survey, ask them what frustrates them the most. What’s not working? What’s taking up too much time? Their answers will reveal what they really need.

2. Observe their Behavior.
Watch how users interact with your product. Where do they struggle? What tasks take them too long? Where do they give up and leave? This can give you insights into unseen pain points.

3. Do some Data Analytics!
Sometimes the pain is in the numbers. Look at your product’s data. Are users dropping off after a certain point? Low engagement or high bounce rates can point to friction in the user experience.

4. Customer Support Knows Everything!
Your support team talks to users every day and knows the common complaints. Tap into that resource to see recurring issues.

5. Check Out Competitor Reviews.
Look at what users are saying about similar products. Where are those products failing, and how can YOU do better?

Now that we have identified the pain points. Let's look at the User Personas.
Let's say we are fixing the problem for the Uber Users.

1. Identify the Goals!
What are the specific outcomes the user hopes to achieve?
Example: “Sasha wants to commute comfortably and on time without worrying about parking or transit delays.”

2. What's their Motivation?
What drives the user to use your product? Why do they care?
Example: “Sasha values convenience and reliability, which is why she uses Uber because it saves her time and reduces the stress of finding a ride.”

3. What is making them frustrated?
What are the roadblocks or frustrations the user experiences?
Example: “Sasha is frustrated by the surge pricing during peak hours and the inconsistent availability of drivers when she’s in a hurry.”

4. Reaction Matters?!
How does the user typically act or respond to similar products?
Example: “Sasha prefers apps that are easy to use and offer transparent pricing. She’s more likely to stick with Uber if there are rewards or loyalty perks.”

5. What's next?
Jobs To Be Done (JTBD).
What is the user trying to achieve? This is the core task they need to get done.
Example: “Sasha, a young professional, needs a reliable and affordable way to get to work every day without the hassle of public transportation.”

When we know the answers to these questions, we are not just guessing what users need but, we have a clear guide to building something that feels like it was made specifically for them!

Let your users be the guide, and your product will naturally thrive!

From Assumptions to Answers with User Research

Enakshi Pal — Fri, 01 Mar 2024 13:11:21 +0000

As human beings, we tend to make assumptions to solve a problem which can either make or break success. However, assumptions won’t help us achieve the goal, reality will.

To gap this bridge between the assumptions and reality, and to offer the right solution, we will perform, User Research.

Now it might seem intimidating at first glance but, it's actually quite accessible!

Yes, rather than a complex puzzle to solve, it is a valuable discipline to master.
It is a powerful tool that helps us uncover the "why" behind user behavior, turning uncertainty into actionable insights.

Through user research, we can gain crucial insights into our target audience, including their goals, needs, motivations, and much more.

Let us now get started with how we can perform the User research and ask effective questions to the users.

The first step is to define our research goals and objectives:

When we have the problem statement with us, we make assumptions about it and ask questions to our customers accordingly.
While assumptions can be a starting point, they are not sufficient for defining research goals. To achieve this, we need to develop hypotheses that can be tested.

Hypotheses are nothing but, assumptions in testable forms.

Let us look at the Seeds of Research, i.e. Assumptions and Hypotheses with respect to the below example.

Imagine a scenario – You're building a side hustle app which targets to fix a problem where users find it difficult have a side project which they can use to make their career transition.

Assumption 1: Some people may struggle to come up with side project ideas or have too many ideas to choose from.

Hypothesis 1: “I believe that people who want to acquire new skills struggle to choose a project idea because mostly they don’t have enough ideas or may have too many ideas to choose from.”

Assumption 2: Some people may even struggle to start their side project, because they have issues to allocate enough time to it, since they think of it as a non-priority task.

Hypothesis 2: “I believe that people who want to acquire new skills experience issues of allocating time to work on their side project, because mostly they perceive it as a non-priority task.”

Now that we have developed the respective hypotheses, let’s move towards defining the research goals and objectives.

• Goal: This is the central question among all the assumptions or hypotheses we made that our research aims to answer.
• Objectives: Specific, measurable statements outlining what we want to achieve.

Let’s understand how we can specify our objectives.
Action verbs become your allies in formulating impactful research objectives. Let us again look into the example with respect to our Side Hustle App:

• Identify: "Identify ways people plan their side hustles and the tools they use."
• Understand: "Understand what makes it easy for people to plan their side projects and what makes it difficult."
• Define: "Define the key pain points users encounter when finding the tools to execute their project"

After we have defined our goals and objectives, now its time to select the research methods which we can use to structure the why and how much of our product accordingly.

Let us understand this using the below table, how to choose the right user research method based on our research goals and objectives.
However, it is not limited to choose only one method and get going; it is totally based on the requirements.

In our case, we will go with in-depth interviews, i.e. the Qualitative research method as our primary discovery method.

Why have we chosen this method?

The reason being in our case, we need to look into the customer pain points and identify how much relevant is the problem to our customers.
These interviews are relatively easier and will be more effective for user research, in our case.

By this, we have learned more about user research which can eventually help us answer all of our assumptions. But we have to remember that, user research isn't a one-time expedition; it's an ongoing journey. Keeping our ears to the ground and listening to the customer feedback can craft the solution to our problem even better!

Let’s embrace user-centric approach and continuous learning!

Beyond What: 'Why?' Matters in Product & Customer Success

Enakshi Pal — Thu, 15 Feb 2024 14:03:40 +0000

When we say we are curious about a certain thing, what is the first question that comes up in our mind?

"Why is this thing designed this way?"

"Why isn't it designed differently?"

All those "why's" come up.

In the world of creating products and helping customers succeed, there's a simple yet mighty question that can make all the difference: 'why?'

For example, let's consider a new mobile app feature that is a chat function, where asking "why?" might prompt questions like:

"Why is the chat interface designed with these particular features?"
"Why isn't there an option for users to customize their chat backgrounds?"
"Why is the send button located in this specific area?"

Exploring these "why" questions allows us to unearth motivations, user needs, and potential pain points for both product and customer success.

Let's take a closer look at why 'why?' matters, and how it can transform the way we approach our work.

The 'Why?' in Product Management:

Finding Purpose: Instead of just adding features for the sake of it, asking "why?" helps us uncover the real problems our product solves. It's like giving our product a mission!

Getting Inside Customers' Heads: Features are cool, but do they really help our customers?
'Why?' prompts us to understand if our customers truly need and want those. It's like unlocking a secret code to make them happy!

Making Smart Choices: With limited time and resources, we need to make smart decisions.
'Why?' helps us prioritize what's important and avoid adding unnecessary stuff. It's like having a trusty compass to guide us!

Telling a Compelling Story: Features alone don't sell products; stories do.
A 'Why?' helps us craft stories to grab attention and make people excited. It's like turning a boring description into an exciting movie trailer!

Let’s dive into some real life instances:

Let’s say, you are building a new language learning app, and you need to convey it to your customers. How will you start your conversation as?

• "We have just built a new Scheduling tool," Instead of that, say: "We built a tool to save professionals’ time on scheduling."
• Now if you add a new feature and say “Our app has new filters," instead, say: "We added filters to help users find what they need faster."

Let's unfold another aspect of The ‘Why’ Equation!

Like we say, our end goal is to make customers happy, which makes understanding the "Why" equation crucial in Customer Success too.

The WHY Equation in Customer Success.

Understanding Goals: Customer success is about more than just fixing problems; it's about helping customers achieve their goals. 'Why?' helps us understand what they want to achieve since we are their trusted advisors!

Breaking Down Barriers: Problems will pop up, but 'why?' helps us figure out why they happened. It's like being a detective and solving mysteries to help our customers succeed!

Building Friendships, Not Just Relationships: Customer success is about building trust and connection. 'Why?' helps us have real conversations and show that we care. It's like turning customers into our Partners in Success!

Let’s dive into some more examples.

• Instead of a boring "How can I help you today?" email, ask: "What are you hoping to achieve with our product this week?"
• Let’s say, you have just fixed a bug and instead of saying “We have just fixed a bug”, ask: "How has this issue impacted your progress?"

A Note…

• Asking "why?" isn't about getting an answer; it's about really understanding.
• Encourage your team to ask "why?" too—it's super important!
• 'Why?' helps us connect with our users, make better decisions, and create products and experiences that truly matter.
By asking "why?" and listening to the answers, we can unlock the magic within our products and build relationships that last a lifetime.

So, let's keep it simple and unlock true understanding and guiding our customers towards sustained success!

If you were given an option to change your role as a Christmas gift from Santa, what role would it be?

Enakshi Pal — Sun, 24 Dec 2023 14:46:27 +0000

Hey all!👋
Since it's the Christmas Eve 🎄🎁
What would you all have asked for?

Are you following the Best Coding Practices?

Enakshi Pal — Tue, 19 Dec 2023 10:21:51 +0000

In the vast landscape of software development, to deliver the modules on time, as developers we often forget to adhere to the best practices.

Well, understanding and implementing coding standards is akin to mastering the secret language that makes code not just work, but work well.

Even experienced developers occasionally slip up on these standards, surprised?

For those just stepping into the coding arena, this exploration serves as a valuable roadmap. It's not just about following rules for the sake of it; it's about learning the language of collaboration and efficiency that can set you apart in the corporate coding realm.

Whether you're a seasoned coder or a fresh face eager to dive into the corporate coding scene, this blog will guide you to unravel the significance of coding standards in creating software that's not just functional but shines in the eyes of industry experts.

Here in this blog, we will look at the examples in two of the most popular languages, Java and Python, about how coding standards can become the compass leading us to success in the dynamic world of corporate software development.

Why Coding Standards Matter:

Consistency Enhances Readability:

Why: Consistent coding styles make it easier for developers to understand and collaborate on projects. It streamlines comprehension and reduces the learning curve for new team members.
Example (Java):

 // Inconsistent Naming
 int calculateSum(int x, int y) {
     return x + y;
 }

 // Consistent Naming (CamelCase)
 int calculateSum(int firstNumber, int secondNumber) {
     return firstNumber + secondNumber;

Example (Python):

 # Inconsistent Naming
 def calculate_sum(x, y):
     return x + y

 # Consistent Naming (Snake_case)
 def calculate_sum(first_number, second_number):
     return first_number + second_number

Indentation for Clarity:

Why: Proper indentation improves code readability, aiding in the visual structure of the code and making it easier to follow.
Example (Java):

 // Improper Indentation
 public void displayInfo() {
 System.out.println("Information");
 }

 // Proper Indentation
 public void displayInfo() {
     System.out.println("Information");

Example (Python):

 # Improper Indentation
 def display_info():
 print("Information")

 # Proper Indentation
 def display_info():
     print("Information")

Commenting for Understanding:

Why: Comprehensive comments provide insights into the logic and purpose of code, fostering better collaboration and easing the maintenance process.
Example (Java):

 // Unclear Code
 int result = x + y; // Calculate result

 // Clear Commenting
 int sum = x + y; // Calculate sum of x and y

Example (Python):

 # Unclear Code
 result = x + y  # Calculate result

 # Clear Commenting
 sum_result = x + y  # Calculate sum of x and y

Unused Code Cleanup:

Why: Removing unused code enhances codebase clarity, reduces complexity, and helps in maintaining a lean and efficient application.
Example (Java):

 // Unused Method 
 public void unusedMethod() {
     // Code here
 }

 // Remove Unused Method

Example (Python):

 # Unused Function
 def unused_function():
     # Code here

 # Remove Unused Function

Testing and Error Handling:

Why: Rigorous testing and robust error handling ensure the reliability and stability of the software, preventing unexpected issues.
Example (Java):

 // Inadequate Testing
 public int divide(int x, int y) {
     return x / y;
 }

 // Improved Testing with Error Handling
 public int divide(int x, int y) {
     if (y != 0) {
         return x / y;
     } else {
         throw new ArithmeticException("Cannot divide by zero");
     }

Example (Python):

 # Inadequate Testing
 def divide(x, y):
     return x / y

 # Improved Testing with Error Handling
 def divide(x, y):
     if y != 0:
         return x / y
     else:
         raise ValueError("Cannot divide by zero")

Security Considerations:

Why: Adhering to security guidelines safeguards against vulnerabilities, protecting the application and user data from potential threats.
Example (Java):

 // Vulnerable Code
 String userInput = request.getParameter("input");
 processInput(userInput);

 // Secure Input Processing (Sanitization)
 String sanitizedInput = sanitizeInput(userInput);
 processInput(sanitizedInput);

Example (Python):

 # Vulnerable Code
 user_input = request.get("input")
 process_input(user_input)

 # Secure Input Processing (Sanitization)
 sanitized_input = sanitize_input(user_input)
 process_input(sanitized_input)

Code Reusability:

Why: Writing modular and reusable code components reduces redundancy, promotes maintainability, and accelerates development.
Example (Java):

 // Non-reusable Code
 public int calculateSum(int x, int y) {
     return x + y;
 }

 // Reusable Code
 public int calculateSum(int... numbers) {
     int sum = 0;
     for (int num : numbers) {
         sum += num;
     }
     return sum;

Example (Python):

 # Non-reusable Code
 def calculate_sum(x, y):
     return x + y

 # Reusable Code
 def calculate_sum(*numbers):
     return sum(numbers)

Declaring Constants:

Why: Using constants enhances code readability, centralizes configuration, and facilitates easier modifications.
Example (Java):

 // Without Constants
public double calculateArea(double radius) {
return 3.14159 * radius * radius;
}

// With Constants
public static final double PI = 3.14159;
public static final double EARTH_RADIUS = 6371.0;
public double calculateArea(double radius) {
 return PI * radius * radius;
}

Example (Python):

 # Without Constants
  def calculate_area(radius):
      return 3.14159 * radius * radius

 # With Constants
   PI = 3.14159
   EARTH_RADIUS = 6371.0

  def calculate_area(radius):
      return PI * radius * radius

Easy Modification for Collaboration:

Why: Structuring code for easy modification enables smoother collaboration, allowing developers to work seamlessly on different parts of the project.
Example (Java):

  // Hard-to-Modify Code
  public void processUserData(String name, int age, String address) {
      // Code here
  }

  // Easy-to-Modify Code
  public void processUserData(User user) {
      // Code here
  }

Example (Python):

  # Hard-to-Modify Code
  def process_user_data(name, age, address):
      # Code here

  # Easy-to-Modify Code
  def process_user_data(user):
      # Code here

Null Checks:

Why: Incorporating null checks prevents null pointer exceptions, ensuring more robust and error-resistant code.
Example (Java):

  // Null Check (Good Practice)
  if (object != null) {
      // Code here
  }

  // Performing Operations Safely (Checking for Null)
  User user = getUser();
  if (user != null) {
      // Code here
  }

Example (Python):

  # Null Check (Good Practice)
  if object is not None:
      # Code here

  # Performing Operations Safely (Checking for Null)
  user = get_user()
  if user is not None:
      # Code here

Avoiding DML Inside Loops:

Why: Executing Data Manipulation Language (DML) operations inside loops can lead to performance issues. Batching operations outside the loop is more efficient.
Example (Java):

  // Avoiding DML Inside Loop (Good Practice)
  List<User> usersToUpdate = getUsersToUpdate();
  List<User> updatedUsers = new ArrayList<>();

  for (User user : usersToUpdate) {
      // Modify user data here
      updatedUsers.add(user);
  }

  // Perform a single update outside the loop
  updateUserProfileBatch(updatedUsers);

Example (Python):

  # Avoiding DML Inside Loop (Good Practice)
  users_to_update = get_users_to_update()
  updated_users = []

  for user in users_to_update:
      # Modify user data here
      updated_users.append(user)

  # Perform a single update outside the loop
  update_user_profile_batch(updated_users)

By now we have understood that coding standards are the backbone of well-organized and maintainable codebases. They foster collaboration, reduce bugs, and enhance the overall quality of software.

So, let’s make sure to follow the coding standards and contribute to the creation of robust and efficient applications, ensuring successful deliverables.

Tech and Wellness: Navigating through the Complicated Relationship

Enakshi Pal — Mon, 25 Sep 2023 17:30:36 +0000

Welcome to the Tech Roller-Coaster, where the smartphone’s buzz is our wake-up call, and the day starts with a scroll through the fitness trackers that motivate us to stay active or with a scroll through the social media circus.

We eat, we walk, we sleep, whatever we do, we get that one friend of ours, always standing by our side. Yes, the “constant” of our lives, our “digital confidant”! We cannot help but appreciate the convenience it offers.

But what exactly are we talking about?

A tool or a friend that can open doors, connect worlds, and even unveil hidden potentials.

By now you have guessed it, right?

Yes, we are talking about Tech, and the journey of how technology can be a double-edged sword, both a lifeline to prosperity and a potential threat to our overall health.

The relationship between tech and our well-being resembles a fascinating blend of cooperation, tension, and everything in between.

To keep up with the pace in the tech media race, we tend to forget our well-being, be it physical or mental.

We have all experienced the benefits of a new gadget and the frustration of a glitchy app, but how does this complicate our overall wellness?

Let us dive in and start the entertaining exploration of this intriguing tech-well-being relationship!

In this digital age, we order our favorite food online, do grocery shopping online, and even learn a new language — all with a few taps on a screen.

It is a partnership that keeps getting stronger!

However, every partnership has its moments of friction, and the tech-wellness team is no exception!

The constant notifications, endless scrolling, and the pressure to be "always on" often leave us feeling overwhelmed and anxious, and not to forget, all of this often eventually lead to having a Fear of Missing Out.

Yes, you read it right!

One of the most unseen fears is the Fear of Missing Out (FOMO). We keep scrolling through our Instagram Feed and gaze longingly at people's perfectly filtered lives and wonder “Why isn't my life that fabulous?”

And then we neglect the fact that for every Instagram-worthy moment, there is always a blooper reel behind the scenes.

Like we all know, to maintain a healthy relationship with anything in this world, one must master the art of balancing. Similarly, to maintain a healthy relationship between the tech and our well-being, we need to learn when to unplug and when to reconnect with the real world.

Apparently, smart devices are powerful tools, but they should not dictate our lives. Setting boundaries, like a tech-free hour before bed or a digital detox weekend, can work wonders for our well-being.

While we are talking about the “digital detox” and being away from tech for some time, we should also not forget about how positively technology is stepping up to support our wellness.

How can we overlook the importance of the smart devices, i.e. the “wearable computers” which are often seen on our wrist?

Yes, you guessed it right!
The “smart” watch or the fitness band has increasingly raised its demand due to convenient access to notifications, health, and fitness tracking etc. It has also increased our daily productivity by streamlining our daily tasks!

Yes! This is the same technology that is a source of stress as well as a source of solutions for our well-being.

Now that we have explored one side of tech, let us jump on to see what is there on the other side!

One of the most important aspects of our lives, which we fight for, cry for, fall for and what not!

Success, career, money, etc. Familiar words, right?

Yes. In the quest for our success and financial stability, technology has played a significant role in opening countless opportunities to earn money. From freelance gigs to online businesses, the possibilities are endless.
Let us not forget about the fact that tech has helped build careers on the way and people are dependent on it as their daily income.

But in our relentless pursuit of success, we often forget to check in on the most crucial assets we possess — our mental and physical well-being.

There comes again the conflict in the relationship! Well, these moments of conflict are the heart and soul of our digital age.
In this epic battle of Tech vs. Wellness, the real hero is our ability to adapt, evolve, and find harmony in the digital age.

As we navigate this complex relationship, we discover that the tech-wellness relationship is not just about competition; it is about finding moments of peace within the digital storm.

Eventually, tech and wellness do not stand as rivals but as partners in our journey towards a balanced and healthier life.

In the end, it is about making technology work for us, enhancing our well-being, and creating a digital age that is not just engaging and fun but also fulfilling. So, let us embrace this holistic approach and strive for a life where we thrive all financially, physically, and mentally in terms of well-being.

Salesforce Simplified: Unlocking the Basics for Beginners.

Enakshi Pal — Thu, 18 May 2023 13:12:40 +0000

Welcome to the extraordinary year of 2023, where innovation is the key to success in this fast-paced digital world, which is spinning at lightning speed!

Businesses and individuals are constantly seeking innovative solutions to manage their data & operations to stay ahead of the competition.

This is where the Cloud comes into play, offering a revolutionary approach to computing that has transformed the way we store, access & utilize information.

Now that was a traditional understanding, wasn’t that?

So according to the title, we were supposed to discuss about Salesforce, right?

Hold on, I will simplify all of this for you with a simple example.

Imagine you're running a lemonade stand on a scorching hot day, and the demand for your delicious lemonade is skyrocketing. You're pouring cups of lemonade left and right, but you're starting to feel overwhelmed. That's when the magical cloud comes to your rescue!

Cloud Computing, like a friendly cloud floating above your lemonade stand, swoops in to save the day! It's like having an army of invisible helpers who handle all the heavy lifting for you. Instead of relying on your tiny stand and limited resources, the cloud provides you with a supercharged lemonade factory in the sky!

Now, here comes the Superhero of Customer Management, Salesforce!

Salesforce is like your trusty lemonade-stand assistant who takes care of everything from managing your customers to helping you serve the perfect cup of lemonade.

You might be wondering how does that even happen?

Let me tell you how!

With Salesforce, you can capture important customer details, like their names, preferences, and feedback, and store them securely in the cloud.

It's like having a digital notebook that remembers everything about your customers, so you can make them feel special every time they visit.

But Salesforce doesn't stop there! It also helps you with marketing your lemonade.

Marketing?!

Yes, you read it right!

It can create eye-catching signs and flyers, send out personalized offers to your loyal customers, and even track the effectiveness of your marketing campaigns.

It's like having a Marketing Guru by your side, making sure your lemonade stand gets noticed by everyone in town!

As of now, Salesforce has handled all your “marketing” stuff but what about Customer Service?
If you don’t serve your customers well then, all your hard work will go in vain, and we don’t want that!

Do not worry. Salesforce has got your back!

It allows you to track and respond to customer inquiries, resolve issues, and provide top-notch service.

It's like having a superhero cape that makes you a customer service champion, leaving your customers happy and coming back for more!

Let us now summarize all these points and refer to the key functionalities of Salesforce.

Customer Relationship Management (CRM)

Salesforce keeps a magical book where it writes down all the names and preferences of your customers. It remembers their favorite flavors and any special requests they have. So, when they come back, you can greet them like old friends and offer their favorite lemonade right away!

Sales and Order Management

When a customer wants to buy lemonade, Salesforce creates an order slip with all the details. It keeps track of how much lemonade is sold, the flavors chosen, and any extra add-ons. This way, you never mix up orders and can always deliver the perfect cup of lemonade!

Marketing and Communication

Salesforce has a magical messaging system. It helps you send personalized messages and special offers to your customers. With a blink of an eye, you can send emails that make your customers smile and want to come back for more delicious lemonade.

Analytics and Reporting

Salesforce reveals insights about your lemonade stand. It shows you which flavors are the most popular, when the busiest times are, and how much lemonade you're selling. With these magical insights, you can make smart decisions and create even tastier lemonade offerings.

Integration and Customization

Salesforce has the power to connect with other tools as well. It can link your lemonade stand's website to capture customer inquiries in an instant. It can even work with payment gateways to make sure every transaction is smooth and seamless.

So now you got the highlights of Salesforce's different capabilities and how they can be applied to manage and enhance your lemonade stand business!

All thanks to the magical cloud and our All-in-One tool Salesforce, your lemonade stand becomes a buzzing hotspot, delighting customers and growing your business.

Now you can focus on making the best lemonade in town while the cloud and Salesforce take care of the rest.

Before wrapping it up, let's have a final look at the key points which will empower you to dive into the world of CRM and solve real world problems!

- Simplifies customer and sales management.
- Automate sales and marketing.
- Optimize sales opportunities.
- Engage customers and conquer markets.
- Gain insights for better business decisions.
- Foster teamwork and collaboration.

Cheers to cloud-powered success with Salesforce!

An easy approach to the Servers.

Enakshi Pal — Sat, 26 Jun 2021 08:45:20 +0000

Being a casual user on the internet, I am dead sure about the fact that, we all, at some point, have faced ONE internet issue for sure!

Which issue?

Let me ask you. When was the last time you saw some sentences hovering around your desktop/laptop/mobile screen saying – “Server not Found”, “Service Temporarily Unavailable” or “Too many users? Please try again later” ?

Didn’t remember?

Well, it’s okay. We are not concerned about the last time you saw these but, we will definitely look into the term ‘Server’ and also about the issues.

If you go and google the term ‘Server’ the first definition you will see as “A person or a thing that serves” .

Well yes. The definition in itself is correct. So, to make it sound effortless, let me show you an instance.

We all know that the hospitals serve us 24*7 and there is no particular day that a hospital remains closed, right? Yes! This is exactly how our servers, which we will be talking about, work.

They work 24*7 without getting tired! How cool, isn’t it?

Now, let’s come to the point. The word *“Server”** has different meanings in the IT world.*

Let us start with an example.

Suppose you want to use some photos of a Nightingale bird in your project. So, you open your favorite browser and type there “Images of Nightingale bird”, and the moment you click on “Search” button the browser presents you the images of Nightingale bird you wanted.

You think this process was a cake walk? I’m sure it was, BUT! You are unaware about the BTS (Behind The Scenes).
Do not worry! I would surely put on some light to BTS!

The moment you clicked on the ‘Search’ button, you actually have sent the request to the server to search for your desired image and within few seconds the server responds to your request and SERVES you with the desired output you wanted to see.

So, basically here you got a glimpse of Web Servers and this is how our Servers work!

Now, let me make you read one thing. A server could be a computer or a computer program as well, that processes the response to the requests made by the client side. But this doesn’t signify a normal desktop, rather it points to a very powerful computer which is specifically designed to run the server software.

Now, after reading the above statement, you might be curious about one thing for sure!

What shall we call them? Servers? Computers? What are they? Which is the perfect word?

So, let me clear this huge cloud of questions!

A computer/desktop is a Single User Request-Response System (SURRS).
By this you can think of a document you need, you open it on your computer and view it. This whole thing is done using a single screen. Nobody else is using your computer, right?

Whereas, a server handles Multiple User Request-Response System (MURRS).
Now, by this you can think of using the simple internet connection on your desktop/laptop or mobile phones. Here multiple users are using the same network. Also, you, being one among the multiple users, are using the same shared network without any trouble on your own device.

This is what our Server does. Fascinating, isn’t it?

So, the main reasons behind calling it “Servers” are…

• Both of the devices are almost same but, their style of serving is different, as in, a server can serve multiple users at a time through the same set of networks.
• Computers have inexpensive configuration. Whereas, Servers have expensive configuration.
• Servers are fixed in place whereas, computers/laptop can be shifted.

Too obvious reasons, right?

Okay so, by now you have got a decent idea about Servers, now let us look at their types as well!

Print Servers
File Servers
Database Servers.
Proxy Server
Mail Server
Web Server
Application Server
Real-Time Communication Server
FTP Serve
DNS Server
List Server
Telnet Server
Open-Source Server
Virtual Server
Online Gaming Server
Chat Servers
IRC Servers
Fax Servers
Groupware Servers
News Servers

Woah! Too many types! Confused about the types?

No worries! Let me give you a small clue to make it easy for you to understand. The name of the servers itself, defines the way or the domain they serve. Easy peasy, right?

A matter of fact is, if something works for 24*7 then there might be some issues as well, right?

“Server not Found”, “Service Temporarily Unavailable” or “Too many users? Please try again later” ?

The moment we see these terms hovering around our screen we feel like the world has stopped! A few seconds of downtime would cost a loss of productivity, opportunity and what not to this world!

These issues are quite common and they occur due to a myriad of reasons. I would mention some of them here.
• Man-made error
• Natural disaster
• Software failure
• Equipment failure

When we hear the term “Servers” in technology, we tend to think about the big machines all around and that’s quite obvious. BUT! Did you know?

A matter of fact: You can set up your own server at home as well!

Last but not the least, being a tech person, you are/will be building or might have built some projects using any server-side scripting language (as in PHP, ColdFusion or ASP) at some point.
To test that you surely needed a server environment, i.e., a Local Server Environment.

Primarily, a local server is again a computer which serves a client within a Local Area Network (LAN). This means, that nobody else can access your services. It is called “Local” because, it is on your computer and you are in-charge of managing it!

An example would be: XAMPP, WAMP, MAMP etc.

Without stretching this any longer, having a brief idea about servers before working with them, will definitely keep you one step ahead!

Keep learning!

The PIE concept of OOP.

Enakshi Pal — Sat, 19 Jun 2021 09:18:55 +0000

Being a beginner in the technical field, knowing one of the object-oriented programming languages in detail, is a MUST!

Let me add to that. Here we are NOT going to discuss about “Which language to choose, to ace DSA?” or “Shall we go for C++? Java or Python?”

But here we shall discuss about the basics of development, i.e., OOP. More accurately we will address the building blocks of OOP.

Building Blocks of OOP?

Yes! You read it right. In any interview, whenever you claim to know about an Object-Oriented Programming (OOP) language, you are expected to have a clear concept of OOP.

Besides everything, one question that you are most likely to get hit by, is about, “What are the important features of OOP?”

Before you start digging deeper, let me explicitly mention that, here we would take Java as a reference to understand the OOP concept. So, lets dive in!

Let me get you familiar with certain terms before we actually start.

Parent Class: The class whose properties and features are used or inherited by another class is known as Parent Class.

Child Class: The class which extends or use the functionalities or properties of the parent class is known as Child Class.

Have you heard about the term PIE?

No. It’s definitely not the Apple Pie we eat but, this is something related to OOP. Curious, yet again. Aren’t you?

Let me break the ice. The PIE here is referred to the basic building blocks of OOP. Let’s have a look!

P - Polymorphism
I - Inheritance
E - Encapsulation

Now let us break the PIE into bite-size pieces!

In PIE, the ‘P’ stands for Polymorphism.

According to the dictionary, Polymorphism is the condition of occurring in several different forms. If we split the term, we see that Poly means “many” and Morphism means “forms or shapes”. Polymorphism is a concept in OOP by which we can perform a single action in many forms.

The best example to understand Polymorphism would be Human Behavior.

How?!

A person can be happy at this moment and at the next moment he can be sad or angry. Here, a single person is functioning multiple emotions. This is how Polymorphism works! Relatable enough?

Technically, Polymorphism allow us to define one interface with multiple implementations.

Let us look into the types of Polymorphism. It has 2 types.

Compile-time Polymorphism
Run-time Polymorphism

Let’s have a sneak peek!

Compile-time Polymorphism: In Java, this type of polymorphism is achieved by Method Overloading. When there are multiple functions with same name and different parameters then these functions are said to be overloaded.

This is also known as Compile-time Polymorphism because, the decision of which method is to be called is made during compile time by the compiler. This is also known as Static Polymorphism or Early Binding because the compiler resolves the method calls based on the argument list and reference on which we are calling the method.

Below is a code snippet for overloading

Run-time Polymorphism: This is achieved by performing Method-Overriding. When a method in the child class having same method signature and return type as its parent class, provides specific implementation of a method that is already provided by its parent class, then the method is said to be overridden.

This is also known as Dynamic Polymorphism or Late binding because here the overridden method call gets resolved during runtime. It is the type of the object being referred to that determines, which version of the overridden method will be executed.

Below is a code snippet for Overriding.

Let us now look at the ‘I’ of PIE!

The ‘I’ of PIE stands for Inheritance. I assume that you are a person of beauty (inner and/or outer) with brain so, where have you got these qualities from?

Of course, you must have inherited these qualities from your parents! This is exactly how the concept of Inheritance works.
This concept allows the child class to inherit the features of its parent class.

Why do we need Inheritance?

Because…
• It decreases code redundancy.
• It supports the concept of code reusability.

Let me elaborate this with an example.

We use reusable or refillable pens for writing on paper so that once the ink gets over, we do not need to change or buy a whole new pen, we need to buy a new refill instead. Here we are using the same old pen with new refill. Here the old pen is the Parent Class and the new refill is the Child Class with it’s new features.

This is exactly how the concept of Inheritance works. Sounds interesting, doesn't it?

Let me put a question. Are you aware of the term ‘Multiple Inheritance’ ? Yes? No? or None of them, may be.

So, Multiple Inheritance is that concept of OOP where a child class inherits the properties of more than one parent class.

Fact : Multiple Inheritance is not supported by Java because, the compiler becomes ambiguous regarding which parent class method to call.

Below is the code snippet to understand Inheritance.

Last but not the least, let us have the last bite of the PIE, i.e., the last letter ‘E’, which stands for Encapsulation.

Basically, the term encapsulation itself defines the action of enclosing something, as if it is a capsule, i.e., it is the wrapping of data in a single unit.

Encapsulation = Data Hiding + Data Abstraction.

Now, what’s that?

Wait! Let’s split the equation first and then have a sneak peek!

According to the equation, we see that Data Hiding is the process which hides the internal data from you (the user) whereas, Data Abstraction is the process where certain internal implementation of particular set of services are hidden from you (the user) and only the essential information is shared with the user.

Let us look at encapsulation with the help of an example.

When you login to your email account, from the moment you open it till, you put your username and password, a lot of internal processes take place in the backend and you have no control over it. These internal processes are being hidden from you through encapsulation, so that you do not have to worry about the working procedure of that particular application!

Therefore, the main purpose of encapsulation is to make sure that the delicate set of data is hidden from you (the user).

Thus, learning OOP would help you in many ways, such as,

• Faster Development.
• Reuse of Previous work.
• Helps in better mapping to the Problem Domain.
• Also plays an important role in Client/Server Applications.

Now that you know about the essentials of OOP, getting along with the development environment would become easier.

Till then keep exploring and keep learning!

Happy Coding!

Sessions or Cookies?

Enakshi Pal — Fri, 11 Jun 2021 09:24:16 +0000

Are you aware of the term ‘Session’? Let me guess! A session according to you might be, a period devoted to a particular activity, right? You are right! BUT…

Here we are going to discuss about Sessions in Computer Science. So, in Computer Science, the term ‘Session’ can be used in different contexts such as session layer, web sessions, connections etc.
But here we will look into the sessions used in web applications.

Primarily we know that, cookies store the user (our) information in form of texts in our computer. Sessions do the same BUT…

Sessions store the user (our) information temporarily at the web server. Didn’t sound convincing?

Basically, a Web Session is a sequence of adjacent events or actions done by a visitor on a particular website within a given time frame.

We can think of sessions in an easier way, i.e., Sessions can be considered as the time taken by the visitor to browse a particular website. It represents the time interval between the user’s first arrival on the web page and the time when the user closes the site.
Fact: A developer who codes for the website, initializes and sets the time limit of the session for almost around 5 mins or shorter. So, a single session doesn’t last beyond a certain duration.

After all of these, you might be wondering about the Whys, aren’t you?

Why do we need Web Sessions?

Because, sessions store user data in the form of session ID, which is unique for every user. Now, a curiosity might arise about where are these sessions being stored?

Like Cookies, are they also stored in user’s hard-disk (computer)?

No. These sessions are stored in the server-side. But, why Servers?

Because, on the internet, the server doesn’t know you, because the HTTP request sent to the server is stateless, i.e., it does not maintain the state (also the time interval you can say) of the user.

Let us understand this with a small example.

Let’s start from the moment you open your web page and search for an image. The moment you search for it, you sent a HTTP request to the server for the image you searched via the URL which is present at the top of the web page. Along with the http request, you send or tell your session ID to the server – “Hello there, it’s me [Your Name]!”, so that the server recognizes you.

After the server receives both the request and session ID, it checks your session ID and after verifying, the server sends you back the Session ID along with your desired output.

One interesting thing might amaze you now. Curious?

Did you know?

Sessions allow the server to manage session state.

Manage state? What does that even mean?

Since HTTP is a stateless protocol, it does not keep track about the past or future commands. So, sessions here, play an important role for the servers to maintain the session state.

Let us discuss a small instance.

Suppose you suspect that, somebody has logged in as you from another device, you got some notification via your mail and within that time all the other sessions got invalidated, i.e., “log me out everywhere” functionality worked. This happened because, Sessions got your back!

Another instance would be when you want to associate, not only your shopping browser but also the shopping cart with another device, you might log in to the other device, you will find all your account information and shopping cart information intact.

All of these happened because, Sessions got it again!

By now you might be thinking that if cookies could do the desired work, why need sessions?

If both Sessions and Cookies are THIS similar then,
Where is the difference?

Okay so, let’s have a sneak peek into the differences now!

1.Storage: Your website can store the cookies on your computer’s hard disk.
Whereas, Sessions are being stored in the server-side.

2.Time-duration: The cookie maintains your information until it is being deleted by you from your computer.
Whereas, Sessions maintains your information until you are on the particular web page. Once you close it, the session is being destroyed.

3.Disable or Enable: You (the user) can disable or enable (by clicking on ‘Accept Cookies’ on some websites) the cookies whenever you want. This can be done on the browser settings.
Whereas, you (the user) cannot disable or enable sessions whenever you want.

A Fact that might amaze you is…

Sessions are also known as Non-Persistent Cookies. Because they are saved on your browser while the browser is running.

After unfolding all the facts, we can say that both the sessions and cookies give the best of them. Despite of all the easy aspects of Sessions, we have to note that more the sessions save, more memory space it occupies.

Websites with more online users, create a pressure on the server memory and as a result they rely on cookies.

As a whole, we need both sessions and cookies to make our browsing experience smoother.

Have a safe browsing!

Accept Cookies? Or Not?

Enakshi Pal — Fri, 04 Jun 2021 07:40:22 +0000

If you are a regular visitor on the internet, browsing through different websites might have made you come across the term “Cookies”, right? There you are asked to click onto some buttons saying - ‘Accept Cookies’ or ‘Manage Cookies’ or sometimes ‘Ok, Got it!’.

Well, it’s not the Cookies we eat but, it is something without which we will be unable to login to websites.

Feeling skeptical? Let us uncover the facts!

Cookies are small packets of information or texts that a web browser stores on a user’s hard disk (here we say, computer).

In an easier way it can be said that Cookies allow a website to store information on your machine and later retrieve it once you re-visit the website in future, therefore giving you a better experience in browsing.

Hey, wait! But why do we exactly need cookies?

You need cookies because…

•It keeps track of all your activities in a particular website, so that, you can be served in a more personalized way. You can think of cookies as your note-taker, who logs and keeps track of your activities on a particular website. Sounds quite convincing, doesn’t it?

But, Why are cookies important?

The several important jobs of the cookies are:

•To keep you logged in by recognizing your computer whenever you visit the website.
•To track your activities as you navigate the website (don’t worry, not for malicious attacks), to enable other facilities.
•To improve the website’s usability.
•To personalize so that the next time you visit the site.

When you visit a website, you are asked to login. You fill the username and password section and login to that website. Now when you visit the website again, you are not asked for your username and password to login again.

WHY?

Because, the website remembered you through the cookies which stored your username and password in form of ID (as every cookie has its own unique ID) on your machine.

Now you might be curious about…

How do Cookies work?

Let’s understand this with an example.

You visit a shopping website and there you are asked to click on ‘Accept Cookies’ or sometimes may be not. You click on that. Then the cookie starts tracking all of your activities on that website.

Suppose you thought of purchasing a new phone. You were searching for one and you shortlisted few phones, matching your requirements.
Let’s assume that you got caught up with some work and had to close the website in between.

Later, when you start browsing some other website, the website eventually starts showing advertisements related to that item you shortlisted on the shopping website.

Now, don’t you want to know, how did that happen?

The moment you opened the online shopping website, the website stored a cookie on your computer. The cookie kept on tracking all of your activities in that website from the beginning to the end, so that the website can show you similar suggestions or even coupons which might help you get a cashback!

The above example showed one of the many ways, of how a cookie works.

Let us have a break and look at these pictures below.

Fig. 1: Browsing Without Cookies

Fig. 2: Browsing With Cookies

Moving forward, we can see that, Cookies have their types as well!

What? They even have types?

Yes!

It is not mandatory that only after you click on ‘Accept Cookies’, the cookies start working.

No! These virtually invisible cookies are all very different from each other. You might find some other types as well but, as a casual user and also as a beginner, these are some of the common types you might want to explore:

1.Session Cookies
2.Persistent Cookies
3.Third-Party Cookies

Session Cookies: These cookies are the Temporary Ones. They memorize your online activities, as websites don’t really have any memory of their own. This is because of the session cookies, why you do not have to login to the same website after you close it, as your username and password gets stored because of the session cookies.

A good example of session cookies is online shopping website. You add an item to your cart and close the website. When you visit the website again, you see the item still present in your cart. Later when you check out, your cart becomes empty.
Do you wonder, why? Because, the session cookies remembered your activity and worked accordingly.

Persistent Cookies: They are also known as the First-party Cookies. These cookies work by collecting data according to your preferences to improve your (user) experience.
Curious?

Let us understand with a short example.

Suppose you have logged in to Facebook for the first time, you don’t like its default settings. You changed the language settings and theme settings from default to dark theme, as dark theme is the new trend! Then you log out from Facebook. After a while when you login again, you find your changes are saved __as per your preferences and they are not lost. All thanks to Persistent Cookies!

Third Party Cookies: These cookies are placed on a website so that, the website could collect all the user data for the third party.
Haven’t you wondered about the relevant ads you see on any website you visit?

Okay let me break the ice for you.

You search for a product on the shopping website. After a while, when you open another website, you find the relevant products’ suggestions hovering around some corner of the website, don’t you?

Now that you are aware of what Cookies are, there types and also how they work, a question might arise, about SECURITY. As we are always concerned about our security, hence we make sure that our data is in safe hands. BUT! If we are accepting cookies, should we not worry about our security?

Yes, We should!

These cookies basically track our activities to give us a user-friendly experience, __they are not harmful in themselves. They don’t infect computer with viruses or other malware_ but, some malicious actors can hijack those cookies and use it for their own purpose._

Scared? No need to worry!

To avoid this fraud, what should you do?

To steer clear of this situation, it is recommended not to click BLINDLY on "Accept Cookies" and also it is necessary to keep your browser up to date as many cookie scams are designed to happen in outdated browsers.

As a whole, Cookies are a good thing for a more pleasurable browsing experience.

Have a safe browsing!

Let's focus on the URL. HTTP or HTTPS?

Enakshi Pal — Fri, 28 May 2021 09:27:48 +0000

Wait! What are these? Are they even different?

Most of us being casual users around the internet, are just concerned about googling our stuff, and get over with our work. We are least bothered about the URL we see at the top of any web page we open, aren’t we?

So, let’s break the ice and get started with the facts!

There is a difference between HTTP and HTTPS.

Surprised? Not surprised at all? None of them?

Let’s have a look then.

HTTP stands for Hyper Text Transfer Protocol.

By any means have you heard about the term, Stateless?

Here it is. HTTP is a stateless protocol where the server does not keep track of any state information. This means, we or the user could send any valid information or command at any time.

The server won’t relate any of its command to its past or future commands. In essence, each command is independent of its past or future commands.

An HTTP server doesn’t remember about whether you have visited the site before or how many times you have visited the site.

Let us consider an instance.

When you open a browser, you type or request something to the browser and instantly you get the desired result within few seconds.

Have you ever wondered about how does this happen so fast or what are the processes behind it?

No, right? We, the users barely care about this. No worries, let’s have a look!

•The browser sends a request (input)_ to the web server.
•The web server receives the request.
•The server then runs an application to process the request.
•After the processing the request, the server returns an HTTP response (output) to the browser.
•Lastly, the browser receives the response and hence we get the results in our browser.

If we (the user) were getting our desired results through HTTP then, Why do we need HTTPS?

Let’s dig in!

HTTPS stands for Hyper Text Transfer Protocol Secure.

The only difference between HTTP and HTTPS is _“encryption”__. _
The purpose of HTTP was going fine until security came into the picture. Today, the world demands security above all.

Why do we need encryption or security?

HTTP is not secured. By that we mean, HTTP transfer data as plain text without any encryption. As a result, anybody who is monitoring the session, can read the request and response created by the user.

How is that even possible?

In case of http, we see that, the user submits his/her username and password, the browser sends it to the server in a plain text format, that can be read by any attacker who is monitoring the session.

Whereas in case of https, we see that, the information requested by the user, is being transferred to the web server in encrypted mode i.e., the attacker can now only see the random string or characters not the plain text.

Do you know?

HTTPS not only secures but, also helps authenticate web servers. You might be curious about the term ‘authentication’ by now.

So, the very basic meaning of authentication is, to verify. Now, verify what?

Authentication means to verify a person or a machine, who they claim to be. Just like we use an ID Card to confirm a person’s identity, similarly we need private keys to confirm the server’s identity.

By now you have got a brief idea, so let us finally draw our attention towards the key points.

•HTTP use Principle of Trust, because security was not the priority back then.
•HTTPS provides authentication and encryption which helps block numerous malicious attacks.

So, now the basic notion about the differences between HTTP and HTTPS is quite understandable.

From the next time, ‘http’ and ‘https’ would not look similar to you anymore, won’t they?