DEV Community: Arun Krish

Checkout new post!

Arun Krish — Fri, 03 Apr 2026 05:52:37 +0000

Arun Krish

Apr 3

Okay, What is Redis?

#beginners #database #performance #tutorial

Comments 1

2 min read

Okay, What is Redis?

Arun Krish — Fri, 03 Apr 2026 05:51:33 +0000

What is Redis?
Redis (Remote Dictionary Server) is an open-source, in-memory, NoSQL data structure store used primarily as a database, cache, and message broker. It stores data in RAM for extremely fast read/write speeds, commonly for caching, session management, and real-time analytics, handling data as key-value pairs.

In simple words, it will act like a cache memory to store data as key - value pair. I watched a tutorial to understand Redis. He showed something like, if we don't use redis the website take too much time for each fetching. But if we use redis the first fetching only take that much time, second fetch onward the fetching time will be low.

In order to understand that, you need to do this tutorial. The code is given below as github gist. Download or copy the code and dance with me.
Redis Gist Code

You want to open your terminal with current directory and run the two codes given below. One for installing the packages and second one for starting the port.

npm i
npm start

Your port will be open at localhost:5000. You want to go to the url

http://localhost:5000/repos/arunkrish11

(it is actually http://localhost:5000/repos/github_id), so you can see how many repos someone has. You can see something like this,

Now you want to inspect the site and go to the network section. There will be something named finish time. It actually shows how time took to load the site, yeah the fetching time. Now you want to go to the code and remove the first section,

// 1. Check cache
    const cached = await client.get(username);
    if (cached) {
      return res.send(`<h2>${username} has ${cached} repos (cached)</h2>`);
    }

If you refresh the page, then you can see the fetching time is high for each time we refresh.

(First fetching after code removal)

(Second fetching after code removal)

Now we want to paste the code that we removed earlier.If you refresh now, you can see the difference. The first fetching only take that much time, second onward the fetching time is low.

(First fetching after the return of code)

(Second fetching after the return of code)

So that's it. Catch you in another post. Til then take care, bye.

Checkout my profiles.
GitHub
DevTo

Advice needed!

Arun Krish — Tue, 03 Mar 2026 09:43:36 +0000

How can I reach out others or companies for getting an internship or a job? I know most of people in this platform must gone through this stage. Can I get some advice, so I can take a note on it?

Leave your thoughts or experience with internship or job hunting. I would love to read those.

Sync any Linux folder to Google drive using Rclone + systemd.

Arun Krish — Sun, 07 Dec 2025 10:58:11 +0000

Here is the steps to automatically upload your local files in the linux to google drive.

Contents in this blog.

Connect Linux → Google Drive
Auto-upload specific folders
Prevent files from being deleted in Drive
Pause/resume syncing anytime
Run everything safely with minimal data usage

1. Install rclone

sudo apt install rclone
Check version: rclone version

2. Configure Google Drive

Run: rclone config
Choose:

n) New remote
name: gdrive

Remote type > choose: drive

Client ID → press Enter
Client Secret → press Enter

Scope → choose: 1) Full access
Use auto config → choose Yes
Rclone will open your browser → Login → Allow access.
Then: Configure as a Shared Drive? → No
At the end: Keep this remote? → Yes
Verify: rclone lsd gdrive:
You should see your Drive folders.

3. Choose folders to auto-sync

Example folders: /home/arunkrish/workspace
These will upload to: gdrive:workspace

4. Why NOT use sync?

sync mirrors your folder, meaning files deleted locally get deleted from Google Drive.
Not good for backups.
So we use: rclone copy
This only uploads new/changed files — never deletes anything.

5. Create systemd auto-upload services

Workspace service

mkdir -p ~/.config/systemd/user
nano ~/.config/systemd/user/gdrive-workspace.service

Contents:

[Unit]
Description=Upload workspace to Google Drive

[Service]
Type=oneshot
ExecStart=/usr/bin/rclone copy /home/arunkrish/workspace gdrive:workspace --verbose --create-empty-src-dirs

Timer:

nano ~/.config/systemd/user/gdrive-workspace.timer

Contents:

[Unit]
Description=Run workspace uploader every 5 minutes

[Timer]
OnBootSec=2min
OnUnitActiveSec=5min

[Install]
WantedBy=timers.target

Enable:

systemctl --user enable --now gdrive-workspace.timer

6. Confirm all timers

systemctl --user list-timers

You should see:

gdrive-workspace.timer

7. How Smart Auto-Sync Works

When internet is OFF → rclone waits.
When internet is ON → rclone uploads new files.
Already uploaded files → NOT uploaded again.
Files deleted locally → NOT deleted in Drive. This behaves like true cloud backup.

8. Pause Syncing Anytime (Low Data Mode)

If your internet is weak, pause auto-upload:

systemctl --user stop gdrive-workspace.timer

Resume:

systemctl --user start gdrive-workspace.timer

Disable permanently:

systemctl --user disable gdrive-*.timer

9. Manual Upload (Optional)

If you want to force an upload right now:

rclone copy /home/arunkrish/workspace gdrive:workspace

10. Summary

With rclone + systemd:

Your folders upload automatically
Data usage stays low
No file ever gets deleted from Drive
Works even when offline
Full control (pause/resume anytime) This setup is cleaner and more powerful than official sync clients.

Start Open Source Contributions Now!

Arun Krish — Wed, 13 Aug 2025 19:14:15 +0000

✨ How to Write Commit Messages & Pull Requests for Open Source Contributions

Contributing to open-source projects on GitHub is a fantastic way to improve your skills, build your portfolio, and give back to the community.

But… before your code gets merged, maintainers need to understand what you’ve done and why.

That’s where clear commit messages and well-structured pull requests (PRs) come in.

In this post, we’ll walk through:

Writing clean commit messages
Creating pull requests that maintainers love
A ready-to-use PR template for your future contributions

1️⃣ Writing a Good Commit Message

A good commit message should be short, descriptive, and consistent.

✅ Commit Message Format

<type>: <short description>

Common commit types:

feat → new feature
fix → bug fix
docs → documentation change
style → formatting or styling changes
refactor → code improvements without changing behavior
test → adding or updating tests
chore → maintenance tasks

💡 Examples

fix: resolve crash when loading user profile
docs: update README with setup instructions
feat: add dark mode to settings page

If you need to explain more:

feat: add search functionality to events list

- Implemented SearchBar component with debounce
- Updated EventList component to filter results in real-time
- Added unit tests for search feature

Pro tips:

Keep the first line under 50 characters.
Use present tense (“add” not “added”).
Commit one logical change per commit.

2️⃣ Creating a Pull Request (PR)

A Pull Request is how you propose your changes to the main project.

Steps to create one:

Fork the repository.
Clone it locally:

   git clone https://github.com/<your-username>/<repo-name>.git

Create a new branch (don’t work on main):

   git checkout -b feat/search-bar

Make changes → commit:

   git add .
   git commit -m "feat: add search functionality to events list"

Push your branch:

   git push origin feat/search-bar

On GitHub, click "Compare & Pull Request".

3️⃣ Writing a Great PR Description

A PR description should explain what you did, why, and how to test it.

Here’s a PR template you can use:

## Description
Briefly explain the changes.

## Changes
- List key changes in bullet points.

## Screenshots / Demo (if applicable)
[Add screenshots or GIFs]

## Related Issue
Closes #<issue-number> (if fixing a bug or feature request)

## Checklist
- [ ] Code follows project style guidelines
- [ ] Tested locally
- [ ] Documentation updated if needed

📌 Example PR

## Description
Added a search bar to the Events page to filter events by name in real-time.

## Changes
- Added SearchBar component with debounce to prevent excessive re-rendering
- Updated EventList component to filter events list
- Added unit tests for the search functionality

## Related Issue
Closes #45

## Checklist
- [x] Code follows project style guidelines
- [x] Tested locally
- [ ] Documentation updated

🎯 Final Thoughts

Small commits = easier code review.
Clear PRs = faster approval.
Consistent format = happier maintainers.

Next time you contribute to open source, follow this guide — you’ll make life easier for both yourself and the maintainers. 🚀

If you found this helpful, save it for later and share it with someone starting their open-source journey! 💙

VIM is gem!!

Arun Krish — Sat, 15 Mar 2025 20:04:35 +0000

What is VIM? Basically, VIM will help you to code faster than you think, by using some commands. If you learn VIM, it's an advantage while competing with others, as well as it will increase your productivity. Yeah, you will not need a mouse anymore. If you don't get it, don't worry. We will figure it out in this blog!

Official site of VIM
VIM git repo
Here you can download
Or refer some YouTube videos

Download VIM on Linux

sudo apt update
sudo apt install vim

Open your terminal to check vim installed or not.

vim

You can see something like this in your terminal. To exit, type :q
and enter.

Use VIM in VScode

Add an extension named Vim to your VS code.

Here we start

After that, create a file. You can notice that the cursor has become wider. Also, you can notice the VIM modes in the bottom left of your VS code (Here is NORMAL).

While pressing i you can see the mode become Insert and the cursor become smaller. Now you are in insert mode. Type anything (actually your codes) and press esc so you can escape from the insert mode to normal mode.

Commands starting with : symbols you can see in the bottom left of your VS Code. Type :q to save your code written.

Below are some codes; play with them and learn more...

Here are the important commands to master VIM.

Basic Navigation

h → Move left
l → Move right
j → Move down
k → Move up
w → Move to the next word
b → Move to the previous word
0 → Move to the beginning of the line
^ → Move to the first non-whitespace character
$ → Move to the end of the line
gg → Go to the beginning of the file
G → Go to the end of the file
:n → Jump to line n (:10 goes to line 10)

Insert Mode

i → Insert before the cursor
I → Insert at the beginning of the line
a → Append after the cursor
A → Append at the end of the line
o → Open a new line below
O → Open a new line above

Editing

x → Delete the character under the cursor
dw → Delete a word
dd → Delete a line
D → Delete from cursor to the end of the line
yy → Copy (yank) a line
yw → Yank a word
p → Paste after the cursor
P → Paste before the cursor
u → Undo
Ctrl + r → Redo

Searching & Replacing

/word → Search for "word"
n → Jump to the next occurrence
N → Jump to the previous occurrence
:%s/old/new/g → Replace all occurrences of "old" with "new"
:%s/old/new/gc → Replace with confirmation
Saving & Exiting
:w → Save
:q → Quit
:wq or :x → Save and quit
:q! → Quit without saving
ZZ → Save and exit (shortcut)

Visual Mode

v → Start visual mode (select text character by character)
V → Start line-wise visual mode
Ctrl + v → Start block visual mode
y → Yank (copy) selected text
d → Delete selected text
> → Indent selected text
< → Un-indent selected text

Windows & Tabs

:split or :sp → Split window horizontally
:vsplit or :vsp → Split window vertically
Ctrl + w + w → Switch between windows
:tabnew → Open a new tab
gt → Switch to the next tab
gT → Switch to the previous tab

Thank you! Happy coding...

How do I revert a merged pull request?

Arun Krish — Sat, 18 Jan 2025 07:50:39 +0000

Here I am discussing how to revert a merged pull request and again push the branch. I am sharing this because I faced this issue while developing something...

Keep in mind that the working branch is "master" and the feature branch is "navbar".

If you don't know how to push your code into github, please visit my previous post here

Here we go...

The problem 1: I created a pull request in github and merged. But that isn't the actual code, or it's not working in the master branch after merging.

The merged file was navbar.

The solution: Let's checkout branch into master and pull the code from github, then check git log.

git checkout master
git pull origin master
git log

You can see a commit message like "merge pull request."

You can revert the commit using that commitId and a git command like

git revert -m 1 714013e1e7dc98787b73b9da197994b770d0c1d7

You can write the commit message for reason for reverting in the opening window and press ctrl x. Then push the code into github.

git push origin master

Now you reverted your pull request successfully. You can see that your merged files are removed now and a new commit message. Eg: here navbar file removed.

The problem 2: What What happens if you want to work in the navbar branch and create a new pull request again?

The solution: checkout into the branch navbar and work in the navbar branch and create a pull request.

git checkout navbar

After editing the file, add, commit and push.

git add .
git commit -m "navbar edited"
git push origin navbar

Go to GitHub and select the navbar branch.

You can see a contribute button; by pressing that, you can create a new pull request.

If there aren't any conflicts, it can merge. If there are any conflicts, first of all, go to your IDE checkout to the master branch and pull the code from github. Then checkout to branch navbar, then merge master into navbar.

git chekcout master
git pull origin master
git checkout navbar
git merge master

Now you can see the conflicts and solve the conflicts in the merge editor (hoping you are using vs code), select the incoming code.

Complete the merge, add, commit, and create a pull request once again.

Now you can create a pull request for the navbar branch by selecting the navbar branch, then clicking the contribute button and opening the pull request, create pull request.

You can see that conflicts are solved.

Thankyou
Happy coding:)

How to push your code into github.

Arun Krish — Sat, 18 Jan 2025 06:43:36 +0000

First of all, after you cloned a repo or for working on a new feature, its better to create a new branch and start working on that.

git branch branch-name
git branch navbar

Edit your file and add; commit your changes.

git add .
git commit -m "commit message"
git commit -m "navbar added"

For every push, you want to ensure that your codes are committed. Now you can push your code to github and create a pull request.

git push origin navbar

Note: If your github account is not connected to your IDE, you need to give the username as well as password of your github account. Your password while pushing is not your password for your github account. For that, you need to create a PAT: personal access token.

It takes a little time to push. After pushing open github, you can see a button showing to create a pull request.

By clicking "compare and pull request," you will go to the next page, where you can give a title and description for your pull request and press "create a pull request.". Congratulations! You created a new pull request.

You can see if there are any conflicts or not.

Thank you
Happy coding:)

TailwindCSS The Great!

Arun Krish — Sat, 21 Dec 2024 18:03:28 +0000

If you are a web developer and usually use CSS for styling, here is your game changer.

Tailwind CSS is a highly customizable, utility-first CSS framework used for designing modern websites and applications. Unlike traditional CSS frameworks like Bootstrap, which come with predefined components and styles, Tailwind focuses on giving developers utility classes to build custom designs directly in
their HTML.

How to install TailwindCSS

Here you can start learning.

The best video I found for more knowledge

Key Features of Tailwind CSS:

Utility-First Approach:
Provides small, single-purpose classes (e.g., text-center, bg-blue-500, p-4) that can be combined to create custom designs.
Customization:
You can customize every aspect of the framework (colors, spacing, breakpoints, etc.) through a tailwind.config.js file.
Responsive Design:
Built-in support for responsive design using prefix-based classes like sm:, md:, lg:, etc.
No Predefined Components:
Instead of providing ready-made components, it focuses on giving the building blocks to create your components.
Dark Mode:
Supports dark mode out of the box with dark: bg-black.
Performance Optimizations:
Removes unused styles (via tools like PurgeCSS or built-in optimization in newer versions) to make production files small and fast.
Consistency and Maintainability:
Helps maintain consistent designs by encouraging the use of utility classes instead of writing custom CSS repeatedly.

CRUD in Firebase

Arun Krish — Sun, 07 Jul 2024 10:44:40 +0000

CRUD operation in Firebase using react and javascript


        // Read
        db.collection('products').get().then(resposne=>{
          resposne.forEach((object)=>{
            console.log(object.data(),object.id);
          })
        })

        // Create
        db.collection('products').add({
          name: 'Laptop',
          type: 'Electronics',
          price: 50000
        }).then(()=>{
          console.log('Added');
        })

        // Delete
        db.collection('products').doc('Q4tjiYSC05MjYG6pQBIQ').delete().then(()=>{
          console.log('Deleted');
        })

        // Update
        db.collection('products').doc('BDgu0r6ECRtyUKxxkxcs').update({
          name: 'Laptop',
          type: 'Electronics',
          price: 50
        }).then(()=>{
          console.log('Updated');
        })

How to host your code in github?

Arun Krish — Thu, 16 May 2024 12:34:21 +0000

HOW TO ADD ANY FILES INTO HOSTING PLATFORMS (GitHub,GitLab,etc)

About this article

This article show us how to add your program file into hosting platform like GitHub, GitLab, etc. We do this by using git version control tool. Git tool is different from GitHub and GitLab.

Git is a distributed version control system that tracks changes in any set of computer files, usually used for coordinating work among programmers who are collaboratively developing source code during software development. Its goals include speed, data integrity, and support for distributed, non-linear workflows (thousands of parallel branches running on different computers).

Follow the following steps to upload your file into hosting platforms.

First of all download git from here. Git is inbuilt software for Linux, to conform that type git --version in terminal.
Open the git bash on your windows, mac and type git --version to conform that git downloaded successfully. I will use the word terminal, for windows and mac users it same as git bash.
Choose your file (the file you want to upload) by typing cd file_name, dir. cd file_name for choose folder and dir for showing all files in current folder. This command varies with OS.
Type git init for add local git file (.git) into your system. You can locate this file by entering into the folder that you located early and turn on hidden files. You can see a .git file in this folder.
Make necessary edit in the programming file and type in terminal git status to conform file edited successfully and follow below commands.
git add — all for choose all the coded file.
git commit -m “new file added” for locally save the code with a message.
git remote
git remote add origin https://github.com/ARUNKRISH11/Sample
Adding git repo link (for each project first time only need this line of command). The link will get by creating new repository in GitHub or GitLab. For creating new repository in GitHub follow the instructions in the below image named 'Create new repository in your GitHub.'
To see the remote name and link used previously use git remote or git remote -v
git push origin master to uploading the file into your GitHub repository.
After that you need to enter hosting platform username and token ID “ARUNKRISH11, ghp_G3cketo8dqEKrp6ubZh3h5GYs5vClDF”
You can generate token id in GitHub by follow the instructions in the below image named 'Create new repository in your GitHub'

All commands used in this post

git --version
cd file_name
dir
git init
git status
git add --all
git commit -m "new file added"
git remote
git remote add origin https://github.com/ARUNKRISH11/Sample
git push origin master

Steps done in terminal or git bash

Create new repository in your GitHub.

Generate GitHub personal access token ID

Thank you for taking the time to read through this Git explanation post! I hope it has clarified some of the key concepts and features of Git for you. Whether you're a beginner just starting out or an experienced developer looking to brush up on your skills, Git is an invaluable tool for version control and collaboration.

A big shoutout to the awesome developer community here for always fostering an environment of learning and growth. Your questions, feedback, and contributions are what make this community so special.

Feel free to share your thoughts, ask questions, or provide additional tips in the comments below. Let's keep the conversation going and continue to learn from each other!

Happy coding! 🚀