DEV Community: Jayesh Tembhekar ⚡

Git commit message 💬

Jayesh Tembhekar ⚡ — Tue, 03 Nov 2020 15:48:54 +0000

Hello, there 👋🏼 I hope you are doing well.

As a developer, I know you are well aware of the Git version control system.

Just wanted to know:

How do you write your ▶

git commit -m "commit message"

Do you follow any special rule or something?
Let's discuss in the comment section below 😄

Your favorite free hosting site? 🌐

Jayesh Tembhekar ⚡ — Sat, 24 Oct 2020 13:43:06 +0000

I have used Netlify and Vercel.
What are you using? 🙂

Comment below ⬇

Has anyone worked in React and Angular both?

Jayesh Tembhekar ⚡ — Sat, 10 Oct 2020 11:43:42 +0000

Two most popular front-end frameworks/library:

React
Angular

Which is your favorite one?
I would like to know 👩‍💻👨‍💻

Annnd., completed ! 🤩

Jayesh Tembhekar ⚡ — Mon, 05 Oct 2020 15:00:30 +0000

Hello, Opensourcer 👋

How is your Hacktoberfest 2020 going?
I have completed my entries for this year.
Really looking forward to getting approved ✅

Do share your entries in the comments.
You can organize your PRs here

You can check mine ▶ TechLead-21

Also, I have completed my 10,000 posts views on DEV.to 🤸‍♂️✌

Do you have issues? 😁

Jayesh Tembhekar ⚡ — Wed, 30 Sep 2020 13:56:59 +0000

All ready for Hacktoberfest 2020. 💥🎊

Hey, drop your projects for beginners so they can contribute to it with ease and have a great first ever Hacktoberfest 2020.

My first Hacktoberfest 😬

Jayesh Tembhekar ⚡ — Sun, 20 Sep 2020 16:28:32 +0000

Hacktoberfest 2020 is just around the corner and to be honest, I am a bit nervous.

What are the plannings have you done for this year?
Which advice for the first time Open Source newbie?

We would like to know from DEVcommunity here 😄

comment your advice that will help me and newbies out here.

Ui/Ux Design Vs. Web Development

Jayesh Tembhekar ⚡ — Tue, 14 Jul 2020 11:43:39 +0000

If you have these qualities, you may be a future...

Ui/Ux Designer 🎨

You're interested in how to improve things for others.
You're open to different ways of looking at the world.
You see improvements to be made everywhere - at school, at home, at work, at the gym, etc.

Web Developer 👨‍💻

You enjoy problem-solving.
You like to find solutions AND implement them.
You look at error messages as a good thing.
You think logically.

Add these tech skills...

1. Ui/Ux Designer

Youtube channels to learn from...

2. Web Developer

Front-End languages like Html, CSS, and JavaScript.
Back-End languages like Node.js or Python
Database technologies like SQL or MongoDB
Fluency with APIs, GIT, basic algorithms + data structures

Youtube channels to learn from...

And you could get jobs like...

Ui/Ux Designer

Product Designer.

UX Researcher.

UX Consultant.

UX Designer.

Web Development

FrontEnd/BackEnd Developer.

Fullstack Developer.

QA Engineer.

Database Administrator.

You can find me here...

🔹 Twitter - @jayeshintech
◼ LinkedIn - @jayeshintech
🔸 Instagram - @jayesh.2112

Six Sigma Belts 🥋

Jayesh Tembhekar ⚡ — Sun, 12 Jul 2020 17:27:27 +0000

A Six Sigma project uses “Belts” to help define the roles of people on the team.

Six Sigma White Belt

A Six Sigma “White Belt” is an entry-level certification for those individuals who need to have a basic understanding of what Six Sigma is.
These individuals are not involved in a Six Sigma project but may work in a company or department going through a Six Sigma process improvement.

Six Sigma Yellow Belt

A Six Sigma “Yellow Belt” is typically a subject-matter expert (SME) in a particular subject or area of the business being reviewed. These members are generally not involved with the Six Sigma project directly. Instead, they may provide information and assistance to Green Belts (as subject matter experts) so that they can better understand a particular segment of the business.

Six Sigma Green Belt

A Six Sigma “Green Belt” is an employee who takes on a Six Sigma implementation project along with his or her other job responsibilities, operating under the guidance of Black Belts.
A Green Belt works to understand which business processes are not performing as needed, identify root causes of problems, analyze and improve contributing factors, and sustain gains in those improvements.

Six Sigma Black Belt

A Six Sigma “Black Belt” has knowledge of Six Sigma philosophies and principles and leads a team during a Six Sigma project. They must have both leadership and project management skills to be successful.

Six Sigma Master Black Belt / Champion

A Six Sigma “Master Black Belt” is in charge of training Black Belts and Green Belts in Six Sigma processes. They are also a go-to reference for ideas and theories during a project. Master Black Belts typically have years of experience as a Black belt, before taking on the Master Black Belt role.
A Six Sigma Champion is a senior executive within the organization whose role is sponsoring specific projects. They have the authority within the organization to allocate resources for the project.

Six Sigma Belts 🥋 Levels

When to use Six Sigma

Jayesh Tembhekar ⚡ — Fri, 10 Jul 2020 10:41:28 +0000

Some organizations make use of various project improvement methods. As a Six Sigma expert, you might have to champion your own method on occasion. Here are some reasons to choose Six Sigma over other methods described in this part.

1. When facing the unknown

Six Sigma is designed so you can begin a project even when you don’t know the cause of the problem. In some cases, teams aren’t even sure what the exact problem is – they only know some metric is not performing as desired. For example, an organization might experience a drop in profits that doesn’t correct itself in several consecutive quarters. Six Sigma methods can begin to seek the causes of the problem, prioritize them, and work toward solutions.

2. When problems are widespread and not defined

Even when a problem is understood, if it is wide in scope and not well defined, improvement projects that are not tightly managed can escalate in scope to a point that they become unmanageable. In this situation, teams attempt to solve increasingly bigger issues. As a result, no problem is ever completely solved. Six Sigma includes controls for avoiding such scope creep so teams can make incremental improvements that steadily improve a process over time. We’ll talk about scope creep more in later chapters.

3. When solving complex problems

If processes are complex and feature many variables, it is difficult to determine how to approach a solution, much less define, and measure success. Knowledge of statistical analysis and process control lets teams approach problems that involve enormous amounts of data and many variables. Through analysis and a graphical representation, complex ideas can be distilled to specific hypotheses, premises, and conclusions.

4. When costs are closely tied to processes

Because Six Sigma’s statistical process control component lets teams make more accurate assumptions than almost any other method, it is very appropriate for situations that are closely tied to revenue or cost. When a single tiny change can result in millions of dollars in gains or losses, teams must validate assumptions with an extremely small margin of error. Guesswork, basic research, and even years of experience cannot do that as accurately as properly implemented Six Sigma methods.

Six Sigma History and Application

Jayesh Tembhekar ⚡ — Thu, 09 Jul 2020 09:09:37 +0000

Six Sigma History and Application

While the roots of Six Sigma are commonly attributed to companies such as Toyota and Motorola, the methodology is actually grounded in concepts that date as far back as the 19th century. Before delving into the history of Six Sigma, it’s important to understand the difference between traditional quality programs, such as Total Quality Management, and continuous process improvement methods, such as Six Sigma.

The Development of Statistical Process Control

Six Sigma applies statistics to define, measure, analyze, verify, and control processes. In fact, Six Sigma teams usually use methodologies known as DMAIC or DMADV to accomplish improvements and develop controls for processes.

DMAIC stands for Define, Measure, Analyze, Improve, and Control.

These are the five phases of a Six Sigma project to improve a process that already exists. When developing a new process, teams use DMADV, which stands for Define, Measure, Analyze, Design, and Verify.

The Normal curve is just one of several possible probability distribution models. It is perhaps the most widely used model, and the other models developed from the normal curve. Probability distribution models are discussed in later chapters on statistics.

W. Edwards Deming was working for the U.S. Department of Agriculture. A physicist and mathematician.

One of Deming’s ideas is called the PDCA cycle, or plan-do-check-act cycle. The idea is that improvement comes when you recognize there is a need for change and make a plan to create improvement. Next,
you do something by testing your ideas. Using the results of the test, you check or verify that your improvements are working. Then you act, bringing

your improvements to a production environment or scaling improvements outside of the test environment. The fact that PDCA is a cycle means it never Act Plan
ends; there are always improvements to be made. This is a core tenet of Six Sigma.

Continuous Process Improvement: Toyota and Lean

What is Jidoka?

Jidoka is a principle that creates control of defects inside a business process. Instead of identifying defects at the end of the production line and attempting to trace errors back to a source, jidoka demands that a process stop as soon as errors are detected so improvements or troubleshooting can happen immediately.

For jidoka to work properly, machines are often equipped to recognize bad outputs from good outputs; the machines are also equipped with a notification of some type to spark human interaction in the process when things go awry.

The principles driving Toyota's system, and later, the foundation of Lean Process Management or Lean Six Sigma, include:

Defining customer values
Identifying the value stream for customer needs and desires
Identifying waste in the process
Creation of a continuous process flow
Continually working to reduce the number of steps and time it takes to reach customer satisfaction

Lean management is highly concerned with removing waste from any process. Waste increases costs and time spent on a process, making it undesirable in any form.

Defining 6σ & its Principles

Jayesh Tembhekar ⚡ — Wed, 08 Jul 2020 10:22:56 +0000

Six Sigma, or 6σ, is both a methodology for process improvement and a statistical concept that seeks to define the variation inherent in any process. The overarching premise of Six Sigma is that variation in a process leads to opportunities for error; opportunities for error then lead to risks for product defects. Product defects—whether in a tangible process or a service—lead to poor customer satisfaction. By working to reduce variation and opportunities for error, the Six Sigma method ultimately reduces process costs and increases customer satisfaction.

Defining 6σ

Six Sigma as a methodology for process improvement involves a vast library of tools and knowledge, which will be covered throughout this book. In this section, we’ll begin to define the statistical concept represented by 6σ.
At the most basic definition,

6σ is a statistical representation for what many experts call a “perfect” process.

Technically, in a Six Sigma process, there are only 3.4 defects per million opportunities. In percentages, that means 99.99966 percent of the products from a Six Sigma process are without defect. At just one sigma level below—5σ, or 99.97 percent accuracy--processes experience 233 errors per million opportunities. In simpler terms, there are going to be many more unsatisfied customers.

Calculating Sigma Level

Organizations and teams can calculate the sigma level of a product or process using the equation below:

Common Six Sigma Principles

Organizations can impact their sigma level by integrating core principles from the Six Sigma methodology into leadership styles, process management, and improvement endeavors. The principles of Six Sigma, and the tools used to achieve them, are covered in detail in various sections of this book, but some common ideas are introduced below.

1. Customer-Focused Improvement

A primary principle of the methodology is a focus on the customer. The Voice of the Customer (VoC) and ways for establishing what the customer really wants from a product or process. By combining that knowledge with measurements, statistics, and process improvement methods, organizations increase customer satisfaction, ultimately bolstering profits, customer retention, and loyalty.

A detailed understanding of the customer and customer desires not only lets businesses customize product offerings and services, but it also lets organizations:

Offer additional features customers want and are willing to pay for
Prioritize product development to meet current needs
Develop new ideas based on customer feedback
Understand changing trends in the market
Identify areas of concern
Prioritize work on challenges based on how customers perceive various problems or issues
Test solutions and ideas before investing time and money in them

Value Streams:

The value stream is the sequence of all items, events, and people required to produce an end result. For example, the value stream for serving a hotdog with ketchup to someone would include:

A hotdog supplier
A bun supplier
A ketchup supplier
Hotdogs
Buns
Ketchup
A cooking procedure for the hotdog
A pot
Tongs
Someone to do the cooking
A plate
Someone to put the hotdog into the bun
Someone to put the ketchup on the hotdog
Someone to put the completed hotdog onto a plate
Someone to serve the hotdog to another

2. Continuous Process Improvement

Inherent in the Six Sigma method is continuous process improvement. An organization that completely adopts a Six Sigma methodology never stops improving. It identifies and prioritizes areas of opportunity on a continuous basis. Once one area is improved upon, the organization moves on to improving another area. If a process is improved from 4 Sigma to 4.4 Sigma, the organization considers ways to move the sigma level up further. The goal is to move ever closer to the “perfect” level of 99.99966 accuracies for all processes within an organization while maintaining other goals and requirements, such as financial stability, as quickly as possible.

3. Variation

One of the ways to continuously improve a process is to reduce the variation in the process. Every process contains inherent variation: in a call center with 20 employees, variation will exist in each phone call even if the calls are scripted. Inflection, accents, environmental concerns, and caller moods are just some things that lead to variation in this circumstance. By providing employees with a script or suggested comments for common scenarios, the call center reduces variation to some degree.
Consider another example: A pizzeria. The employees are instructed to use certain amounts of ingredients for each size of pizza. A small gets one cup of cheese; a large gets two cups. The pizzeria owner notes a great deal of variation in how much cheese is on each pizza, and he fears it will lead to inconsistent customer experiences. To reduce variation, he provides employees with two measuring cups: a 1-cup container for small pizzas and a 2-cup container for large pizzas.

The variation is reduced, but it is still present. Some employees pour cheese into the cups and some scoop it. Some fill the cups just to the rim; others let the cheese create a mound above the rim. The owner acts to reduce variation again: he trains all employees to fill the cup over the rim and use a flat spatula to scrape excess cheese off. While variation will still exist due to factors such as air pockets or how cheese settles in the cup, it is greatly reduced, and customers experience more consistent pizzas.

4. Removing Waste

Remember the hotdog example for value streams? We asked the question: do four different people act to place the hotdog in the bun, put the ketchup on the hotdog, plate the hotdog, and serve it? If so, does the process take more time because the product has to be transferred between four people? Would it be faster to have one person perform all those actions? If so, then we’ve identified some waste in the process—in this case, waste of conveyance.

Removing waste—items, actions, or people that are unnecessary to the outcome of a process—reduces processing time, opportunities for errors, and overall costs. While waste is a major concern in the Six Sigma methodology, the concept of waste comes from a methodology known as Lean Process Management.

5. Equipping People

Implementing improved processes is a temporary measure unless organizations equip their employees working with processes to monitor and maintain improvements. In most organizations, process improvement includes a two-pronged approach. First, a process improvement team comprised of project management, methodology experts, and subject-matter experts define, plan, and implement an improvement. That team then equips the employees who work directly with the process daily to control and manage the process in its improved state.

6. Controlling the Process

Often, Six Sigma improvements address processes that are out of control. Out of control processes meet specific statistical requirements. The goal of improvement is to bring a process back within a state of statistical control. Then, after improvements are implemented, measurements, statistics, and other Six Sigma tools are used to ensure the process remains in control. Part of any continuous improvement process is ensuring such controls are put in place and that the employees who are hands-on with the process on a regular basis know how to use the controls.

Types of Cloud Services 🌩

Jayesh Tembhekar ⚡ — Thu, 25 Jun 2020 10:38:26 +0000

Hello, Devs 🙋‍♂️

Lets explore the three categories of cloud computing

IaaS versus PaaS versus SaaS

1. Infrastructure as a service (IaaS)

Infrastructure as a Service is the most flexible category of cloud services. It aims to give you the most control over the provided hardware that runs your application (IT infrastructure servers and virtual machines (VMs), storage, and operating systems). Instead of buying hardware, with IaaS, you rent it. It's an instant computing infrastructure, provisioned and managed over the internet.

IaaS is commonly used in the following scenarios :

Migrating workloads :
Typically, IaaS facilities are managed in a similar way as on-premises infrastructure and provide an easy migration path for moving existing applications to the cloud.
Test and development : Teams can quickly set up and dismantle test and development environments, bringing new applications to market faster. IaaS makes scaling development and testing environments, fast and economical.
Storage, backup, and recovery : Organizations avoid the capital outlay and complexity of storage management, which typically requires skilled staff to manage data and meet legal and compliance requirements. IaaS is useful for managing unpredictable demand and steadily growing storage needs. IaaS can also simplify the planning and management of backup and recovery systems.

Some notable examples of IaaS :

2. Platform as a service (PaaS)

PaaS provides an environment for building, testing, and deploying software applications. The goal of PaaS is to help you create an application quickly without managing the underlying infrastructure. For example, when deploying a web application using PaaS, you don't have to install an operating system, web server, or even system updates.

PaaS is a complete development and deployment environment in the cloud, with resources that enable organizations to deliver everything from simple cloud-based apps to sophisticated cloud-enabled enterprise applications. Resources are purchased from a cloud service provider on a pay-as-you-go basis and accessed over a secure Internet connection.

PaaS is commonly used in the following scenarios :

Development framework : PaaS provides a framework that developers can build upon to develop or customize cloud-based applications. Just like Microsoft Excel macro, PaaS lets developers create applications using built-in software components. Cloud features such as scalability, high-availability, and multi-tenant capability are included, reducing the amount of coding that developers must do.
Analytics or business intelligence : Tools provided as a service with PaaS allow organizations to analyze and mine their data. They can find insights and patterns, and predict outcomes to improve business decisions such as forecasting, product design, and investment returns.

Some notable examples of PaaS :

3. Software as a service (SaaS)

SaaS is software that is centrally hosted and managed for the end customer. It is usually based on an architecture where one version of the application is used for all customers, and licensed through a monthly or annual subscription. Office 365, Skype, and Dynamics CRM Online are perfect examples of SaaS software.

Here are a few more advantages of SaaS :

Payment flexibility : SaaS is a subscription, pay-as-you-go model. Customers can manage their budgets better because they can choose the best licensing that adapts to their needs and make payments accordingly. SaaS models also give them the flexibility to terminate the contract at any time, eliminating those recurring costs.
Scalability : Customers can always revisit their licensing model and access more or fewer services depending on their business needs at that time.
Simpler upgrades : With SaaS, IT departments don’t have to worry about painful upgrades. The provider takes care of that for them. Users always have access to the latest version of the service. When the SaaS is delivered from a multi-tenant architecture, the software provider benefits, too, because new updates and upgrades are automatically available to all users in all the companies that subscribe.
Accessibility : Customers can access SaaS anywhere at any time as long as they have an Internet connection and a web browser.
Easy customization : Despite the multi-tenant architecture, most SaaS applications can be easily customized to fit the business needs of each customer. These customizations don’t impact the common infrastructure and are always preserved when an upgrade is performed.

Some notable examples of SaaS :