The history series · 02: People
Alan Cooper and the Making of Thunder
Visual Basic began as one man's attempt to let people design a shell without programming. Microsoft called the result a shell construction set; the industry ended up calling him the father of Visual Basic.
01The problem Cooper kept bumping into
Alan Cooper entered the 1980s as a working software developer, and the thing he kept noticing was not technical at all. It was that the people with the best ideas about software, the store managers, the editors, the accountants, were exactly the people locked out of building it. Every idea had to be translated through someone who knew a compiler, a translation that lost most of its meaning on the way. Cooper's response, developed through the late eighties in the Bay Area, was a tool called Tripod: a way to construct the shell of a program, its windows, its buttons, its behaviour, visually, by manipulating interface elements directly instead of describing them in code.
Tripod was not a BASIC product. It was not, strictly speaking, a language product at all. It was an argument: that interface design and programming were different jobs, and the first one should not require the second.
02The demo
The story Cooper told for decades (and the one repeated in histories of the industry) is that in 1988 he demonstrated Tripod to Bill Gates, and that Gates grasped instantly what he was looking at, reportedly calling it "a shell construction set". Whatever the exact wording, the outcome is not disputed: Microsoft acquired the technology and brought Cooper in to work on what would become, under the internal code name Thunder, the product the world met in 1991 as Visual Basic 1.0.
Inside the project, Cooper's visual construction system was known as Ruby: a name that long predates the famous programming language and occasionally causes double takes in retrospective accounts. Microsoft's contribution was to bolt Ruby onto the BASIC heritage the company already owned from QuickBASIC, giving the visual shell a language engine everyone half-knew from their school micros. The pairing was obvious in hindsight and radical at the time: a drawing program that emitted working software.
"Visual Basic was not a language with a designer bolted on. It was a designer with a language bolted on, and that ordering changed everything."
03Father of Visual Basic
Cooper worked at Microsoft on the Thunder project in its formative period, and the industry title that stuck to him afterwards: "the father of Visual Basic", is one he wore with visible ambivalence. He was present at the creation of the form designer, the Toolbox and the property-driven model of interaction that shipped in VB 1.0 and that this depot dissects in The IDE That Invented RAD. The language underneath, the packaging, the corporate strategy (those were Redmond's. The insight that ordinary users could be trusted to design interfaces) that was Cooper's, and it is the insight the entire product line was built on.
The fuller version-by-version story of what Microsoft did with that insight is told in The Complete History of Visual Basic.
04Second act: the critic of software itself
Cooper's second career may be the more influential one. After leaving Microsoft he turned his frustration with badly designed software into a body of writing that effectively founded software interaction design as a practice. About Face: The Essentials of User Interface Design (1995) became the standard text of the field. The Inmates Are Running the Asylum (1999) gave the industry its most quotable diagnosis: that programmers, left to design for themselves, build software that behaves like a computer rather than like a person.
Through his design consultancy, Cooper and his colleagues also popularised the persona, the fictional, concrete user a design team builds for, which remains one of the most widely used (and most widely misused) tools in product development. There is a pleasant irony the depot never tires of: the man whose tool let millions of non-programmers build software spent the rest of his career insisting that software be built for non-programmers.
Cooper consistently credited the Visual Basic team at large for the shipped product: the language work, the database layers, the tooling of versions 2 through 6. "Father of" is a headline word, not an org chart. The tool's long corporate life is documented across our VB6 deep dive and the timeline.
05Why the story still matters
Every few years the industry rediscovers Cooper's original argument under a new name (no-code, low-code, citizen development) usually without noticing that the first working version shipped in 1991. The lesson of Thunder is double-edged. Yes, the abstraction was a triumph: drag, drop, double-click, ship. And yes, the abstraction leaked: whole categories of software were built by people one abstraction layer away from understanding their own tools, a tension still visible today in everything from spreadsheet macros to visual website builders. The depot's position is that both halves are true, which is precisely what makes it a story worth keeping.
Continue through the depot
