DEV Community: Ritvik Shukla

Companies looking for people to hire!

Ritvik Shukla — Thu, 18 Nov 2021 11:36:30 +0000

Hey folks 👋

We launched a new global open source community called Web3 Community in September. And now Web3 Community is a group of 250+ open source and blockchain enthusiasts, learning and growing together.

Some companies are looking for people to hire in our community. You can also grab these opportunities. Join us on our Discord server. There will be many more such opportunities in the future.

Web3 Community focuses on Web3, Blockchain, and somewhat related to decentralized applications (Dapp).

We have gathered content about Blockchain Developer paths and shared it with our repository to get you started.

Join our growing community and contribute to our open source projects

Web 3 Community - Hacktoberfest 2021

Ritvik Shukla — Fri, 01 Oct 2021 04:46:29 +0000

Hacktoberfest starts today. This year Web3Community is excited to take part in the fest for the first time.

An excellent opportunity for everyone to learn more about the open-source environment, meet active contributors and win a t-shirt or have a tree planted in your name!

What is Hacktober?

Hacktoberfest is a month-long celebration of open source software run by DigitalOcean. Hacktoberfest is open to everyone in our global community!. You can sign up anytime between October 1 and October 31.

Making four or more contributions between October 1-31 will allow you to get a memorable t-shirt as a token of appreciation, or you can choose to have a tree planted in your name and help make Hacktoberfest 2021 more carbon neutral.

You can follow this guide for rules.

Why contribute to Web3Community?

Web3Community is an Open Source Community that focuses on decentralized applications, web 3, and blockchain technologies ✨

Here you will get to interact with some awesome folks. 🤓
No one is expert, we all are learning, you can join us and Learn blockchain tech together, develop some great Open Source Projects.

Every single contribution matters.

How can I contribute?

Create an issue first before creating a Pull request.
Fork the Repository and create a Branch for any Issue that you are working upon.
Create a Pull Request which will be promptly reviewed and suggestions would be added to improve it.
Add Screenshots to help us know what changes you have done.
Once you receive the approval from the team, the contribution is ready to be merged and taken into account for the overall Hacktoberfest activity.

For help you can join our Discord

Happy hacking!

MLH INIT 2022

Ritvik Shukla — Sat, 26 Jun 2021 12:59:15 +0000

MLH is organizing INIT 2022, where you will get an opportunity to learn and network with like minded people!

What is INIT?

INIT is a celebration for the start of the 2022 Hackathon Season! This is the first time MLH is running INIT, the format will feel familiar to those who have participated in Local Hack Day. You can expect to complete challenges, hear about BIG community announcements, chat at hacker hangouts, enjoy fun live sessions,network with people, make new memories (and memes) and of course our favorite SWAGS!!

So If you are Interested, then Register here:

Registration

Register for the whole week - https://hackp.ac/init
Complete the swag form - https://hackp.ac/INITswag
Update your address - https://hackp.ac/address
Join Discord and a Guild - https://discord.mlh.io/

And Eddiehub would be participating in INIT this season. Join Eddiehub guild!! You will get to learn and network with some awesome folks out there so do not miss this one!!

Join our guild- https://discord.mlh.io/ (Select EddieHub as your guild)

Join our community on discord also- https://discord.gg/jgfaD56B

How to write a README file for your Github Profile?

Ritvik Shukla — Sun, 20 Jun 2021 04:46:06 +0000

https://tech4e.medium.com/how-to-write-a-readme-file-for-your-github-profile-d386069b8d48

Resources YOU can follow-

1. https://www.markdownguide.org/basic-syntax/#code

2. https://github.com/eddiejaoude/eddiejaoude

3. https://github.com/praveenscience/praveenscience 

4. https://rahuldkjain.github.io/gh-profile-readme-generator/

5. https://www.makeareadme.com/

Version Control System For Beginners- Part III

Ritvik Shukla — Sun, 20 Jun 2021 04:32:43 +0000

Work with GitHub like a pro

In the previous blog we have learned about the git in detail and we have learned about the version control system in detail. In this blog we will learn about GitHub. Suppose you and your team have worked on some software for over a year and all the files are in your pc and suddenly one day water get spilled on your pc and your data your code all gone! Then? What will you do? Will you write the code from the beginning?

Scary, right? To solve this problem we have GitHub! GitHub is a provider of Internet hosting for software development and version control using Git. It offers the distributed version control and source code management(SCM) functionality of Git, plus its own features. It provides access control and several collaboration features such as bug tracking,feature requests, task management,continuous integration.

Creating a GitHub repo:

Repositories contain a collection of files of various different versions of a Project. These files are imported from the repository into the local server of the user for further updations and modifications in the content of the file.

Suppose GitHub is a virtual computer and you want to make a folder where your project data can be saved along with the data of the different versions of your project, so that folder will be called a repository.This folder can be cloned to your local pc (we will learn how later in this article) for further updations and changes.

How to push the changes to your repo?

First make the folder on your local system in which you want to save all the files of your project. Now initialize the repository using the git init command. Now check the status of the repository using the git status command to check what are the files which are yet to be staged. Now use the git add . command to add the files to the staging area which are ready for the commit. Now git commit -m 'your message', adds the change to the local repository,which can later be pushed to the GitHub repo. We have discussed all these things in detail in my previous blog post.

If you want to see what changes you have made in each commit you can use git log -p command.

Like this you will see all the commits and the changes you have done in each commit. And I have told you earlier that using git log command you can see all the commits that are done and also who have committed that change but not what is changed for that you have to use git log -p .

Now you have to generate and add the SSH key to your GitHub account. Simply adding SSH key means you are confirming GitHub that yes it is your pc and you will push code from there.

To generate SSH key follow this .

After adding the SSH key to your GitHub account you can use the git push -u origin master to push the changes you have done.

How to pull the changes that have been done on GitHub by other contributors?

We can pull the changes that have been done by the other contributors on GitHub on our local pc by the git pull command.

git pull origin master is the command which you should run in Git Bash to pull the changes.

How to clone any repository on your local system?

$ git clone https://github.com/your-username/your-repository

This command will clone the repository to your local pc where you can do what ever changes you want to do in the project repository.

Now we will learn how to merge the two branches or more in the repository.

How you will merge more than one branch of the repository to the main branch?

Branch of a repository-

Suppose in your school/college your teacher dictate notes very fast and you were not able to write it properly so you take out two pages from your classroom copy in which you will write the notes and then after the class you will ask from your friends if anything is wrong in that notes, and if there is not anything wrong then you will paste those pages in your copy.

So here your copy is main branch of your repo and those 2 pages are the branch of your repository and your friends are the maintainers of the repo who will tell you about any mistakes. And then the pasting of those pages is just like merging the branch to the main branch after testing(finding errors and correcting it).

You can see all the branches using the $ git branch command.

To delete a branch after you have merged it to the main branch and the new branch is of no use you can use the command

$ git branch -d branch-name

but this command will not delete the branch from your GitHub account, so for that you can use the following command

$ git push --delete branch-name

To make a new branch and switch to that branch from master we can use the following command

$ git checkout -b branch-name

To delete your git repo you can use the following command, this will note remove your data but you have to start again from git init:

$ rm -rf .git

To switch the branch you can use the following command:

$ git checkout branch-name

To merge the desired branch to the main branch you can:

Switch to the master branch
Run $ git merge branch-name command

Your branch will be merged to the master branch.

To see all the branches, their last commit, and their last commit message you can run

$ git branch -v

To see which branch has been merged you can run

$ git branch --merged

To see which branch has not been merged you can run

$ git branch --no-merged

If you want to delete any branch which has not yet been merged but you want to delete it you can run

$ git branch -D branch-name

So these are all the important commands which everyone should know, you can learn more commands if you want to but i will not suggest to mug up all the commands you should know the use of each commands after that you should pick any one language and start learning it.

I am ending this article with Dennis Ritchie quote:

Sources you can follow :

We will meet in MY next blog post.

Till then,

Keep Learning! Keep Hustling!!

Happy Coding!

Version Control System For Beginners-Part II

Ritvik Shukla — Sun, 20 Jun 2021 04:06:27 +0000

What is Git?

Git is a type of distributed version control system used for managing and tracking the changes done to the code. Git was created by Linus Torvalds in 2005 for development of the Linux Kernel. Git is a free and open source software.

Real life projects generally have multiple developers working in parallel. So a version control system like Git is needed to ensure there are no code conflicts between the developers.

Software requirements changes with time. So Git allows the developers to revert and go back to the older version of the code.

If you are the open-source enthusiast or you want to work in some big tech companies in the future you will need git somewhere definitely so lets understand How to install git on your pc!

If you are using Windows Operating System Follow these steps:-

Click to download git for windows (https://git-scm.com/downloads)

When you will click on the git installer that you have downloaded from the above link blindly click next in every step and get git installed on your pc.

For Linux Based Systems:-

Open the terminal using the shortcut Ctrl+Alt+T

Copy and paste these commands in the command window which you opened:-

$ sudo apt install git
$ sudo apt update
$ sudo apt upgrade

Copy and Paste these commands one by one in the terminal. You may be prompted to enter your password.

How to Create a git repository (In Windows) ?

You have to create the repository if the original code is in your pc. Create a folder in which you want to save the original code files. Right click inside the folder and click on Git Bash here. Git command terminal will open and you are good to go.

How to Create a git repository (In Linux)?

Open the terminal using the shortcut Ctrl+Alt+T

To make a new folder or directory on your pc:-

1.Type mkdir DIRECTORY NAME and then press Enter

Type ls to list all the directories present on your pc
Type cd Directory name to go to the wanted directory

These commands will create a new directory on your pc. After that you can initialize a new git repository in that directory.

To check whether git is successfully installed on your pc or not, use the command given below:-

$ git --version

If git was successfully installed on your computer then the output that you will get will be:

git version "Version of git installed" example- git version 1.9.1

If you get the output like this, then git is installed successfully on your pc.

Now when we have installed git on our pc we will learn How to configure your Git username and email using the following commands. These details will be associated with any commits that you create.

To configure your Git username for every repository on your computer:-

$ git config --global user.name "Tech4everybody"Replace our name with your own inside the inverted commas!

To Confirm that you have set the Git username correctly(If you have configured username for every repository):

$ git config --global user.name

To configure your Git username for a single repository:-

$ git config user.name "Tech4everybody"Replace our name with your own inside the inverted commas!

To Confirm that you have set the Git username correctly(If you have configured username for a single repository):

$ git config user.name

To configure your Git email for every repository on your computer:-

$ git config --global user.email "Tech4everybody@t4e.tech"Replace this email with your own email!

To confirm that you have entered the right email id (If you have configured email for every repository):-

$ git config --global user.email

To configure your Git email for a single repository:-

$ git config user.email "Tech4everybody@t4e.tech"Replace this email with your own email!

To confirm that you have entered the right email id(If you have configured email for a single repository):-

$ git config user.email

Before learning the initialization of the git repository let’s understand

What is a git repository?

A Git repository is a virtual storage of your project. It allows you to save versions of your code, which you can access when needed.

How to initialize a new Git repository?

To create a new repository, you’ll use the git init command. git init is a one-time command you use during the initial setup of a new repository. Executing this command will create a new .git subdirectory in your current working directory. It can be used to convert an existing, unversioned project to a Git repository or initialize a new git repository. Usually this will be the first git command that you will use.

How to add files to any git repository?

The git add command adds the untracked files to the staging area. However, git add doesn't really affect the repository in any significant way—changes are not actually recorded until you run git commit.

To add one file to staging(Index) area:

$ git add Filename

To add more than one file to staging(Index) area:

$ git add .

Git status command is used to show modified files of the working directory, staged for your next commit.

$ git status

How to save your changes to the local repository?

The git commit command makes sure that the changes are saved to the local repository. The command “git commit –m ” allows you to describe everyone and help them understand what has happened.

Commits all the changed files with “Commit Message”

$ git commit -m "Commit message"

You can use — amend flag with the git commit command to commit again for changing the latest commit. Running this will overwrite not only your recent commit message but, also, the hash of the commit. It won’t change the date and time of the commit.

It will also allow you to add other changes that you forget to make using the git add command.

$ git add "Changed file name"

$ git commit --amend -m "message"

You can see in the above image that the commit date and time is same for both the initial and the amended commit.

To get a record of the commits in a git repository:-

The git log command shows a list of all the commits made to a repository. You can see the hash of each git commit, the message associated with each commit, and more metadata. This command is useful for displaying the history of a repository.

$ git log

How to unstage any file from the staging area?

$ git reset filename

To know about the changes which are not staged you can use git diff command:-

$ git diff

Here the lines in red are those which I removed and the lines in green are those which I added.

To know about the changes which are staged but not committed you can use the command given below:-

$ git diff --staged

So in this blog, we have learned the most important and most used git commands. In the next blog, we will learn more about Github, and how to clone a repository, how to create a branch, and how to merge them, and many more things.

After my third blog on Version Control Systems you will be ready to contribute to the open source community.

Ending this article with Steve Jobs Quote

If you found this article useful, follow me for more!

Happy Coding!

Version Control System For Beginners- Part I

Ritvik Shukla — Sun, 20 Jun 2021 03:36:58 +0000

Suppose you are working on any project with the team of 100 software developers and suddenly one day your pc stop working and all your data get deleted by mistake and all the data of the project was in your pc. Then?? What will you do?? Isn't it a big problem?

And also it will be very difficult for everyone to contribute to the project remotely if the data of the project will be divided! So VCS and Github are there to solve our these problems! we have our saviour with us Git & Github!

What is Git?

Git is a version control system! Now let's understand version control system and it's type in detail first.

Version control systems are used in managing and in keeping track of the changes done to the source code over time. As you know in making of the software collaboration of more than one developer is there, so it is important to track the changes done to the source code.

Using a version control system if a mistake is made by anyone in the source code you can return to the previous version easily. You can take the example of Open-Source Projects where more than one developers from different parts of the world contribute to a single project, and each one of them contributes to the project in some specific kind either by finding a bug in the code or by adding some new feature or by updating the README section.

The version control system assigns a unique hash code for every modification done to the source code. It is useful in reverting to the previous version of the code.

If you do not use any kind of version control system you will run into problems like not knowing what changes you have done to code and when you have done it. If you have done any mistake in the code, the code will not work properly and you will not be able to revert to the previous version which was working as you were not tracking it. Using the version control system you can also check which lines of code are added and which are deleted. This can help you identify the problem in the code more easily.

The version control system mentions the date and time also, on which the modification was done. It also mentions the name and email id of the contributor contributing to the project.

Suppose you are working with a team of other five developers on the same project and you want to add some new feature to it but you are not confident that it will work properly or not, you are afraid that if it doesn’t work properly then the development process will stop. Here the version control system helps , Version control system gives us the comfort to create a separate branch for every contributor who wants to add something new or wants to make changes in the code and when they work properly, they are merged in the main code.

What are the different types of VCS?

There are three types of the Version control system:

Local Version Control System
Centralized Version Control System
Distributed Version Control System

Local Version Control System:

In simple language, the Local Version Control System is the system in which you track all the files and store them on your computer.

You are feeling bored! Right? I can understand!!

Let’s take an example to understand in a better way:-

Let’s suppose you have written 100 lines of code and you saved it with the name “Folder 1” and then after someday you thought of adding or changing something in it but you don’t want to disturb the version 1 directory so you created a new directory “Folder 2” and copied all the code of version 1 in it and started working on it, but after the modification, you saw that the code is not working properly, so you revert to version 1 directory. This is how you can keep track of the files using the Local Version Control System.

Interesting! Right?

This approach is very common and simple but it is also incredibly error-prone. It is easy to forget which directory are you in and in which directory you have to make the change so there is a high chance of error.

Centralized Version Control System-

As you know that to make a software, collaboration is very much necessary and for collaboration there should be a communication between the contributors contributing to the project. Using the centralized version control system everyone contributing to the project knows to some extent what changes others have done.

In the Centralized Version Control System, there is only one repository on the server containing all the versions of the code. Everyone who wants to make any change in the main code on the server, they have to commit the changes they want to reflect in the central repository. To view the changes done to the repository, other users have to update it from the server.

Suppose four developers are working together on the same project. Developer “A ” wants to make changes in the project, so first, he made those changes in his working copy on his local system, and after he is confident about the working, he has to commit those changes to reflect them in the central repository. Now to see those changes in their working copy other contributors contributing to the project have to update it from the central server.

So what is the problem in using CVCS for version control? Do you Know?

No? Okay! No problem, we will learn together :)

The major drawback of this type of version control system is that all the versions of the code are on the server so if it goes down during the period of development, collaboration will stop.

If the hard disk of the central database becomes corrupted and you have not kept any backup of the code files anywhere, You lose everything and you will have to start from the beginning.

This does not seem to be a very big problem to you. Right?

But when you’ll work in some big tech giants where code is in millions of lines.

Then?

Yes!!! You’re Right!! Then It will be a big problem!!

Distributed Version Control System:

Distributed version control systems contain multiple repositories. Each user has their working copy where they can make the changes without disturbing the main code. Every clone has a full backup of data. Using Distributed Version Control you can work jointly on the same project with the different group of people. When you will commit, it will reflect those changes in your local repository and you have to push the changes to make them visible in the central repository, and to see other’s changes you have to pull it from the central repository.

Git is a type of Distributed Version Control System which is mostly used nowadays. Git is widely used in the open-source sector. Using Git, it becomes easy for anyone from anywhere to contribute and it becomes easy to manage the code.

So, let’s summarize what we have learnt till now:

Using a version control system it becomes easy for anyone from anywhere to contribute to the project.

Using a version control system one can make changes in the same repository at the same time without affecting the development process.

Using a version control system it becomes easy to revert to the previous version if you have made a mistake.

Using a version control system it becomes easy to identify the mistake in the code.

Using a version control system you can know what changes have been made to the code, who have made them and when it was made.

So, we have completed the basics of version control systems in this blog.

In my next blog post we will learn about Git in detail!

Excited! Right? I’m also excited…

So, for now I’m ending this blog post.

If you want to connect with me follow me , we will meet again in my next blog post :)

Till then,

Happy Coding!