Configuring the Developer Environment
Every InnoDI candidate works in a standardized local and cloud software engineering environment. Before beginning Semester 1 (CORE-501–CORE-505), configure Visual Studio Code, Python 3.11+, and Node.js LTS.
1. Visual Studio Code
Install Visual Studio Code with the official Python, Jupyter, ESLint, and GitLens extensions for reproducible laboratory work.
2. Runtime Verification
Verify python --version (≥ 3.11), node --version (LTS), and git --version in your terminal.
Git & GitHub Repository Workflow
All studio and laboratory deliverables at InnoDI are version-controlled via Git to maintain an auditable commit trail for faculty evaluation.
git config --global user.name "Your Full Name" git config --global user.email "innodi@sounny.com"
- Fork & Clone: Fork the official assignment repository and clone it locally.
- Incremental Commits: Commit each analytical step with clear messages documenting your reasoning.
- Verification: Submit your repository commit hash in the LMS for
gradeAssistpre-screening and faculty review.
Cohort Collaboration & Technical Support
Asynchronous mastery does not mean isolation. InnoDI cohorts coordinate studio critiques, code reviews, and technical troubleshooting through structured channels.
#general
Official Rectorate notices, colloquia, and semester milestones.
#tech-support
Post reproducible stack traces, environment errors, and lab questions.
#studio-critique
Peer and faculty feedback on spatial, UX, and AI prototypes.