|
I'm an AI/ML undergraduate with strong foundations in Python, Java, Computer Networking, and AI/ML. I enjoy designing intelligent, automation-driven solutions and getting my hands dirty with real-world problem solving β from building AI-assisted developer tools to configuring firewalls and virtualization stacks. I learn through hands-on projects, coding practice, and real-world experimentation.
ββββββββββββββββ
β AI / ML β
βββββββββ¬βββββββ
β
βββββββββββββββββββΌββββββββββββββββββ
β β β
βΌ βΌ βΌ
ββββββββββββββββββββ ββββββββββββββββββ ββββββββββββββ
β SOFTWARE β β NETWORKING / β β AUTOMATION β
β ENGINEERING β β INFRASTRUCTURE β β β
ββββββββββββββββββββ ββββββββββββββββββ ββββββββββββββ
|
π€ AI / ML
|
π» Software Engineering
|
π Networking / Infrastructure
|
|
StarkAlgoLens is an AI-powered coding mentor with a React (Vite + Tailwind CSS) frontend and a FastAPI backend. It performs code analysis and secure code execution, then generates personalized learning roadmaps and tracks progress over time. Under the hood:
|
Node trail
|
|
A Python automation tool that reads a source PDF, parses it into structured JSON, maps fields using rule-based logic, and drives a Google Form submission through Playwright browser automation β including handling of ambiguous input cases. |
|
Capabilities: Python automation β’ PDF parsing β’ JSON extraction β’ rule-based field mapping β’ Playwright browser automation β’ ambiguous-input handling
A private, on-premises network built and administered end-to-end β not just web development. The lab covers:
- π₯ pfSense firewall policy configuration
- π Cisco and Juniper switching / routing
- π§± Network segmentation
- π₯οΈ Proxmox-based virtual machines and containerized services
The contribution snake is generated automatically by the
snake.ymlGitHub Action (see Setup below) and regenerates daily from real contribution data.First-time setup: the image above won't render until
snake.ymlhas run at least once and created theoutputbranch. Trigger it manually from the Actions tab (Run workflow) right after publishing this repo β no placeholder or fallback image is used, so the space stays empty until the real data exists.
Live GitHub statistics and activity metrics rendered via high-availability badge services.
Areas I'm actively building in β not a ranked or scored list.
βββββββββββββββ
β AI / ML β
ββββββββ¬βββββββ
β
βββββββββββββββββΌββββββββββββββββ
βΌ βΌ βΌ
βββββββββββββ βββββββββββββββ ββββββββββββββ
β Automationβ β Intelligent β β DSA / β
β β β Software β β Problem β
β β β Systems β β Solving β
βββββββββββββ βββββββββββββββ ββββββββββββββ
ββββββββββββββββββββββββββββββββββ
βΌ βΌ
βββββββββββββββ ββββββββββββββββββββ
β Computer β β Infrastructure β
β Networking β β Experimentation β
βββββββββββββββ ββββββββββββββββββββ
JAYMITHRAN
β
ββββββββββββββββ¬βββββββββββββββ
βΌ βΌ βΌ
GitHub LinkedIn LeetCode
βοΈ Setup & configuration (for repository owner β click to expand)
Place these files in a repository named exactly JAYMITHRAN/JAYMITHRAN (a repo matching your username makes GitHub render this as your profile page). Folder layout:
JAYMITHRAN/
βββ README.md
βββ assets/
β βββ hero.svg
β βββ tech-network.svg # source copy β README embeds this inline (see Β§2)
β βββ starkalgolens-architecture.svg
β βββ network-lab.svg
β βββ achievements.svg
β βββ education.svg
βββ .github/
βββ workflows/
βββ snake.yml
GitHub renders <img src="*.svg"> as a flat, rasterized-style image β any <a href> links baked into that SVG are inert in that context. The Tech Constellation diagram is pasted directly into README.md as raw inline SVG instead of loaded via <img>. That's the only section handled this way; every other diagram (hero, StarkAlgoLens architecture, network lab, achievements, education) stays as a normal <img> reference since they don't need interactivity.
Note: GitHub's markdown sanitizer may strip
<a>elements from inline SVGs, making the tech-node links non-clickable on GitHub. The inline SVG is retained for visual consistency and because it renders the diagram natively without rasterization artifacts. If clickable links are essential, consider adding a markdown link list below the diagram as a fallback.
Keep assets/tech-network.svg and the inline copy in README.md in sync if you edit the node links or layout later β they are two copies of the same diagram by necessity of this workaround.
Uses Platane/snk to render your real contribution graph as an SVG on a schedule, and publishes it to an output branch via crazy-max/ghaction-github-pages.
- No extra secrets needed beyond the default
GITHUB_TOKEN. - After the first run, an
outputbranch will exist containingdist/snake-dark.svganddist/snake.svg. - The README references
raw.githubusercontent.com/JAYMITHRAN/JAYMITHRAN/output/snake-dark.svgβ replaceJAYMITHRANwith your actual username/repo if different. - In Settings β Actions β General, ensure "Workflow permissions" is set to Read and write permissions so the action can push to the
outputbranch. - First run: trigger the workflow manually (
Actionstab βGenerate Contribution SnakeβRun workflow) right after publishing the repo β the image has nothing to display until that first run creates theoutputbranch.
Uses the live github-readme-streak-stats service β works immediately with high uptime, just replace JAYMITHRAN in the image URL if you fork this for another account.
Search this repository for JAYMITHRAN and replace with your own username in:
README.md(social badge links, stats URL, snake image URL, inline SVG links point to external docs and don't need changing)snake.yml(uses${{ github.repository_owner }}automatically β no edit needed if the repo is under your account)
| Service | Purpose | Reliability notes |
|---|---|---|
| Platane/snk | Contribution snake SVG generation | Runs via your own GitHub Action β no third-party uptime dependency |
| github-readme-streak-stats | Live contribution streak & activity stats | Dedicated high-availability deployment via demolab.com |
| Shields.io | Social link badges only (GitHub/LinkedIn/LeetCode) | Static badge rendering, high uptime |
- All technologies listed are present in the source resume
- All project descriptions are resume-supported (no invented features)
- No fabricated metrics, star counts, proficiency percentages, or line-of-code figures
- All social links point to the stated usernames/handles
- All 22 tech-node links point to official docs/sites (no random third-party sources)
- No emoji used inside any SVG file (vector icons only)
- Images include descriptive
alttext for accessibility - Unused
stats.ymlworkflow and its unreferenced output asset removed
