Joel Spolsky on Stack Overflow, Inclusion, and How He Broke IT Recruiting (2018)

Current status and legacy

• Commenters note his blog has gone quiet; others report he is active elsewhere and involved with a “Block Protocol” effort.
• His historical hiring advice is seen as hugely influential; some think it modestly improved things, others believe it helped create today’s dysfunctional interview culture.

Internships, probation, and contract-to-hire

• Many engage with the idea of “apprenticeship/internship-style” hiring with easier initial filters and evaluation during real work.
• Supporters: works well for new grads, career switchers, and people re-entering the workforce; internships as a “farm team” can diversify the pipeline.
• Skeptics: risky for people with existing jobs, families, health insurance, or visas; 10h/week “contract to evaluate” is seen by some as a paid interview with little company commitment.
• Longer contract-to-hire (3–6 months full time) is common but criticized for attracting only desperate candidates and encouraging churn.
• Some emphasize fair pay for interns; others note widespread abuse of unpaid or underpaid internships.

Firing, probation, and risk allocation

• Several argue most industries simply hire and fire based on performance and that tech’s fear of firing drives overly selective hiring.
• Others highlight legal and reputational risk, poor onboarding, and weak management as reasons firing is rare, especially at large firms.
• There is concern that deliberate over-hiring with planned firings is costly, legally fraught, and ethically dubious.

Interview practices and filters

• Debate over online tests, take-home assignments, and live coding:
  • Pro: simple coding screens (FizzBuzz-level) efficiently weed out clearly unqualified applicants, especially when there are hundreds per role.
  • Con: tests are time-consuming, feel disrespectful, and are easy to game with LLMs; heavy processes mimic big-tech for roles that don’t warrant it.
• Some suggest crude résumé-based filters or even random selection might be no worse than current elaborate pipelines.

Stack Overflow culture

• Several describe SO as toxic, rule-heavy, and unwelcoming to casual or beginner users.
• Others say efforts to fix this overstated the problem and alienated the core contributors; tension exists between being a strict reference archive vs. a conversational help forum.

Inclusion and gender balance

• Comments note declining female participation in programming but criticize vague statements that don’t propose concrete remedies.
• Academia-adjacent experiences cited: women report harassment and feeling pushed out, suggesting factors beyond pure preference.
• Others mention research on differing interests (“things vs. people”) and nature–nurture ambiguity; consensus is that causes are multifactorial and hard to untangle.

Systemic responsibility

• Some argue no single person “broke” hiring; algorithmic thinking, imitation of large firms, and broader systemic incentives would have produced similar outcomes.
• Others maintain that widely read hiring guides and blog culture amplified specific practices (live coding, “no B players”) with real human costs for experienced developers.