Thread: New to programming, is C++ the way to go?

Hardware engineering as in "hardware" engineering?

Yeah, C/C++ is a great place to start. Although, this is kind of like walking into St. Peter's Basilica and asking if anyone thinks taking Jesus into thine heart is a good idea.

Seriously tho, while some of the regs around here would rather put C++ on their toast than jam, and attribute near mythical properties to it (in relation to other common languages) which it does not really have in quite those proportions, it's great and you'll love it and it's totally appropriate to your goals. IMO.

But it is "multi-paradigm" or not, it is still only one perspective on programming. Don't forget that!

Like MK27 said, you're on a C/C++ forum so most of us are going to say that's the way to go.

I learned C/C++ from reading internet tutorials when I was in high school. It definitely takes time to learn, but it can be rewarding in the end in a lot of ways. Don't limit yourself to just C/C++ either, look at other languages too. However, pick a language and learn that first, do not try to learn too many things at once.

C and C++ are two great options, I am a bit of a hobbiest however, and I must point out, that if you intend on getting low-level with hardware, a lot of chips that you will work with will NOT have a compiler, in this case, the ONLY option is using assembly code, but as a rule of thumb, the first thing written for popular chips is - you guessed it - a C or C++ compiler.

I'd recomend learning C and C++, but don't neglect assembly, also the kind of assembly used in the low level schema is not the IL used by modern operating systems, if you want to get down and dirty with a processor, then you have no other option these days (as far as IBM go) than to use DOS, FreeDos is still available, and maintained, I've seen new programs for it dated this year.

Besides C, C++ and Assembly, not much else is really even used in low-level circut building.

EDIT: It really depends on how low-level your work will take you, the futher down the hardware chain you go, the more valuable Assembly will be, for example, if you intend on just setting up networks and working with conventional IMB and Apple based machines, say like setting up hardware in an office, forget Assembly, you can acheive much more with C or C++.
But, if you are going down to the circuit level, and wanting to build tailored target specific machines, Assembly is invaluable, in fact, if you plan on designing your own chips, they will use unique pseudo-codes not found in Apple(6800 descendants) or IBM(8086 descendants), requiring you to manually plot binary values to build even a basic Assembler (Building an Assembler is the first step to making a new chip-set operational - then - using the Assembler, one typically writes a C or C++ compiler, and edits these files with a text editor (NO INTELLISENSE or any exciting features found in modern iterations of Visual Studio, more like Notepad for Console. A C compiler is much quicker and easier to write than C++, so often the C++ compiler is written in C - Linux is a good prep if you want to build your own OS, but since you said you want to work hardware, this may be incidental.) Either way, getting into hardware can be much more to learn than simple software design, preping up on a wide variety of electronics may be better then spending to much time with programming, depending on what you have planned....
Hardware Engineering is a broad topic that can cover anything from heavy duty mainframe style powerhouses through to digital watches and washing machine circuitry, not exactly sure where you want to be in years to come, and you don't have to elaborate, just pointing out that the general field of Hardware engineer has many specialist branches...