What Joel Spolsky Learned About Real Problems, In‑House Programming, and Leadership

University: The Most Useful Course

Spolsky cites a single Dynamic Logic class that changed his career direction. The professor proved a theorem about a program f := not f that leaves f unchanged after an even number of executions; the proof took hours and the homework asked to prove the converse. Spolsky spent weeks on the assignment and concluded that spending effort on trivial logical puzzles is unproductive—software should solve real problems. He also mentions a demanding CS323 course with extensive programming assignments (≈40 hours per week). Completing the work revealed his passion for coding, while students who disliked the workload realized programming was not for them, helping avoid future career mismatches.

Days at Viacom

After Microsoft, Spolsky worked as an in‑house programmer at Viacom. He found the role painful for three reasons:

Cost‑driven companies force developers to use only mature, conservative technologies, limiting experimentation.

Projects are considered finished once they run; there is little incentive to improve code quality, unlike in product‑focused tech firms where better software drives success.

IT programmers are treated as maintenance staff with little path to management, whereas in technology companies engineers can rise to executive roles.

He advises choosing companies whose core business aligns with one’s technical expertise rather than merely accepting a technical title.

Management’s Role

At Juno, an early internet email service, management followed a top‑down model: non‑technical leaders dictated product direction without understanding technical details. Spolsky contrasts this with the Silicon Valley approach, where managers create an environment that removes obstacles and lets talented engineers focus on building high‑quality products. He concludes that effective management should “move the furniture” and provide space for skilled developers to produce first‑class software.

Importance of Communication

Spolsky emphasizes that clear, compelling expression distinguishes ordinary staff from leaders. A demanding writing professor taught him to convey complex ideas simply, a skill that later helped his blog attract a large audience and contributed to the early success of his startup, Fog Creek Software.

Key Conclusions

Prioritize solving real, meaningful problems over trivial, time‑consuming puzzles.

Select employers whose business domain matches your technical background.

Good management should eliminate obstacles and empower engineers to create high‑quality products.

Strong communication ability is a decisive factor between a regular employee and a leader.