CompCode Academy

Lesson 3 of 65 · Free to read

Day 3 ΓÇö Developer environment setup

Month 1 · Week 1 — Mental Models & Environment Setup Audience: Final-year students & early-career engineers (0–3 years) Format: Self-paced study + optional live clinic · Suggested time: 4–6 focused hours Key tools: VS Code, Git, GitHub

Overview

Before Copilot or Cursor can help, you need a boring, reliable environment: editor, git, runtime, and the ability to clone/run a repo. Most “AI isn’t working” issues are actually path, node version, or git permission issues.

Learning objectives

By the end of this session, you can:

  • Explain the core ideas behind: Developer environment setup: VS Code, Git & GitHub, Node.js, Python, terminal fundamentals.
  • Apply the ideas using VS Code, Git, GitHub on a realistic task (capstone, internship, or first-job style)
  • Produce the exercise deliverable with clear success criteria
  • Identify common failure modes and how to recover
  • Capture at least one reusable prompt, rule, or checklist for your personal library
  • Decide what must remain human-reviewed for this class of work

Core concepts

Minimum viable toolchain

VS Code (or Cursor later), Git + GitHub auth, Node LTS and/or Python, terminal comfort (cd, ls/dir, env vars). Learn to read error messages before pasting them into chat — you’ll ask better questions.

First commit hygiene

Small commits with clear messages beat giant “WIP” dumps. AI can draft commit messages; you still own the content.

Tooling for today

Primary tools: VS Code, Git, GitHub. Prefer official docs when APIs change. When a model invents a symbol, verify against source or docs immediately.

Practice posture

You are a final-year or early-career engineer pairing with a very fast teammate (the model): clear intent, grounded context, inspect consequential changes, keep a paper trail (commits, prompts, decisions).

Process diagram

Watch & learn

Study these free videos before or during the exercise. Each embed is chosen to reinforce today's objectives.

Course video

Open on YouTube
Git and GitHub for Beginners (freeCodeCamp) — Commit, branch, push — the baseline every AI workflow needs.

Course video

Open on YouTube
AI-driven Development for Programmers (Fireship) — Fast tour of AI coding workflows developers actually use.

Worked example / case study

Scenario

Create a GitHub repo, push a README, clone a starter, run it, screenshot the running app.

Step-by-step

  1. Clarify the outcome in one sentence tied to the exercise below.
  2. Gather grounding context (files, docs, schema, acceptance checks).
  3. Run the primary tool(s): VS Code, Git, GitHub.
  4. Produce the smallest vertical slice that proves the idea.
  5. Verify with a command, test, screenshot, or side-by-side comparison.
  6. Write down one steering note — what you told the AI when it went wrong.

Sample prompt you can adapt

Role: Senior engineer mentoring an early-career developer (pairing with me).
Task: Developer environment setup: VS Code, Git & GitHub, Node.js, Python, terminal fundamentals.
Context: Final-year / early-career project (capstone, internship, or junior role).
Constraints:
- Match existing project patterns
- No new dependencies unless justified
- Include tests or a verification checklist
- Call out assumptions explicitly
Output: step plan first, then code/files, then verification commands.

Hands-on exercise

Primary task. Configure VS Code, create a GitHub repo, make your first commit and push. Clone a provided starter repo and run it locally.

Coaching notes

Checklist: editor extensions (ESLint/Prettier), git user.name/email, SSH or HTTPS auth tested.

Steps

  1. Set up or open the workspace required by: VS Code, Git, GitHub.
  2. Skim today's core concepts and watch the video(s) before prompting.
  3. Execute the task in small commits (or saved artifacts if no-code).
  4. Fill the success checklist below.
  5. Note one surprise and one process improvement for tomorrow.

Success criteria

  • Deliverable matches the exercise description
  • You can explain every AI-generated change in plain language
  • Verification ran (tests, manual check, or published URL)
  • At least one pitfall from this lesson was consciously avoided
  • Artifact saved (repo commit, doc, or published link)

Timebox

Suggested: 90–150 minutes of focused build time after study.

Templates & checklists

AssetPurpose
Prompt stubReuse today's structure (role → task → constraints → format)
Verification checklistTests / manual QA / security skim
Decision logWhat you delegated vs kept human

Copy-paste prompt skeleton

## Goal
Developer environment setup: VS Code, Git & GitHub, Node.js, Python, terminal fundamentals.

## Context files
- (list paths)

## Constraints
- Stack: (fill)
- Do not: (secrets, drive-by refactors)

## Definition of done
- Configure VS Code, create a GitHub repo, make your first commit and push. Clone a provided starter repo and run it locally.

Daily reflection (3 minutes)

  • What did AI do well?
  • Where did it confidently fail?
  • What rule will you add to your cookbook/rules file?

Common pitfalls

  • Installing every VS Code extension on day one
  • Committing node_modules or .env
  • Skipping 'run the starter' before asking AI to change it

Key takeaways

  • Environment reliability multiplies AI usefulness
  • Git is your undo button for agent mistakes
  • Always prove 'it runs' before 'make it better'
  • Tools (VS Code, Git, GitHub) change; the judgment skills transfer.

Resources

  • Official docs for: VS Code, Git, GitHub
  • Course cookbook: keep prompts in a versioned Markdown file in your repo
  • Prior days this week — skim objectives if you skipped ahead

Self-paced lesson — Mastering AI-Assisted Development & Vibe Coding — Day 3 of 65.

New free lessons and course updates. Unsubscribe from any email.