The spreadsheet and the flagged manual, which is what learning VBA at a desk actually looks like.
The direct answer to why the language persists: offices run on spreadsheets, and spreadsheets run on macros written years ago by people who have since left. Somebody has to maintain, fix and occasionally write them, and that somebody is disproportionately valuable when they are cheap. For a student, that is the entire case: a small skill in a neglected language can carry an application further than a larger one in a crowded language.
For the shape of the thing itself, VB Depot documents the history of Visual Basic from 1988 to the present, including where VBA sits inside Office, how it differs from the VB6 and VB.NET dialects, and why so much of it is still in production. That context is worth an hour, because knowing where the language came from tells you what it is for, which is the question interviewers actually ask.
Why do offices still run on macros?
Because replacing them is expensive and the alternative is rarely better for the job they do. A macro that pulls a report together every Monday is invisible, works, and is cheaper to keep than to rebuild in a newer tool. The result is an installed base that outlives fashion, which is why the language keeps appearing on job specs for finance assistants, lab administrators and operations placements.
What the interview wants is not mastery. It is a signal that you can read a macro someone else wrote, follow what it does, and make a careful change without breaking the Monday report. That is a much smaller bar than the phrase "programming experience" suggests.
How do you learn just enough VBA for a placement?
Inside Excel, on real material, in small sessions. Record a macro of something you already do by hand, then read the code it produced and change one thing about it. That loop, record, read, modify, is the fastest way in because it skips the blank-page problem. The official reference is Microsoft's own getting started with VBA pages, which are dry but accurate and free.
Time it like a revision method rather than a project: short spaced sessions across a term beat a weekend of tutorials, for the same reasons described in spaced repetition without an app. Twenty minutes every other day on a real spreadsheet builds more usable skill than a certificate course completed in a sitting.
Just enough is a real amount:
- Learn to read and modify before you learn to write from scratch.
- Record, read, change one thing: the loop that teaches VBA fastest.
- Space the sessions; a term of short practice beats a weekend of it.
The limit is honest: VBA will not get you a software job, and it is a poor first language if programming is the goal rather than a lever into a placement. Learn it for what it is, a way to be useful in an office that runs on Excel, and put the rest of your skill hours where your degree points.
The same read-the-manual habit, applied to a different kind of course, is in the practical logbook, where the record of the work is part of the work.