CompCode Academy

Lesson 60 of 65 · Free to read

Day 60 ΓÇö The economics and governance of AI coding

Month 3 · Week 12 — Small Language Models & AI Automation with n8n 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: Claude, GPT, Gemini, Ollama

Overview

Economics and governance of AI coding: model routing, prompt caching, budgets, IP/ownership, review gates, and a written playbook.

Learning objectives

By the end of this session, you can:

  • Explain the core ideas behind: The economics and governance of AI coding: model routing (LLM vs. SLM), prompt caching, per-engineer spend budgets, and team adoption — IP/ownership, review gates, and a written playbook.
  • Apply the ideas using Claude, GPT, Gemini, Ollama 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

Playbook contents

Approved tools, spend guidelines, review gates, data handling, exception process.

Cost experiments

Same task across models including an SLM; record quality vs cost.

Tooling for today

Primary tools: Claude, GPT, Gemini, Ollama. 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
From Vibe Coding to Agentic Engineering (Karpathy × Sequoia) — Why vibe coding raises the floor — and engineering raises the ceiling.

Course video

Open on YouTube
God-Tier Developer Roadmap — Career framing and skill sequencing.

Worked example / case study

Scenario

Cost/quality comparison; draft one-page AI-assisted development playbook for a real team.

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): Claude, GPT, Gemini, Ollama.
  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: The economics and governance of AI coding: model routing (LLM vs. SLM), prompt caching, per-engineer spend budgets, and team adoption — IP/ownership, review gates, and a written playbook.
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. Run one task across several models (incl. an SLM), compare quality vs. cost, then draft a one-page “AI-assisted development playbook” with spend guidelines and review gates for a real team.

Coaching notes

Include a monthly budget example.

Steps

  1. Set up or open the workspace required by: Claude, GPT, Gemini, Ollama.
  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
The economics and governance of AI coding: model routing (LLM vs. SLM), prompt caching, per-engineer spend budgets, and team adoption — IP/ownership, review gates, and a written playbook.

## Context files
- (list paths)

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

## Definition of done
- Run one task across several models (incl. an SLM), compare quality vs. cost, then draft a one-page “AI-assisted development playbook” with spend guidelines and review gates for a real team.

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

  • Playbooks that ban tools people already use (shadow IT)
  • No budget owner
  • Ignoring IP/licensing clauses

Key takeaways

  • Governance enables adoption
  • Budgets need owners
  • Write it down
  • Tools (Claude, GPT, Gemini, Ollama) change; the judgment skills transfer.

Resources

  • Official docs for: Claude, GPT, Gemini, Ollama
  • 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 60 of 65.

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