██╗  ██╗ █████╗ ██████╗ ███████╗██╗  ██╗ █████╗
██║  ██║██╔══██╗██╔══██╗██╔════╝██║  ██║██╔══██╗
███████║███████║██████╔╝███████╗███████║███████║
██╔══██║██╔══██║██╔══██╗╚════██║██╔══██║██╔══██║
██║  ██║██║  ██║██║  ██║███████║██║  ██║██║  ██║
╚═╝  ╚═╝╚═╝  ╚═╝╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝╚═╝  ╚═╝

#!/usr/bin/env python3

class HarshaVardhan:
    name        = "Harsha Vardhan Yelleti"
    alias       = "Born-as-Harsha"
    university  = "KL University, Visakhapatnam"
    degree      = "B.Tech ECE (Electronics & Communication)"
    focus       = ["VLSI Design", "ASIC", "Semiconductors"]
    languages   = ["Python", "C", "Verilog", "TypeScript", "JavaScript"]
    tools       = ["Cadence", "Synopsys", "LTSpice", "Django", "React"]
    currently   = "RTL → GDSII flow, ERP tooling & full-stack projects"
    goal        = "Build at the intersection of Hardware & AI 🚀"

    def motto(self) -> str:
        return "Turning silicon into intelligence ⚡"

me = HarshaVardhan()
print(me.motto())
# Output: Turning silicon into intelligence ⚡

This profile spans two complementary engineering disciplines: VLSI / ASIC design — covering RTL-to-GDSII flows and analog/digital circuit simulation — and full-stack software engineering, built on Django, React, and modern UI tooling. The underlying objective is fluency at the point where hardware design and software/AI tooling converge.

Forked/learning repositories (Y24OpenSourceEngineering, open-source-practice, first-contributions) are kept starred for ongoing open-source practice and are intentionally left out of the featured table above to keep it focused on original work.

status:
  completed:
    - ✅  Build complete BTech ECE resource repository
    - ✅  Launch personal portfolio (now live at harshavardhan-vlsi.lovable.app)
    - ✅  Build Django full stack web application
    - ✅  Surpass 300+ GitHub contributions
    - ✅  Build blog platform with comments system
    - ✅  Build e-commerce web application
    - ✅  Build task management application

  in_progress:
    - 🔄  Master Cadence & Synopsys full design flow
    - 🔄  Complete VLSI project  RTL → GDSII
    - 🔄  Build out amdox-erp-suite UI modules
    - 🔄  Iterate on portfolio UI/UX (Harshavardhan-portfolio-2026)

  upcoming:
    - ⏳  Publish research / technical blog
    - ⏳  Open-source an ML + Hardware project
    - ⏳  Land VLSI / Semiconductor internship

Most repositories are independent projects; clone the one you're interested in rather than this profile repo itself.

1. Pick a project from the featured projects table above.
2. Clone it:

   git clone https://github.com/Born-as-Harsha/<repo-name>.git
   cd <repo-name>

3. Check the stack shown in the table (Django/Python, TypeScript/React, or Verilog) and follow the matching setup below.
4. Read the repo's own README for any project-specific environment variables or dependencies before running it.

(e-commerce app, task manager, student activity tracker)

1. Create and activate a virtual environment:

   python -m venv venv
   source venv/bin/activate        # Windows: venv\Scripts\activate

2. Install dependencies:

   pip install -r requirements.txt

3. Apply database migrations:

   python manage.py migrate

4. Start the development server:

   python manage.py runserver

5. Open http://127.0.0.1:8000/ in your browser.

(portfolio codebases, amdox-erp-suite)

1. Install Node.js 18 LTS or later.
2. Install dependencies:

   npm install

3. Start the dev server:

   npm run dev

4. Open the local URL printed in the terminal (typically http://localhost:5173/).

The live portfolio is built and prototyped with Lovable, an AI-assisted React/Vite/Tailwind app builder. To run or modify the prototype:

1. View or edit visually — open the portfolio's Lovable project via the "Edit with Lovable" link in the site footer; changes made there sync automatically to the live deployment.
2. Work with the code locally instead, if the project has been exported/synced to a GitHub repo:

   git clone https://github.com/Born-as-Harsha/<portfolio-repo-name>.git
   cd <portfolio-repo-name>
   npm install
   npm run dev

3. Environment check — Node.js 18+ and npm are the only hard prerequisites; the project uses Vite, so no separate build step is needed for local development.
4. Preview a production build before publishing:

   npm run build
   npm run preview

5. Deploy — Lovable auto-publishes on save; for the GitHub-synced copy, pushing to the connected branch triggers redeployment.

Finding the right project

• Browse the featured projects table above to find a repo relevant to your interest (VLSI/HDL, Django full-stack, or frontend/portfolio work).
• Status tags (Active, Complete, In progress, Reference) indicate how much ongoing maintenance to expect — treat Complete/Reference repos as stable, and Active/In progress repos as subject to change.

Running a project

• Each repo is self-contained; follow the setup steps above for its stack, then check its local README for anything project-specific (env vars, seed data, API keys).
• For Django apps, run with DEBUG=True locally only; never reuse the development SECRET_KEY or default admin credentials in a deployed environment.
• For React/TypeScript apps, use the Node version specified in the repo's package.json/.nvmrc if present, to avoid dependency-resolution issues.

Using the live portfolio

• The live portfolio at harshavardhan-vlsi.lovable.app is read-only and meant for browsing project write-ups, case studies, research, and contact details — it is not a repository to clone.
• Best viewed in an up-to-date Chromium, Firefox, or Safari browser; the layout is responsive but optimized primarily for desktop viewing of technical diagrams.

Reporting problems

• If something in a repo doesn't run as documented, or a link in this profile README is broken, please open an issue on the relevant repository (or on this profile repo for README-level issues) rather than assuming it's intentional.

Contributions, issues, and suggestions are welcome on any of the public repositories linked above.

1. Fork & branch

git clone https://github.com/<your-username>/<repo-name>.git
cd <repo-name>
git checkout -b <type>/<short-description>

Use a type/ prefix for branch names, e.g. feature/add-dark-mode, fix/broken-nav-link, docs/update-readme.

2. Code standards

• Match the existing formatting/style already used in the file you're editing (indentation, naming, import order).
• For Python/Django code, follow PEP 8 and run python -m py_compile (or the repo's linter, if configured) before committing.
• For TypeScript/React code, run npm run lint (and npm run build) locally to catch type or build errors before opening a PR.
• Keep changes minimal and scoped — avoid unrelated formatting-only diffs mixed into a functional change.

3. Commit messages Use short, imperative, present-tense messages, ideally following Conventional Commits:

feat: add responsive nav to portfolio
fix: correct migration order in task-management-application
docs: update setup steps for amdox-erp-suite

4. Pull requests

• Push your branch and open a PR against the repo's default branch.
• In the PR description, include: what changed, why, and how it was tested (screenshots welcome for UI changes).
• Link any related issue with Closes #<issue-number>.
• For larger or breaking changes, please open an issue first to discuss the approach before investing significant time.

5. Review

• Expect feedback or requested changes rather than an immediate merge — please keep the conversation in the PR thread.
• Once approved, PRs are merged via squash-merge to keep history clean; you don't need to squash commits yourself beforehand.

To keep the links in this profile stable and reduce the chance of future breakage:

• The live portfolio is hosted on Lovable at a fixed subdomain (harshavardhan-vlsi.lovable.app); verified reachable and serving the current portfolio content. Any future migration will be announced here with the old link kept as a redirect where possible.
• The header's typing-animation badge links through git.io/typing-svg, which is the standard, still-functioning redirect used by the readme-typing-svg project itself (confirmed against the tool's own documentation) — not a stale shortlink.
• All project links point to GitHub repository URLs rather than third-party mirrors, since GitHub URLs remain stable as long as the repo isn't renamed or deleted.
• Stats/graph widgets use the official canonical endpoints for each project (github-readme-stats.vercel.app, streak-stats.demolab.com, github-readme-activity-graph.vercel.app, github-profile-summary-cards.vercel.app) — earlier deployments some of these tools used (e.g. Heroku/Cyclic-hosted versions) have since been shut down, so only current, actively maintained URLs are used here.
• The github-readme-stats cards include a cache_seconds parameter to reduce intermittent 429 Too Many Requests responses, since the shared public instance is rate-limited and best-effort by design; if a card still fails to render, it's almost always a temporary rate limit or Vercel hiccup rather than a broken link — reloading the page or waiting a few minutes resolves it.
• For guaranteed uptime on these widgets, each tool supports self-hosting (one-click Vercel deploy or a GitHub Action that commits static cards to the repo); this is the recommended next step if a badge needs to be 100% reliable rather than best-effort.
• This README is reviewed periodically alongside repository updates so that project statuses, links, and the featured table stay in sync with what's actually shipped.

Harsha Vardhan Yelleti  ·  ECE @ KL University  ·  Visakhapatnam

"I build at the intersection of hardware and software — where VLSI meets AI, the future is written in silicon." 🔬