The Missing Semester of Your CS Education – Revised for 2026

Original Article ↗ Hacker News Discussion ↗

Version Control & Git Education

  • Many welcome the strong version-control chapter, arguing good commit history and use of tools like bisect/blame/rebase dramatically improve debugging and collaboration.
  • Others note most developers learn only minimal git workflow at work or “by necessity”, leading to poor histories and cargo-cult usage (delete/re-clone when confused).
  • Disagreement over responsibility: some say widespread misuse means git is badly designed (unintuitive, jargon-heavy, poor “undo”); others see it as a powerful tool that simply requires training, like a bandsaw or a Bloomberg terminal.
  • Alternatives (Mercurial, jj, GUI frontends, git aliases/scripts) are praised as higher-level or friendlier interfaces over git’s “assembly-like” CLI.
  • There’s debate over whether clean commits should matter in corporate settings where the PR (often squash-merged) is the real unit of work.

Scope and Value of the “Missing Semester”

  • Many consider this kind of course one of the most useful in their education, solving day-to-day blockers (shell, git, tooling) that fundamentals don’t address.
  • Some report similar 1-credit or UNIX-tools courses at their universities and say they still rely on those notes. Others note departments often wanted but weren’t allowed to teach such “non-academic” skills.
  • Suggested additions:
    • Practical IT skills: information management, backups, self-hosting basic services, basic troubleshooting.
    • Tools: sed/awk, shell mastery, scripting, statistics/data tools (Polars/Plotly), LaTeX/org/R/Quarto, touch typing.
    • Software topics: testing/QA (possibly its own course), deeper software quality (complexity, maintainability, modularity).
    • “Beyond code”: interaction with OSS communities, interviewing, salary negotiation, team leadership, communication with management, career progression, and personal hygiene.

AI, Agentic Coding & CS Degrees

  • Course authors explicitly ask about including AI topics. Some commenters support this and want more, e.g., a “build your own agent” lecture as high-leverage practice.
  • Others see “agentic coding” as hype that doesn’t deserve space, suggesting the course should focus on understanding systems, not operating AI tools.
  • Broader debate: is CS education still worthwhile when AI can write code?
    • One side: for people viewing CS purely as vocational “coding”, maybe less so.
    • Counterarguments: CS is distinct from coding; LLMs excel at recombining known patterns but struggle with novel formulations and poorly documented domains; human insight remains essential.
    • Concerns that many will become low-paid “LLM operators” vs higher-value software engineers.

Comments, Ethics & Soft Skills

  • The “Beyond the Code” section on comments is appreciated; guidance that comments explain “why” rather than restating “what” resonates.
  • Discussion around TODOs: they often rot unless tied to tickets or tagged with initials to preserve intent.
  • Some are surprised ethics isn’t more central as a “missing semester” topic, though others question how much a short course can shift moral compasses.