The vault · 15
The Tutorial Tradition
Before video platforms, before interactive sandboxes, a tutorial was an .asp page with a code block, a screenshot and an email address. This is the vault's reading guide to how Visual Basic was actually taught, and where that curriculum lives now.
Every VB site of the era had one, and vbdepot.com was no exception: a tutorials section at /tutorials/, an index page in classic ASP, and a submission form (eform.asp) so readers could send in their own lessons. The section was the heart of the site in a way a nav bar can never convey, because in 2000 a tutorial was the unit of transferable knowledge. You did not watch it. You copied it, pasted it into the IDE, pressed F5, and it either ran or it taught you something about typos.
01Why Visual Basic was so teachable
The language met beginners where they already were: in front of a form. A first lesson could produce a working window in ninety seconds, which is why the pedagogy of VB leaned so hard on do something visible, then explain it. The RAD workspace was not just a productivity tool; it was a teaching machine. Properties were vocabulary, events were grammar, and the running program was instant feedback in a way a console printing "hello" never quite matched for a windows audience.
Tutorials exploited this. The canonical sequence ran: drop a control on the form, wire one event, run it, add a second control, break something on purpose so the reader meets the debugger. The best authors of that generation wrote like mechanics, with an ear for what a novice would touch next.
02The canon, and where it lives now
One tutorial from the old depot survives by name in the web archive, and it is the perfect specimen: creating a simple bouncing ball application, the animation lesson half a generation of hobbyists cut their teeth on. The depot has rebuilt it, line by line, with the modern commentary the original never had room for.
The rest of the old curriculum did not vanish; it was absorbed into the magazine. This is the path we would hand a newcomer today, in the order the vault itself learned it:
- The complete history, for what the tool was and why it mattered.
- The IDE that invented RAD, because the environment was half the language.
- The bouncing ball tutorial, for the first taste of motion and timers.
- The code depot, where idioms replace exercises.
- VBA deep dive, for the dialect that outlived them all.
The archive holds the tutorials index under two names, .asp and .htm, a fingerprint of the era's slow migration from static HTML to server-scripted pages. Both now arrive at this page. The submission form that once lived beside it now points to the contact desk.
03What replaced the tutorial page
The form-first lesson plan never died; it moved. Step-by-step guides became screencasts, screencasts became interactive notebooks, and the community that once traded .frm files by email now trades repositories, a shift traced in the community guide. But the grammar of a good tutorial is unchanged since the bouncing ball: one visible goal, one new idea per step, honest handling of the error the reader is about to cause. The delivery mechanism aged; the pedagogy did not.
04Beyond the depot
Two destinations we point at when a reader asks how the modern successor of the tutorial page actually gets made, both outside our language and both better than anything we could write on the subject.
- Écrire un brief vidéo · in French, on specifying a video before filming it, which is the discipline the written tutorial used to call an outline.
- técnicas de grabación en estudio · in Spanish, on recording technique: the half of a screencast that beginners forgive least when it is done badly.
Continue through the depot
