Creative Projects
08 · Creative Projects & Portfolio Strategy
Alex, your strongest admissions lever right now is building a visible, public body of technical work that admissions readers can actually click on and evaluate. Stanford, MIT, and Georgia Tech all value demonstrated builders — students who ship, not just study. Here's your concrete roadmap.
Project 1: Open-Source Your SLAM Robotics System
You already have a robotics navigation system — the fastest win is transforming it into a polished open-source repository. This is MIT's preferred evidence format: a codebase that proves you can engineer at a high level and communicate technically.
| Component | Deliverable | Why It Matters |
|---|---|---|
| Repository Structure | Clean repo with /src, /docs, /tests, /examples directories | Shows software engineering maturity beyond "it works on my machine" |
| README | Project overview, architecture diagram, installation guide, GIF/video demo | MIT and Stanford reviewers will spend ~90 seconds on your repo — the README is your pitch |
| Documentation | API reference, algorithm explanation (how your SLAM approach works), design decisions | Separates you from students who dump code without context |
| Testing | Unit tests with CI/CD via GitHub Actions (aim for 70%+ coverage) | Successful CS portfolios (see Arvin R., Stanford admit) featured CI/CD pipelines as proof of professional practice |
| License & Contributing Guide | MIT or Apache 2.0 license, CONTRIBUTING.md with issue templates | Signals you understand open-source culture and want community engagement |
Success metric: 15+ GitHub stars and at least 2 external contributors or forks within 3 months of launch. Promote it in relevant Reddit communities (r/robotics, r/SLAM), ROS forums, and Hacker News "Show HN."
Project 2: Build & Ship an Independent Product (Pattern-Breaking)
Alex, your profile currently centers heavily on robotics and ML. That coherence is a strength — but at Stanford and MIT, it can also read as narrow. Your second project should deliberately break the pattern by applying your CS skills to a completely different domain. This proves versatility and intellectual range.
Here are three concrete options — pick one and commit fully:
| Project Idea | Tech Stack | Domain Signal | Best Fit School |
|---|---|---|---|
| Civic Tech: Local Transit Accessibility Tool — a web app that maps wheelchair-accessible routes using public transit data and crowd-sourced reports | Python (FastAPI), React, PostgreSQL + PostGIS, Mapbox API | Shows you care about people, not just algorithms | Stanford (human-centered CS culture) |
| Developer Utility: Git Commit Analyzer — a CLI tool that uses NLP to analyze commit message quality, flag poor practices, and generate weekly team health reports | Python or Go, spaCy/HuggingFace, GitHub API, PyPI/Homebrew distribution | Shows you build tools for developers — meta-engineering | MIT (tool-builder identity) |
| Creative Coding: Generative Art Platform — a browser-based tool where users create algorithmic art using a visual node editor, exportable as SVGs or NFTs | TypeScript, Canvas/WebGL, Node-based UI (like Rete.js), Vercel deploy | Shows artistic sensibility — rare and memorable for CS applicants | Georgia Tech (computational media program) |
The non-negotiable requirement: whichever project you choose must have real users. Not a class demo. Not a hackathon prototype. A deployed, usable product. Target 50+ active users or 100+ downloads within two months of launch. This is the single clearest differentiator between admitted and waitlisted CS applicants at elite programs.
Build Plan & Timeline
| Phase | Activities |
|---|---|
| Phase 1: SLAM Open-Source | Refactor codebase, write documentation, set up CI/CD, publish repo, begin promotion |
| Phase 2: New Project — Prototype | Choose project, define MVP scope (ruthlessly small), build core feature, deploy alpha |
| Phase 3: New Project — Launch | User testing, iterate on feedback, public launch, write blog post explaining the build |
| Phase 4: Portfolio Polish | Update GitHub profile, write project case studies, record demo videos, finalize all READMEs |
GitHub Profile Strategy
Your GitHub profile is a second transcript for CS admissions. Here's what a strong profile looks like versus a weak one:
| Element | ❌ Weak Signal | ✅ Strong Signal |
|---|---|---|
| Contribution graph | Sporadic green squares, long gaps | Consistent activity across months — doesn't need to be daily, but shows sustained work |
| Pinned repos | Default or empty | 3-4 pinned repos: SLAM project, new project, one smaller utility or learning project |
| README quality | Auto-generated or missing | Custom profile README with bio, project highlights, and links |
| Stars & forks | 0 on all repos | 15+ stars on main projects (organic, from community promotion) |
| Code quality | Single massive commits, no structure | Atomic commits with clear messages, pull request workflow even on solo projects |
Tactical tip: Create a profile README (a repo named after your GitHub username) that serves as a landing page. Include a one-line bio, links to your two main projects, your tech interests, and a "Currently building..." status. Admissions readers and recommendation letter writers will see this first.
Portfolio Presentation Layer
Beyond GitHub, Alex, you need a simple personal portfolio site — a single-page site that ties everything together. This is what you'll link in your application's "additional information" section.
- Tech: A static site (Next.js or even plain HTML/CSS on GitHub Pages — don't over-engineer this)
- Content: Two project case studies (SLAM + new project), each with: problem statement → technical approach → architecture diagram → outcome/impact → link to repo and live demo
- Tone: Write like an engineer explaining to a smart non-expert. Avoid jargon dumps. Show your thinking, not just your code
- Blog section (optional but powerful): 2-3 short posts documenting what went wrong during development and how you solved it — successful portfolios consistently feature a "failure narrative" that demonstrates resilience and learning
What You Haven't Provided Yet
Alex, you have not provided details about your current GitHub activity, existing personal projects outside of structured programs, or any hackathon or competition project history. If you have any existing code, deployed apps, or technical writing, please share them — we may be able to incorporate or elevate work you've already done rather than starting from scratch.
Key Principle
Every element of this strategy serves one goal: when a Stanford or MIT admissions reader Googles your name or clicks your GitHub link, they should see a builder — someone who creates real things, documents them clearly, and cares about impact beyond the terminal. Your SLAM project gives you a head start. The pattern-breaking second project proves range. The polished GitHub profile ties it all together into a cohesive technical identity that no transcript alone can convey.