AI summary by TwinMind
We Need To Stop Lying About Git
Theo - t3․gg
18m 15s
Initial Controversial Statement
- Tweet about CS graduates not knowing basic git commands being "astounding"
- Expected lukewarm reception but generated significant backlash
- Audience poll: 1 (not spicy), 2 (spicy), 3 (should be canceled) - mostly 1s with sarcastic 3s
Personal Git Experience & Context
- Started using git before learning to code for Minecraft server file management
- Only had one incident in 15-year career where deleted uncommitted code
- Witnessed classmates' fear when deleting code without version control
- School friends asking "what's a commit?" when code was deleted
CS Degree Purpose Clarification
- CS degrees exist primarily for programming jobs (95% of graduates)
- Only alternatives: coding jobs or research/education
- Degrees existing solely for academia are "perpetually self-fulfilling prophecy"
- Universities market CS degrees for coding job preparation
- Personal experience at RPI: engineering school but CS in science department
- Required bio instead of circuits due to science major classification
University Git Exposure Examples
- RPI had awesome open source program requiring git usage
- Taught many students git, witnessed terrible practices
- One student insisted on UI-only git usage:
- Coded algorithms in Python
- Added random numbers to filenames
- Drag-and-dropped files to GitHub via web interface
- This behavior described as "begrudgingly dragging heels" rather than using git
Curriculum Integration Suggestions
- Not advocating dedicated git courses or semester-long classes
- Proposed solution: require git for homework submission
- Custom git server at school
- Two-page PDF instruction
- No git submission = failing grade
- Make it prerequisite for completing assignments
- Doesn't take long to learn enough git for solo school environment
Hiring Standards Position
- No developer should be hired without basic git knowledge
- Would accept SVN knowledge as compromise if candidate willing to learn git quickly
- Version management understanding essential after 4 years of software writing
- Analogy: equivalent to not knowing IDEs, only using notepad
- Acceptable: using Sublime instead of VS Code (tool preference)
- Unacceptable: no version control knowledge whatsoever
Version Control as Core Concept
- Version control should be "1,000%" familiar by job-seeking time
- Not about specific git technology but version control concept
- Git currently most justifiable version control to learn
- Students should feel "insecure and embarrassed" if they don't know git
- "Unacceptable to write software for years and not know how version control works"
Industry Reality Check
- Git is "literal underpinning" of 99% of serious software development
- Essential for collaborative work
- CS graduates not knowing git indicates:
- No desire to learn beyond curriculum
- Couldn't be bothered researching industry requirements
- Should be barrier to hiring
- Engineers typically learned git 10+ years ago, not discussed in hiring
Hacker News Controversy
- Tweet front-paged on Hacker News for entire day
- Generated significant pushback and debate
Common Counterarguments Addressed
- "CS degrees teach general knowledge, not specific skills"
- Response: Version control is fundamental, not a fad
- "Git is just a tool, not a discipline"
- Response: Basic tools should be known (file system navigation analogy)
- "Git isn't even 20 years old"
- Response: Current students are 20 or younger, git is older than them
- Mechanic analogy: mechanic not knowing hammer usage is unacceptable
Technology Adoption Comparison
- Elementary/middle schools using Google Docs for 10+ years
- Universities still not using git in curriculum
- Question: Why more willing to adopt proprietary software than universally used open source?
Gen Z Technology Gap
- Many use phones/iPads more than computers
- Chromebook usage common
- Many don't know file system navigation
- File management and git knowledge both essential
Industry Examples & Exceptions
- Facebook uses Mercurial (rare exception)
- Most companies use some form of version control
- Almost all use git specifically
- Any codebase without VCS is "almost ideological"
Educational System Critique
- Software engineering classes focused on theory (UML, SOLID, DRY, KISS, Agile, Scrum)
- Mostly "waste of time" with no practical programming
- Missing practical tools education
Hiring Manager Perspective
- Looking for people good at learning and self-improvement
- 4 years of coding without learning git indicates poor learning initiative
- Diverse interests should naturally lead to discovering tools and ecosystems
- 99% of programming paths lead to git exposure
Current Job Market Reality
- New graduates competing with laid-off experienced developers
- Experienced developers definitely know git
- Need to appear close to "industry veteran" level
- Choice between hiring laid-off Facebook employees (know Mercurial + git) vs fresh graduate with no version control proof
- Obvious hiring decision favors experienced candidates
Historical Context
- Year 2000: expensive industry tools, open source alternatives used
- Today: open source IS the industry standard
- No excuse for not learning standard tools
Final Position
- Git not about being "better engineer" but baseline requirement
- Same necessity as having IDE for writing code
- Need VCS for managing code after writing
- 99% use git, so just use git
- Described as fundamental baseline, not advanced skill
