I was lucky, in about 1980 my father had an option to hire another member of staff for his small (6 people) electrical design company, or buy a computer. He bought the computer. It was a Hewlett Packard HP-85 using Basic as an operating system. I started programming on that at age 8, and then on the others we bought after he convinced the main customer to start using them too. In 1984 or so we got our first IBM PC, an XT that sucked compared to the HP, but we persevered with it.
After we added PLC (factory machine) control to the electrical design, I quit school at 14 to code full time, DBase 3, VBasic scada systems and PLC program, which is similiar enough in some ways to Assembler that I moved to some PC assembler stuff. After that, its all the same regardless of language or machine, just get the book to learn the nuances.
I was lucky because by about 1992 everyone wanted coders but there were few about with over 10 years experience, so wages were high. These days I quit coding, burned out on it. Instead of cut holes in brass
A good knowledge of coding is a definite asset even in this world overpopulated by computer geeks. Get a language down solid and you should find learning another is pretty easy. I would say learning something to a high depth, and having continual reasons to learn is more important than which language. The thing I saw that kills people learning to code is them sitting in front of a computer with no reason to write something. Whatever interests you, make sure you have the drive and enjoyment to make whatever it is (programs, apps, websites, etc) to as high a standard as possible. Like CodyEatsWorld, I look at his work and see a guy that pushes himself to make what he produces as sharp as possible. Have a reason to code every day and you can't help but get good in time.
You can focus on visual stuff, file and data handling, maths stuff, core or operating system stuff, networking, hardware device control, Object oriented stuff, or a bucket of other areas, but a good working knowledge of all those things will help immensely. Once you know the core to a good level, there isn't an incredible difference between running database queries for oil rig design, running telemetry systems for formula 1 teams, controlling robots to make car engines, making pet food, writing quests for MMOs, or making animated graphics. (yes I did all these things at some point
)
Good luck with it