Should You Seriously Learn VBA?

Question

Microsoft

Hello!
Recently I did a little work on VBA (Visual Basic for Application) where I needed to convert excell file data. The process of writing a small application that processes data easily and quickly seemed very interesting and promising to me. But since I'm not very versed in these technologies, I decided to ask professionals questions:
1) Is studying vba promising in the context of data processing (excel, doc)?
2) I heard that microsoft is going to use .net #C instead of vba, is that true?
3) If I still master vba, will I be able to find a good job at least in freelancing?
Sincerely ,
Almik

Answer 1

Depends on what you do/want to do.
If you work in the field of finance: as a financial analyst, controller, accompanied by a business - VBA is a must have, as it is very popular in this area. And for more or less serious advancement, you just need to know this language.
If your path is programming, then look the other way.

Answer 2

If I understand correctly, you are in search of your own path)) Therefore, my answer will be a little off-topic.
As for VBA, my opinion is that it is not very promising and really cool projects are not developed on it.
I am a web developer myself, and in fact what you did can be done in PHP, for example, in C #, the same can be done in many other languages. I recommend that you think more globally and don't stop at doc and excel processing.

Answer 3

You should only study VBA purposefully if you are serious about something in MSO, mainly in Excel\Access, and really feel the need for it.
It is not necessary to master it as a "profession", it is better to take something more serious.
If you need to automate / write some function / smoothen the interface in the MSO environment, you, knowing any other programming language and having google, can relatively easily and quickly solve any problem in VBA, maybe not as elegantly as a person who devoted a lot of time to learning VBA, but it will work.

Answer 4

Not worth it, stupid waste of time. If you want to engage in support in the future, and not development, then yes, otherwise no.