Skip to content
View NitkarshChourasia's full-sized avatar
🦁
pragmaticForAndToLife
🦁
pragmaticForAndToLife

Organizations

@EddieHubCommunity @Py-Contributors @FunsukWangdu00

Block or report NitkarshChourasia

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
NitkarshChourasia/README.md

About Me

I am Nitkarsh Chourasia, a developer who likes turning curiosity into working software. I learn by building: small tools, experiments, automation scripts, backend projects, language practice repositories, and notes that make difficult topics easier to revisit.

  • Currently exploring Rust, compilers, toy databases, peer-to-peer transfer, and backend fundamentals.
  • Building with Python, JavaScript, C/C++, C#, Java, notebooks, and practical AI/document workflows.
  • Interested in automation, full-stack development, data-heavy tools, open-source learning, and clean project documentation.
  • Operating principle: be pragmatic, ship working systems, then improve them with evidence.

Featured Work

NotebookHub repository card alive_document repository card
rust_compiler repository card database repository card
fun_py repository card leetcode_journey_through repository card

What I Build

Area Current Direction
Backend and automation Python scripts, Flask/Django learning, Node.js, API-shaped utilities, and repeatable workflows
Systems learning Rust practice, compiler notes, toy database ideas, file transfer experiments, and lower-level engineering fundamentals
Data and AI Jupyter/Colab notebooks, OCR/document ideas, ML practice, prompt engineering, and practical tooling
Programming foundations DSA, language practice, puzzle repositories, C/C++, C#, Java, and JavaScript fundamentals
Creative technology Web portfolios, video/audio/image tooling, presentations, spreadsheets, and documentation

Toolbox

Python, JavaScript, HTML, CSS, Node.js, Java, C++, C#, Rust, Git, GitHub, Linux, Django, Flask, MySQL, SQLite, VS Code, Figma, Photoshop, Premiere Pro

Python JavaScript Rust C++ C# Jupyter

GitHub Snapshot

Nitkarsh Chourasia GitHub stats Nitkarsh Chourasia top languages
Nitkarsh Chourasia GitHub streak
Nitkarsh Chourasia GitHub activity graph
More places to find me

Facebook | Instagram | Pinterest | Quora | Reddit | X/Twitter | YouTube

Holopin badges

An image of @nitkarshchourasia's Holopin badges, linking to the full Holopin profile


Animated wave divider

Being pragmatic is the way.

Pinned Loading

  1. A brief introduction about me. A brief introduction about me.
    1
    class Person:
    2
        def __init__(self, name, bio, website, social_media):
    3
            self.name = name
    4
            self.bio = bio
    5
            self.website = website
  2. Git best practices. Git best practices.
    1
    Using Git effectively and following best practices can help you avoid failures, prevent irreversible mistakes, and ensure the successful development of features. Here are some Git best practices to consider:
    2
    
                  
    3
    1. **Use Version Control**: Always use version control, like Git, to track changes in your codebase. This allows you to maintain a history of your project, revert to previous states, and collaborate effectively.
    4
    
                  
    5
    2. **Branching Strategy**: Follow a branching strategy like Gitflow, where you have different branches for features, releases, and hotfixes. This helps isolate work, manage features, and stabilize releases.
  3. Owner_PRs_CODEREVIEW Owner_PRs_CODEREVIEW
    1
    To allow others to review your code on GitHub when you are the owner and primary contributor, you can follow these steps:
    2
    
                  
    3
    1. **Create a Branch:** Before you start working on a new feature or making changes, create a new branch in your repository. This branch will contain the changes you want others to review.
    4
    
                  
    5
    2. **Make Changes:** Add, modify, or delete code as needed to implement the feature or fix an issue.