Files
TinyTorch/paper
Vijay Janapa Reddi 3e38929e34 Restructure Discussion and strengthen Conclusion per research feedback
Major improvements to Discussion and Future Work sections based on comprehensive
research team feedback:

DISCUSSION SECTION (Section 8):
- Added new 'Design Insights' subsection opening with positive framing:
  * Progressive disclosure effectiveness through gradual feature activation
  * Systems-first integration preventing 'algorithms without costs' learning
  * Historical milestones as pedagogical checkpoints with validation
  * Build-Use-Reflect cycle enabling immediate application

- Consolidated 'Scope' and 'Limitations' into unified section with trade-off framing:
  * Production Systems Beyond Scope (GPU, distributed, deployment)
  * Infrastructure Maturity Gaps (NBGrader validation, performance, energy)
  * Accessibility Constraints (language, type hints, advanced concepts)
  * Connected limitations to deliberate pedagogical choices

FUTURE DIRECTIONS (Section 9, renamed from 'Future Work'):
- Reorganized with clear structure prioritizing empirical validation first
- Made tool mentions more concept-focused (e.g., 'distributed training simulation'
  vs 'ASTRA-sim for distributed training simulation')
- Removed duplicate sections and consolidated curriculum extensions
- Maintained detailed empirical validation roadmap (3-phase plan)

CONCLUSION (Section 10):
- Complete rewrite with strong vision statement and call to action
- Opens with fundamental choice: use frameworks vs understand frameworks
- Expanded practitioner value proposition with concrete debugging scenarios
- Added memorable closing: 'The difference between engineers who know what ML
  systems do and engineers who understand why they work'
- Transformed from passive ('one approach') to confident and inspiring

STRUCTURAL IMPROVEMENTS:
- Discussion now opens positively (Design Insights) before limitations
- Future Directions organized by audience (researchers, educators, community)
- Conclusion ends with vision + call to action instead of apologetic tone
- Fixed undefined reference (subsec:future-work -> sec:future-work)

Paper compiles successfully with no LaTeX errors or undefined references.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-19 09:08:13 -05:00
..

TinyTorch Research Paper

Complete LaTeX source for the TinyTorch research paper.


Files


Quick Start: Get PDF

  1. Go to Overleaf.com
  2. Create free account
  3. Upload paper.tex and references.bib
  4. Click "Recompile"
  5. Download PDF

Option 2: Local Compilation

./compile_paper.sh

Requires LaTeX installation (MacTeX or BasicTeX).


Paper Details

  • Format: Two-column LaTeX (conference-standard)
  • Length: ~12-15 pages
  • Sections: 7 complete sections
  • Tables: 3 (framework comparison, learning objectives, performance benchmarks)
  • Code listings: 5 (syntax-highlighted Python examples)
  • References: 22 citations

Key Contributions

  1. Progressive disclosure via monkey-patching - Novel pedagogical pattern
  2. Systems-first curriculum design - Memory/FLOPs from Module 01
  3. Historical milestone validation - 70 years of ML as learning modules
  4. Constructionist framework building - Students build complete ML system

Framed as design contribution with empirical validation planned for Fall 2025.


Submission Venues

  • ArXiv - Immediate (establish priority)
  • SIGCSE 2026 - August deadline (may need 6-page condensed version)
  • ICER 2026 - After classroom data (full empirical study)

Ready for submission! Upload to Overleaf to get your PDF.