Yes, you’re going to be doing some C++ programming. There are a ton of videos that help get your feet wet, or just get the basics up and running (example here). For convenience, here is a quick link to a YouTube search.
As Kris stated, there are a lot of benefits with GAS, even if you don’t intend to fully utilize all the features it has to offer. What I’ve seen some do, is get the desired MVP (minimum viable product) features of their project going, and then identify if moving those into a framework such as GAS would be beneficial. If not, don’t do it. Simple as that.
I’ve seen shipped projects that included a huge library of assets, because the team didn’t sit down and identify what they did or didn’t need, and instead just sent the whole pack out (in this example, 2 field grass assets were used, ~9mb of data… they shipped a whole forest pack instead of culling unused assets, ~1.2gb).
Moral of the story? You know what you need or what you don’t. If you can’t identify those items, you need to research and learn what does what and why. It’s a boring part of development, but unless you want to get stuck in a loop of throwing mud at the wall and never getting better, it’s a necessary skill to obtain. Unless you’re the person with the clipboard. Then just tell some other poor sap to handle audits!