You should get into the habit of VCS / GitHub so it's easier by the time they get it released.

When I was a kid, you went to the doctor, he took a minute to catch up on your chart and then gave you about ten to fifteen minutes of attention which included looking in your eyes, ears and throat, listening to your lungs and tapping your back and maybe doing a reflex test on your knee while listening to your current complaint, if there was one.  Did he spend thirty minutes typing into a computer a lot of irrelevant information like they do today? Has any doctor looked in your ears recently?

With GitHub, am I more like the doctor of old, or like the ones today that can't seem to diagnose anything without a dozen hands-off tests? In other words, will I be fixing problems or documenting every "i" I dotted and every "t" I crossed meanwhile getting very little done?

Here's one for Alex. Say I'm a developer that has a release of his software. There may be a lot of changes made to the various access objects, and VBA code for the next release. Would GitHub (or VCS?) help other developers that have the first version get their .accdb up to date with the newer version being released? They would be making their own changes to the objects and VBA code while development is being done on the core application. Make sense?

Yeah, that's the point of the tool.
You'd make a feature branch, make your changes, raise an MR to put it back into the main app.
Someone would review it then it would get merged.
(You could then upload a version of the accdb as a Release in GitHub if you wanted)

The add-in has an option to build from source, so you can take the files and compile them into an accdb.

But to your question it depends what you mean.
If they need the db to develop against they would just pull the latest changes from the main and make their own branch and make changes to that.
See https://docs.github.com/en/get-started/using-github/github-flow

This really doesn't relate to Access though, it's more around how you develop any application so it might be good to take a step back and get your head around the underlying process and reasons for doing it this way, then apply it to a couple of hobby projects, maybe even a simple website to compare/contrast.

@Alex Thanks for that information. Can you provide some links, in order, that would take one from "zero to hero" with this tool (if the above link isn't meant to do that)? Assume they don't know anything about Github.

My videos:
git Beginner Level 1

Microsoft Learn
GitHub Foundations Part 1 of 2
https://learn.microsoft.com/en-us/training/paths/github-foundations/
GitHub Foundations Part 2 of 2
https://learn.microsoft.com/en-us/training/paths/github-foundations-2/

Introduction to Git
https://learn.microsoft.com/en-us/training/modules/intro-to-git/

@ Alex Grins!