ArticleslgStudy

computer science

Programmers at Work

Programmers at Work is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Programmers at Work rather than just read about it. In short: Programmers at Work is a collection of technical interviews with nineteen prominent software developers from the early personal computer era. The interviews, published by Microsoft Press in 1986, were designed to capture the personalities and driving forces behind the development of innovative algorithms, computer systems, application software, and video games, while also exploring larger topics such as ethics and t…

Programmers at Work — main illustration
Programmers at Work — illustration

Key takeaways

  • Programmers at Work belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Programmers at Work to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Programmers at Work from memory before moving on to harder problems.

Reference excerpt

Programmers at Work is a collection of technical interviews with nineteen prominent software developers from the early personal computer era. The interviews, published by Microsoft Press in 1986, were designed to capture the personalities and driving forces behind the development of innovative algorithms, computer systems, application software, and video games, while also exploring larger topics such as ethics and the future of computing. The book focuses primarily on the achievements software developers were able to accomplish within the limits of 16-bit computing architectures, including the IBM Personal Computer and Apple Macintosh. The in-person interviews were conducted by the book’s author and editor, Susan Lammers. Lammers was an early Microsoft employee who became Editor-in-Chief of Microsoft Press in the mid-1980s. The original collection of interviews was published on June 26, 1986. In 2026, a 40th anniversary edition of the book was released by 8080 Books and Simon & Schuster with a new preface by Lammers. The 2026 edition seeks to demonstrate how the lessons learned from early programmers are still relevant today, especially in topics related to software design, computer architecture, and creativity.

Contents

Introduction Programmers at Work features an introduction written by Lammers in which she establishes her main goals in creating the collection. She discusses computer programming culture and timeless design and engineering issues that are sometimes neglected in the tech industry. One of the goals of the presentation is to inspire and educate younger programmers. Lammers also claims her motivation was to stay as much in the background as possible during the interviews, letting the personality and ideas of the programmers take center stage. Each chapter of the book features a short biography of the programmer and a comprehensive interview. Hand-drawn images of the interviewees are also featured in each chapter. Interviewees include:

Charles Simonyi, Microsoft software architect and originator of Microsoft Word Butler Lampson, computer scientist and fellow of the ACM John Warnock, early Xerox PARC employee and co-founder of Adobe Systems, Inc. Gary Kildall, creator of the CP/M operating system Bill Gates, creator of Altair 8800 BASIC and co-founder of Microsoft John Page, early Hewlett-Packard employee and creator of PFS:FILE database Wayne Ratliff, programmer and designer of Vulcan database and dBASE Dan Bricklin, co-designer of VisiCalc spreadsheet Bob Frankston, co-designer of VisiCalc and contributor to Lotus 1-2-3 spreadsheet Jonathan Sachs, co-founder of Lotus Development Corporation and originator of Lotus 1-2-3 spreadsheet Ray Ozzie, contributor to PLATO (University of Illinois) and designer of Lotus Notes Peter Roizen, T/Maker spreadsheet co-founder and software developer Robert Carr, architect of GO Corporation's PenPoint operating system Jef Raskin, visual arts professor and originator of the Macintosh project at Apple Andy Hertzfeld, software engineer on original Macintosh project at Apple Toru Iwatani, video game designer and creator of the arcade game Pac-Man Scott Kim, visual designer and calligrapher; author of the book Inversions Jaron Lanier, computer scientist, futurist, and composer Michael Hawley, academic and artist working in the field of digital media

Glossary The glossary section of the book features technical terms that arose during the interviews, allowing readers to explore evolving terminology as it took shape in the 1980s. The resources in this section make the book accessible to a wide range of readers and may be useful for historians of technology. Example: “Boolean Algebra: A system of logic functions named after George Boole that uses operators such as AND, OR, NOT, EXCEPT, IF, and, THEN to derive the solution of logical problems in which each element can be one of two states, usually true or false."

Appendix The appendix features supporting technical materials for twelve of the interviews. These include handwritten diagrams, source code, and supplemental images that document how each developer approached their work, including early stages of the design process. Notable examples include Bill Gates' handwritten notes from 1975 for his implementation of BASIC for the MITS Altair microcomputer.

Reception In 1986, Erik Sandberg-Diment of The New York Times wrote that Programmers at Work did for budding software writers what the Paris Review interviews did for would-be fiction writers in the 1950s and 60s. It provided comfort, inspiration, and a sense of community between readers and creators who were establishing new products. Wired editor Steven Levy cited the interviews as useful source material to capture the creativity of Xerox PARC during the early days of computing. Academic researchers also used Programmers at Work to study visual imagery during the software development process, including the mental models that programmers sometimes use to conceptualize data or hardware architecture.

Citations

Worked examples

Example 1 — a first encounter with Programmers at Work

Start with the simplest possible case. Write down what Programmers at Work claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Programmers at Work before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Programmers at Work ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Programmers at Work

In research
Programmers at Work appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Programmers at Work in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Programmers at Work is common in secondary-school and first-year university syllabi. It links to neighbouring topics 1986 non-fiction books, Computer programming books, History of computing, so understanding it makes those chapters shorter.
In everyday life
Look for Programmers at Work outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Programmers at Work in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Programmers at Work means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Programmers at Work out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Programmers at Work in simple terms?

Programmers at Work is a collection of technical interviews with nineteen prominent software developers from the early personal computer era. The interviews, published by Microsoft Press in 1986, were designed to capture the personalities and driving forces behind the development of innovative algo…

Why does Programmers at Work matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Programmers at Work?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Programmers at Work.

Tags

  • 1986 non-fiction books
  • Computer programming books
  • History of computing
  • Interviews
  • Microsoft Press books

Keep exploring