Pre-Semester Project: Foundation Setup Portfolio

Required Output Classification

Required output	Classification	Public/private guidance
Runnable project implementation and repository structure	Portfolio candidate	Polish the public repo only after tests pass, secrets are removed, and setup steps work from a clean checkout.
README with setup, inspection, verification instructions, and known limitations	Portfolio candidate	Make this public-facing if the project is safe to share; keep internal coursework notes in a private evidence folder.
Tests, traces, proofs, diagrams, benchmark outputs, or review notes required by the brief	Checkpoint evidence	Keep raw logs, benchmark runs, and reviewer comments private by default; publish summarized or reproducible versions when useful.
ADRs, design memos, runbooks, benchmark reports, and other high-effort engineering writeups	Portfolio candidate	These are worth polishing publicly when they tell a clear tradeoff story; otherwise keep them as private coursework evidence.
Final reflection, retrospective, or carry-forward notes	Checkpoint evidence	Keep candid self-assessment private unless rewritten as a concise public learning note.

Duration: Throughout Pre-Semester (3 weeks)
Deliverable: Complete foundation setup demonstrating study system mastery, development environment proficiency, and Git workflow competency

Project Overview

The Pre-Semester project integrates study systems, development environment mastery, and Git fundamentals into a unified foundation portfolio. This project proves you're ready for the intensive 96-week degree program by establishing sustainable systems and professional tooling.

Project Components

Component 1: Study System Implementation and Tracking (Module 1 Integration)

Weight: 40% of project grade

Implement and demonstrate a complete study system based on Atomic Habits principles:

Study Habit Implementation:

• Daily study routine tracked for 21 consecutive days (full 3 weeks)
• Environment design with dedicated study space and tool organization
• Tracking system documenting consistency, focus quality, and learning retention
• Recovery protocols for when study habits are disrupted

Documentation Requirements:

• Habit loop analysis: Document cue, craving, response, reward for your study habit
• Environment audit: Before/after photos and descriptions of study space optimization
• Progress tracking: Daily logs showing study time, focus quality (1-10), and learning outcomes
• Reflection essays: Weekly 1-page reflections on habit formation progress and challenges

Assessment Criteria:

• Demonstrated 21-day consistency in study habit execution
• Clear evidence of environment design supporting study behavior
• Systematic tracking with honest assessment of progress and setbacks
• Evidence-based reflection on what works and what needs improvement

Component 2: Development Environment Mastery (Module 2 Integration)

Weight: 30% of project grade

Build and document a complete, reproducible development environment:

Environment Configuration:

• Shell setup with custom configuration, aliases, and productivity enhancements
• Editor proficiency demonstrating efficient text editing and programming support
• Command-line fluency completing complex tasks faster than GUI equivalents
• Automation scripts for common development and maintenance tasks

Documentation Requirements:

• Dotfiles repository with comprehensive configuration files and setup documentation
• Setup automation allowing reproduction of environment on new machines
• Efficiency analysis: Before/after timing for common tasks (file operations, text editing, project navigation)
• Tool mastery portfolio: Screenshots or recordings demonstrating proficiency with key tools

Assessment Criteria:

• Complete, working development environment that supports programming and technical work
• Documented setup process allowing environment reproduction
• Demonstrated efficiency improvement in development tasks
• Professional-quality dotfiles organization and documentation

Component 3: Git Workflow and Collaboration Portfolio (Module 3 Integration)

Weight: 30% of project grade

Demonstrate Git proficiency through actual repository work and collaboration:

Repository Portfolio:

• Personal learning repository with proper organization, documentation, and commit discipline
• Collaborative project simulation showing branch workflow, pull requests, and conflict resolution
• Contribution to existing project (documentation improvement, small fix, or enhancement)
• Professional repository presentation suitable for portfolio and technical interviews

Technical Demonstration:

• Git workflow fluency: Branching, merging, rebasing, and advanced operations without reference consultation
• Collaboration skills: Code review participation, constructive feedback, and professional communication
• Recovery techniques: Demonstration of fixing Git mistakes and repository problems
• Integration with development environment: Seamless Git usage within command-line workflow

Assessment Criteria:

• Professional-quality repositories with clear documentation and organized commit history
• Evidence of successful collaboration and code review participation
• Demonstrated ability to resolve complex Git scenarios independently
• Integration of version control into daily development workflow

Integration Requirements

The portfolio must demonstrate connections across all three modules:

Required Cross-Module Integration:

1. Study Systems + Dev Environment: Use command-line tools efficiently within established study routines
2. Dev Environment + Git: Integrate Git operations seamlessly into command-line workflow
3. Study Systems + Git: Use Git to organize and track learning artifacts and progress
4. All Three Modules: Maintain consistent quality across study habits, tool usage, and version control practices

Timeline and Milestones

Week 1: Foundation Establishment

• Study system design and initial implementation with environment optimization
• Basic development environment setup with shell and editor configuration
• Git repository initialization for learning portfolio and dotfiles management
• Daily habit tracking begins with systematic documentation

Week 2: System Integration and Refinement

• Study system refinement based on first week's experience and challenges
• Advanced development environment configuration with automation and productivity enhancements
• Git workflow development with branching practice and collaboration simulation
• Integration testing ensuring all systems work together effectively

Week 3: Portfolio Completion and Assessment Preparation

• Complete documentation of all systems with setup instructions and lessons learned
• Collaboration demonstration through code review and contribution activities
• Efficiency assessment documenting improvement in study and development task completion
• Portfolio presentation preparation for Semester 0 readiness verification

Assessment Rubric

Excellent (90-100%)

• Sustainable study habits demonstrated through consistent execution and thoughtful adaptation
• Professional development environment with comprehensive documentation and automation
• Fluent Git workflow with evidence of collaboration and advanced technique mastery
• Exceptional integration showing synergy between study systems, tools, and version control
• Portfolio quality suitable for professional presentation and technical interviews

Proficient (80-89%)

• Solid study habits with minor inconsistencies but overall successful implementation
• Functional development environment with good documentation and basic automation
• Competent Git usage with evidence of learning and improvement over time
• Good integration between different foundation components
• Clear portfolio presentation demonstrating readiness for advanced coursework

Developing (70-79%)

• Basic study habits established but may need reinforcement for sustainability
• Working development environment but limited customization or documentation
• Functional Git usage for basic operations but limited advanced technique demonstration
• Limited integration between foundation components
• Acceptable portfolio meeting minimum requirements but lacking polish

Incomplete (Below 70%)

• Inconsistent study habits without evidence of sustainable system establishment
• Incomplete development environment setup or major functionality gaps
• Basic Git operations only without workflow development or collaboration evidence
• No meaningful integration between different foundation areas
• Portfolio insufficient for demonstrating readiness for intensive academic program

Submission Requirements

Documentation Portfolio

1. Study System Documentation: Daily logs, weekly reflections, habit analysis, and environment design
2. Development Environment Guide: Dotfiles repository, setup automation, and efficiency analysis
3. Git Portfolio: Repository collection, collaboration evidence, and workflow documentation
4. Integration Analysis: 2-page essay connecting all foundation components and explaining their synergy

Technical Demonstration

1. Environment setup video (5 minutes): Demonstrate setting up development environment from scratch using your automation
2. Git workflow demonstration (10 minutes): Show complex Git operations and collaboration techniques
3. Study system walkthrough (5 minutes): Explain and demonstrate your study routine and tracking system

Readiness Assessment

1. Self-assessment questionnaire: Honest evaluation of competency across all foundation areas
2. Peer review session: Work with another learner to review and validate each other's foundation setup
3. Forward planning: Document how these foundations will support Semester 0 and beyond

Success Metrics

Quantitative Indicators

• Study consistency: 21/21 days of study habit execution (or documented recovery from disruptions)
• Environment efficiency: 50%+ improvement in common development task completion times
• Git proficiency: Successful completion of advanced Git scenarios without external help
• Integration quality: All foundation components working together seamlessly

Qualitative Indicators

• Sustainable systems: Study habits and workflows that can handle increasing academic demands
• Professional competency: Development environment and Git practices suitable for collaborative work
• Meta-cognitive awareness: Clear understanding of your own learning process and what works best
• Readiness for intensity: Confidence in your ability to handle 20 hours/week of technical study

Support Resources

Technical Setup

• Missing Semester resources: Official exercises, video walkthroughs, community discussion
• Pro Git book: Comprehensive Git reference and advanced technique coverage
• Development environment examples: Dotfiles galleries and professional configuration templates

Community and Collaboration

• Study groups: Connect with other learners following similar foundation-building approaches
• Online communities: Command-line users, Git communities, academic study groups
• Mentorship: Seek advice from experienced developers on professional tool usage and workflow optimization

Academic Integration

• Learning science resources: Additional material on habit formation, spaced repetition, and effective study
• Productivity resources: Time management, focus techniques, and sustainable learning practices
• Career preparation: Professional development practices and portfolio building guidance

This Pre-Semester project validates that your foundation systems can support the intensive 96-week degree program ahead while establishing the professional practices essential for collaborative engineering work.

---

Production-Style Project Brief

Use this project as a reviewable engineering brief, not only a completion exercise.

Problem statement

Write a one-paragraph statement covering the user, the problem, the constraint, and the outcome this project is meant to produce.

Required evidence

• working artifact or reproducible deliverable
• README with setup, inspection, and verification instructions
• tests, traces, proofs, diagrams, benchmark output, or review notes appropriate to the semester
• decision log with at least three meaningful tradeoffs
• known limitations section with explicit scope cuts

Review questions

1. What is the smallest vertical slice that proves the project works?
2. Which requirement is most likely to be misunderstood by a reviewer?
3. What did you deliberately not build, and why?
4. What evidence would convince someone else that the result is correct?

Done means

The project is done only when another technical reader can inspect the artifact, run or review the verification evidence, and understand the tradeoffs without a live explanation.

---

Weekly Project Milestones

Use these milestones to keep the project from becoming a last-week scramble.

Milestone	Focus	Evidence
Start	Scope the smallest useful slice	problem statement, non-goals, first task list
Early build	Produce a walking version	runnable skeleton, first test, first committed artifact
Middle	Add the hard part	implementation note, trace/proof/benchmark/design decision
Review	Stress the weak point	failure case, debugging note, peer/self review, correction commit
Finish	Package for inspection	README, verification instructions, known limitations, reflection

Answer-Quality Examples

Quality	What it sounds like
Weak	"I built it because the module asked for it."
Acceptable	"It works for the required examples and I can explain the main idea."
Strong	"Here is the tradeoff I chose, the evidence that supports it, and the case where it would fail."
Portfolio-ready	"A reviewer can inspect the artifact, rerun the checks, and understand why this solution fits this semester's goals."

Future Capstone Connection

Before closing this project, write two sentences on how it could help the final capstone: one reusable technical skill and one artifact habit to preserve.

Calibration Materials

Use these learner-visible calibration materials before self-grading or requesting review:

• Answer key and solution outlines
• Rubric, passing standard, strong traits, and weak patterns