Forem: Anushree Chatterjee

Rise of low-code and no-code tools

Anushree Chatterjee — Tue, 11 Apr 2023 09:41:12 +0000

The rise of low-code and no-code tools in Salesforce development has brought significant benefits to businesses, but it has also addressed real-life problems that companies face in an increasingly competitive market.

For instance, one of the biggest challenges businesses face is the need to deliver solutions quickly and efficiently. With low-code and no-code tools, businesses can develop custom applications faster than ever before. For example, a nonprofit organization was able to develop a Salesforce application to manage its donations in just a few weeks, compared to the six months it would have taken using traditional coding methods.

Another challenge that businesses face is the shortage of skilled developers. According to a 2020 survey by the International Data Corporation, the demand for developers is expected to exceed supply by 30% in 2022. Low-code and no-code tools can help address this shortage by enabling non-technical stakeholders to participate in the development process. This can also help to reduce the risk of human error.

Furthermore, low-code and no-code tools have made it possible for businesses to create custom applications that are tailored to their specific needs. For example, a construction company was able to develop a Salesforce application to manage its inventory and supply chain, which significantly improved its efficiency and reduced costs.

Finally, low-code and no-code tools have made it possible for businesses to scale their solutions quickly and easily. With pre-built components and templates, businesses can quickly add new features to their applications as needed. This is particularly important in industries that are rapidly evolving, such as healthcare and finance.

In conclusion, the rise of low-code and no-code tools in Salesforce development has brought significant benefits to businesses, addressing real-life problems and enabling them to deliver solutions quickly, efficiently, and cost-effectively.

COVID-19 Tracker 2021

Anushree Chatterjee — Tue, 20 Jul 2021 10:18:37 +0000

Corona has made everyone suffer in various aspects, and I do hope it doesn't get any more worst of it. So, I've made an active COVID19 tracker for India 2021.

The basic idea of making this project in the first place was to make it informative enough so that people know that how much of the population has been affected by covid-19 in 2021 too.

Without any further ado let's begin with today's post.

The website is hosted on Netlify but why netlify though? Comment down if you want to know about it, I will definitely add another post for that over here.

COVID TRACKER 2021

This project looks a very simple one yet uses big concepts like how does fetch works in JavaScript this one question is one of the favorites' question for the recruiter to ask to any JavaScript Developer.

First step open your code editor create one index.html file then proceed further with the steps given below:

Step1: Let's begin with the html boiler plate

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <title>Covid Tracker for India</title>
    <link rel="stylesheet" type="text/css" href="styles.css" />
  </head>
      <body>
      </body>
</html>

Step2: Next we need to create div sections for the container.

In the image given below we can clearly see the div tags class names that are used to edit them in the CSS later:

div section board is the child div of the container
then comes the six different blocks which are named as follows:
div section c: this is the div for telling the active cases
div section cr: this is the div for telling the critical cases
div section r: this is the div for telling the recovered cases
div section ca: this is the div for telling the total cases
div section d: this is the div for telling the total death cases
div section t: this is the div for telling the total tests done

The code for this using these divs in your index.html file:

<div class="container">
      <h2>
        COVID -19 Cases in <span id="country"></span>
        <img src="" id="flag"/>
      </h2>
      <div class="board">
        <div class="card a">
          <h5>Active Cases</h5> //h5 tag is used for writing 
         </div>                   text in web page     
        <div class="card ca">
          <h5>Total Cases</h5>
        </div>
        <div class="card cr">
          <h5>Critical Cases</h5>
        </div>
        <div class="card d">
          <h5>Total Deaths</h5>
        </div>
        <div class="card r">
          <h5>Recovered Cases</h5> 
            </div>                   
        <div class="card t">
             <h5>Total Tests Done</h5>
          <span id="tests"></span>
        </div>
      </div>
    </div>

The alignment of these div classes is done in the CSS section which you can get access via my GitHub.

Step 3: Creating and editing the Script File(script.js).
The main concept here is of fetching the data through an India Corona -tracker API.

Syntax of using a fetch funtion in JavaScript is given below:

   fetch('URL')
  .then(response => response.json())
  .then(data => console.log(data));

What does fetch do and how does it works internally with your web browser?

fetch is used for making AJAX(Asynchronous JavaScript XML) calls in JavaScript to store data.
fetch sends an HTTP request to the server and we can get sure whether the request was successful or not via promises
Below image displays how does it actually works diagrammatically:

promise tells you whether the request was successful or not if it was successful then we can see the data on our web-page but if it wasn't then we will know there is some issue with our fetch and we can improvise that.

Below is the promise's working shown diagrammatically:

This is your code for Script.js file

fetch("https://corona.lmao.ninja/v2/countries/India")
    .then((response) => {
      return response.json();
    })
    .then((data) => {
      console.log(data);
      document.getElementById("country").innerHTML = data.country;
      document.getElementById(
        "active"
      ).innerHTML = data.active.toLocaleString();
      document.getElementById("cases").innerHTML = data.cases.toLocaleString();
      document.getElementById(
        "critical"
      ).innerHTML = data.critical.toLocaleString();
      document.getElementById("death").innerHTML = data.deaths.toLocaleString();
      document.getElementById(
        "recovered"
      ).innerHTML = data.recovered.toLocaleString();
      document.getElementById("tests").innerHTML = data.tests.toLocaleString();
      document.getElementById("flag").src = data.countryInfo.flag;
    });

So as we discussed fetch, promise and how will the APIs work this will be the end of the post. Hope you liked it.

For the icons I've used font-awesome which is a great site to use fav-icons from.

Take care and keep coding💜

My First PR in GIT-HUB

Anushree Chatterjee — Tue, 25 May 2021 03:52:20 +0000

As a beginner every coder wonders " How should I start with Open Source? " and not a while ago I started learning about Open Source Fundamentals, guess what in these last few weeks I have more than 10 PRs merged in a JavaScript Project. I know it's not much right now but in my opinion Learning and Exploring are two things that are never going to be enough for a Passionate Coders. Wait till the end and find out how a noob coder made it to the world of contributions

Reading this title you must be wondering what is this post about? So let me tell you I am going to talk about how to use GitHub effectively.

Wait, what is GitHub? Aren't we suppose to cover that part first. So let me break it to you as simple as possible GitHub is like a place where you can help the coding community by contributing your valuable knowledge about specific skills. Technically speaking GitHub is a code hosting platform for version control and you can also collaborate on other projects by making valuable points about your changes, it lets you and others work together on projects from anywhere.

If you are still looking for a simpler explanation check out my other post on Explaining git to a 10 years old.

If you don't have a GitHub account make one ASAP.

As I said earlier GitHub is a code hosting platform so it needs some line of commands for you to learn and you should know how to use terminal(for linux), git-bash(for windows) to host your code on GitHub. If you need a post on that I can make you guys a cheat sheet for all the git commands that are used way too much along-with some solved errors.

While using GitHub on your level and making it as effective as possible, I honestly came through many hurdles. But I tackled them by figuring them out on my own. Let's talk about when you open any other person's repository(just like there are files and folders in windows, repositories are files and folders for GitHub) what are your thoughts about that repository? If you think that you can make that repository look more better and it will help someone learn something new then you are at the right path.

Firstly you should open up an Issue and tell the maintainer of that repository about the changes you are about to make so that if he finds it good enough you'll become an assignee, once you get that assignee label you can simply follow these steps and make your first PR:

Fork that repository make it your own git-hub's profile repository then save it on your local host using: git clone your_own_link_of_the_repository
Work on that first locally i.e on your local system by creating your own branch for that repository using: git checkout -b branch_name
Make your changes then add them locally using: git add .
Commit to all the changes by using: `git commit -m "relevant message" Here relevant message means:
feat- added a new feature
fix- fixed a bug
test- everything related to testing
refactor- change of code not any bug fixes or adding a new feat
docs- updation in docs
style- related to styling, designing
chore- updating in build tasks, package manager, configurations related.
After doing all these steps push your specific branch remotely i.e push it on your GitHub repository of the project using: git push origin branch_name

After pushing the branch make your first PR by clicking on the button "compare and create pull request". Well this is a tough part but I got you, here is a template you can use to describe the things


### Related Issue
  - Name of the issue for which you created this project

Closes: #[Issue Number]

### Describe the changes you've made
A brief description of all the changes that you made keep it short and brief but interesting.

### Describe if there is any unusual behaviour of your code(Write `NA` if there isn't)
If your projects has some sort of malfunctioning then mention them here. For example if your project as a web page is not responsive then describe that here.

### Checklist:

Example how to mark a checkbox:-
[x] My code follows the code style of this project.

- [ ] My code follows the style guidelines of this project.
- [ ] I have performed a self-review of my own code.
- [ ] I have commented my code, particularly in hard-to-understand areas.
- [ ] I have made corresponding changes to the documentation.
- [ ] New and existing unit tests pass locally with my changes.

### Screenshots
Put any screenshot(s) of the project here.

Showing your project's snap will make it more obvious that you performed all this on your own and its your idea to improvise that specific repository

Now the last tip from my side is when it's your first time here you are not recognised basically cause you don't have a network yet and no-one is willing to even see your projects, that's heart breaking but don't worry I'll tell you what participate in competitions like Hacktober fest, GirlScript Summer of Code, Cross Winter of Code. I've done all my contributions because of the help these platforms provided to noob coders like us. I've participated in these competitions and hopefully I did well.

So let's not loose hope and try doing contributions as long as you can then someday you'll fall in love with Open Source Contributions. I would love to read your story someday :)

Keep coding and Stay safe 💜

How to approach Dynamic Programming?

Anushree Chatterjee — Sun, 09 May 2021 14:08:07 +0000

Dynamic Programming(DP) itself sounds so huge that coders try to avoid it as far as possible. But big companies like Nutenix, Flipkart, Amazon love those coders who can code a solution that is both optimised and have a minimum time complexity.

Wondering what this post is about?

The title suits this post well, today we'll talk about how a noob coder can identify a DP problem and then approach towards solving it.

Firstly, let me tell you that DP is all about recursion:

                     DP = Enhanced Recursion

where Enhanced Recursion is basically calling a function itself with a simpler input.

Parent of a DP problem is Recursion. What do I mean by parent here? Every DP problem can be solved using recursion so it really matters for you to learn recursion first. Clear your concepts on Recursion then proceed to DP.

Secondly, identifying the question of DP

Keep these two things in mind while identifying:
a) Choice will be given like in a Knapsack problem which element to include and which one element shouldn’t be included.
b) Optimal Questions like those questions covering topics about Minimal, Maximum, Largest, Maximum Profit.

From recursion, Overlapping Recursion is a DP problem.

Now you must be wondering what is this overlapping recursion? Well it's basically a tree-like structure of a recursion function getting called two or more times and then overlapping each other while getting called up.
If the function is called and the program gets executed without even touching other recursion functions then that is called overlapping problem in recursion.

Let's get to the approach that should be used for solving a DP problem:

If you don't know this approach:
[#Recursive Solution---> Memoization]
then do not I repeat DO NOT use this approach to solve your question that is using a "Top down approach which means forming a matrix initially and then filling up the boxes assuming some conditions"

As a developer in making I would really like to add that without knowing Recursion, proceeding to DP is stupidity. You should have a recursive approach to proceed to a top down solution.

The standard form to solve any DP question is this:

Recursive Solution ---> Memoize ---> Top-Down Approach

The only difference between various DP variations question lies in the recursive code.

BONUS POINT

Different questions that you can try out learning are:
1) 0 1 Knapsack Problem(6)[this 6 means the different questions that includes variation with 0 1 knapsack]:

Subset Sum
Equal Sum Partition
Count of Subset Sum
Minimum Subset sum difference
Target Sum(Leet Code Problem)
Count number Of Subset with a given difference

2) Unbounded knapsack(5)
3) Fibonaaci(7)
4) LCS(Longest Common Sub-sequence)(15)
5) LIS(Longest Increasing Sub-sequence)(10)
6) Kadane's Algorithm(6)
7) Matrix Chain Multiplication(7)
8) DP on Grids(4)
9) DP on trees(14)
10) Others(5)

Ending this post while reminding you all to take care of yourselves and keep coding 💜

5 Reasons to use Node-js along with React-js

Anushree Chatterjee — Mon, 03 May 2021 17:21:21 +0000

Always been wondering how and why do we use node js along with react js? Well same here but I can list down the very needed five reasons every web developer thinks about before starting their work on building a website.

P.S: Trying not to make this post boring because React can never be boring that too plus node it is just going to be dope 🔥. So what are we waiting for? Let's get right into it.

1) Helps in maintaining high server load

Yeah you heard it right, having node with your react project makes it super easy for the server to maintain server requests as node can handle multiple server requests, on top of that it helps in maintaining the server load balance.

2) Helps in maintaining dynamic website

Dynamic websites are those websites that have to maintain a real-time database, and to manage those kinds of websites "react+node" helps a lot, in short your problem for the front-end plus back-end can be resolved using these two combos for sure.

3) Helps in creating single page applications easily

Single page applications like Gmail, Facebook can be easily made using node and react. Here react provides a very interactive UI/UX whereas the node provides a very simple back-end model.

4) Helps in building JSON for your APIs

JSON files stands for JavaScript object notation, it helps in transmitting data between website and a server. APIs are used in programming an application, as a developer you have to talk to the users for certain inputs and also with the program application to give specific output for that input. Now node helps in creating reusable code and this code gets shareable using react.

5) Helps while creating MERN stack applications

The web applications that use mongoDB, express.js, react.js and node.js. Using this we can create applications like e-commerce websites, banking websites and many more. React plus node will help us in building such applications with ease.

Ending this post with a reminder to take care of yourselves and keep coding ❤️

Explaining Git to a 10 years old!

Anushree Chatterjee — Sun, 11 Apr 2021 05:09:20 +0000

Imagine having an awesome collection of Pokemon stickers you ask your friends to exchange some of them with yours. Everything is cool until the very next moment when you find out that your favourite sticker is lost or is dumped somewhere...you are sad now just because of those stickers but then your friends offer you the same sticker with the same Pokemon on it cause they were having the copies of those stickers now you are happy so you go back to your house and keep the sticker somewhere safe so that it never gets lost again.

For Developers:

Here "having an awesome collection of Pokemon stickers" indicates your repositories in GitHub.

When you lost track of what is the status of your repository is indicated by "sticker getting lost or dumped".

But then you have already created branches of your main branch so there you can revert your actions and make the necessary changes in your repository without hampering your main branch