Skip to content
View Shashank0701-byte's full-sized avatar

Highlights

  • Pro

Block or report Shashank0701-byte

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.

Content in all repositories owned by your account will be closed.
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
Shashank0701-byte/README.md
███████╗██╗  ██╗ █████╗ ███████╗██╗  ██╗ █████╗ ███╗   ██╗██╗  ██╗
██╔════╝██║  ██║██╔══██╗██╔════╝██║  ██║██╔══██╗████╗  ██║██║ ██╔╝
███████╗███████║███████║███████╗███████║███████║██╔██╗ ██║█████╔╝ 
╚════██║██╔══██║██╔══██║╚════██║██╔══██║██╔══██║██║╚██╗██║██╔═██╗ 
███████║██║  ██║██║  ██║███████║██║  ██║██║  ██║██║ ╚████║██║  ██╗
╚══════╝╚═╝  ╚═╝╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝╚═╝  ╚═╝╚═╝  ╚═══╝╚═╝  ╚═╝
boot sequence


🐍 something's eating my commit history

snake eating contribution graph

⚙️ auto-generated nightly by GitHub Actions — see setup below


🧊 my contributions, but make it 3D

3D contribution graph

$ kubectl get engineer shashank -o yaml

apiVersion: v1
kind: Engineer
metadata:
  name: shashank-chakraborty
  location: bengaluru-in
  status: fourth-year-student
spec:
  focus: [backend-engineering, devops-automation, cloud-security]
  currentlyBuilding: infrastructure-drift-detection-engine
  personality: >
    Will rebuild a working CI/CD pipeline for a 6-minute improvement.
    Reads incident postmortems for fun. Cannot leave a sequential
    pipeline alone — will parallelize it out of principle.
status:
  uptime: "since 2023"
  lastIncident: "shipped instead of sleeping"
  reliability: "measured, not assumed"

📡 skill radar

skill radar chart

🛰️ $ terraform plan — current infra

graph TD
    A[Shashank] --> B[Backend APIs]
    A --> C[DevOps & Infra]
    A --> D[Cloud Security]
    B --> B1[FastAPI / Flask / Node.js]
    B --> B2[Async pipelines - Celery / Redis]
    C --> C1[Docker + Kubernetes + HPA]
    C --> C2[CI/CD - GitHub Actions]
    C --> C3[Observability - Prometheus / Grafana]
    D --> D1[AWS IAM graph analysis]
    D --> D2[Privilege escalation detection]
Loading

📟 $ git log --oneline --graph --decorate — highlight reel

* a1b2c3d (SystemCraft) parallelize CI/CD pipeline
|         → 10min sequential → under 4min, fixed artifact-integrity bug too
* 9f8e7d6 (SystemCraft) k6 load test @ 500 concurrent users
|         → p95 latency 3.33s → 861ms (-74%), throughput +161%
* 4c5d6e7 (Shadow Permission Analyzer) BFS/DFS on AWS IAM graph
|         → detects multi-hop privilege escalation chains in Neo4j
* 2b3c4d5 (DocuFlow) event-driven invoice pipeline
|         → async workers cut processing time by 40%
* 1a2b3c4 (Hackman) 24hr national hackathon, team ClarityAI
          → top 10, agentic decision-intelligence tool

📦 featured deploys

SystemCraft — real-time system design simulator (live · repo)

Built to answer one question: does my infra work under load, or does it just look like it does? Kubernetes HPA, a CI/CD pipeline I tore apart and rebuilt for speed, and a Gemini-powered evaluation engine with race-condition handling on concurrent AI calls.

Stack: Next.js · MongoDB · Kubernetes · GitHub Actions · Prometheus/Grafana · k6

Shadow Permission Analyzer — AWS IAM privilege-escalation detector (repo)

Models IAM identities as a graph instead of a flat policy list, because privilege escalation is a path problem, not a single-permission problem. BFS/DFS traversal finds multi-hop chains a manual audit would miss.

Stack: Python · Neo4j · FastAPI · boto3 · pytest

DocuFlow — event-driven invoice pipeline (repo)

OCR parsing and data extraction split into independently scalable workers, because a single fat script is not a pipeline. 40% faster processing through async orchestration.

Stack: Python · Celery · Redis · PostgreSQL

🚧 DriftGuard — infra drift detection engine (planning)

Compares live Docker/Kubernetes environments against Git-managed config and flags what quietly changed underneath you. Because "it worked when I deployed it" is not a monitoring strategy.

Planned stack: Python · FastAPI · Docker · Kubernetes · GitHub Actions


🧠 $ leetcode — solving problems, one bug at a time


$ echo "always be shipping" >> /etc/motd

Profile views

Pinned Loading

  1. Shadow-permission-analyser Shadow-permission-analyser Public

    Python

  2. docuflow docuflow Public

    DocuFlow is a containerized, event-driven pipeline that automates ingestion, OCR, parsing, and analytics for invoices and financial documents.

    Python 5

  3. System-Craft System-Craft Public

    Bridging the Gap Between Theoretical Knowledge and Practical System Design. System design is fundamentally an exercise in navigating trade-offs. Traditional preparation methods rely heavily on stat…

    TypeScript

  4. personal-portfolio personal-portfolio Public

    TypeScript

  5. interview-prep interview-prep Public

    JavaScript 3

  6. CoreX CoreX Public

    C