Seven Languages in Seven Weeks

About the book

Bruce Tate structures the book as a sequence of brief encounters with seven programming languages, each chosen to represent a distinct set of ideas. Ruby opens with object orientation and metaprogramming; Io brings prototype-based objects and message passing; Prolog introduces logic programming and declarative problem solving; Scala mixes object and functional styles on the JVM; Erlang centers on concurrency and fault tolerance; Clojure offers Lisp-style functional programming on the JVM; Haskell pushes pure functional typing furthest.

Each week divides into days, and each day pairs explanation with exercises the reader is expected to attempt. Tate treats the languages as teaching vehicles. The point is to notice assumptions carried from familiar languages and to see alternatives. Breadth of exposure matters more here than mastery of any single tool.

Tate writes for people who already program and want to widen their sense of what a language can do. The prose is direct and instructional, with code samples carrying much of the argument. Expect to type and run examples rather than read passively.

How to read it

Read with an editor and a terminal open. The exercises are the substance, and skipping them turns the book into a list of features. Give each language enough time to feel unfamiliar before judging it. The discomfort is often the lesson.

The pace is brisk by design. Some treatments are necessarily shallow, and the code reflects the language versions current when the book was written. Treat it as a map of paradigms, then consult current documentation for anything you plan to use seriously.

Who it suits

This suits programmers with experience in at least one mainstream language who want exposure to logic programming, functional styles, concurrency models and prototype-based objects. It also helps developers choosing a language for a specific problem by showing what each paradigm makes easy or awkward. Beginners still learning their first language will find the pace too fast and the comparisons less meaningful.

Reading considerations

Seven languages in roughly as many weeks means depth is sacrificed for range, and several ecosystems have moved on since the book appeared. Check that examples still run on current versions, or read for concepts and expect to adapt code. The book surveys paradigms. It does not settle which language is best for your project.