/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

The Perils of JavaSchools

Lazy kids.  —  Whatever happened to hard work?  —  A sure sign of my descent into senility is bitchin' and moanin' about "kids these days," and how they won't or can't do anything hard any more.  —  When I was a kid, I learned to program on punched cards.

joelonsoftware.com Joel Spolsky

Context & Ripple Effects

Joel Spolsky's essay lands two weeks after Business Week asked whether Java had become 'so nineties', giving the language's cultural moment a second front: not just whether Java is fashionable, but whether teaching it exclusively is hollowing out computer science education. His argument — that schools which teach only Java dodge difficult material and graduate weaker programmers — echoes his own origin story learning on punched cards, framed as a generational complaint about kids who won't do anything hard.

The piece traveled quickly for a blog post, picked up same-day by a Microsoft-affiliated geek blogger under the blunt headline 'Joel says teaching Java is bad for CS students,' signaling that the JavaSchools critique had an audience well beyond Spolsky's own readership.

First-order effects

  • CS departments teaching a single-language Java curriculum face renewed criticism from an influential industry voice that their graduates lack the hard foundations — recursion, memory, low-level mechanics — that employers and grad programs screen for.

Second-order effects

  • Students choosing programs now have a public rubric for distinguishing rigorous curricula from vocational ones, putting competitive pressure on universities to defend or diversify what they teach beyond Java.

Third-order effects

  • If the pattern holds, computer science education splits into a two-tier market — language-training programs feeding industry demand versus fundamentals-first programs feeding research and systems work — with each new popular language reigniting the same fight.

The trend: The recurring cycle of 'kids these days' programming debates — punched cards then, AI coding assistants later — keeps returning to one question: whether CS education should chase industry languages or insist on hard fundamentals.