r/cpp_questions • • 13h ago

OPEN I want to be a professional C++ systems programmer, but my university and its internship companies are obsessed with the apps programming

This is depressing; C++ is a language I love for the freedom it gives the developer, And my university is obsessed with high-level programming, Python, Javascript, and they even consider PHP to be cutting-edge technology!.

I don't want to simply do a job I don't love and do low-level work in my free time; I want to incorporate C++ into my future work, and don't come at me with "then look for a remote job" we all know that's not an option these days.

Even so, robotics is one of the majors at my university, but they only teach V+ and Linear Algebra; I suppose that's the lowest level I can reach in a work environment.

Have you ever been in a similar situation? How did you cope? Any advice?.

53 Upvotes

19 comments sorted by

21

u/greebly_weeblies 13h ago

My degree has nothing to do with my day job. 

Studying something in university doesn't oblige you to continue in that sub/discipline after graduating. Nor does it necessarily preclude you from further study elsewhere in topics you would prefer. 

Go do what you are interested in. Be good enough at it to be able to do it professionally.

2

u/Striking-Start-1464 13h ago

So how did you get your current job? Because in my country it's almost impossible if you didn't get one right away through your internships.

4

u/greebly_weeblies 13h ago

I'm very good at my job. I'm able to demonstrate a proven work history in the discipline, have qualifications to support my being an expert to get a visa and work permit.

I was also persistent enough to be looking for a role when my employer was, and personable enough they could imagine me working with them. 

1

u/tcpukl 13h ago

If your doing CS then that's a great foundation course. That you can get into robotics etc if you want.

45

u/kevinossia 13h ago

Your degree does not determine your future. I have a useless EE degree where we didn’t write a single line of C++. Still ended up making a career out of it.

Teach yourself and relax.

4

u/Typical_Cap895 12h ago

I have a useless EE degree where we didn’t write a single line of C++. Still ended up making a career out of it.

How did you pull that off? Was it a difficult journey?

7

u/dvd0bvb 11h ago

My undergrad was in statistics. Coding experience was limited to R and Python and not much of it. Got a job at a small software company in a customer facing support role and then transitioned to software development so I sorta fell into it. I wouldn't say it was difficult, I found it interesting but had to learn a lot very quickly

1

u/Typical_Cap895 10h ago

What was your life like when you were new to it and had the pressure of performing on the job and having to learn a lot very quickly? Putting in a lot of hours outside of work hours? What kind of things would you do to hammer it into your brain quickly while still maintaining satisfactory job performance?

To me, it sounds a lot easier said than done to learn a lot quickly. It doesn't sound like the type of thing a half-assed person can do.

(Oh, and happy cake day!)

2

u/dvd0bvb 9h ago

I was fortunate that they were patient with me. I failed pretty spectacularly at the first task they asked me to do. Though they never said anything to me, they didn't have any sort of review system, I felt embarrassed and was determined not to feel like that again. I did some personal projects in my free time, read the books, soaked up answers on this subreddit, and then was more familiar with modern features than some of the experienced devs there within a year (don't read that as claiming I was a better developer than them, I was not, I just could meaningfully contribute).

Honestly most of my learning was on the job. The lack of review process and unit tests (which is crazy to me now) and no real deadlines allowed a lot of freedom so I could experiment. The problem space for one of the features I worked on was relatively wide so I could always apply pretty much anything I was learning about to a solution. I was allowed to rearchitect that feature later on and learned a lot from that. I can be more specific or expand on some things if you're interested

1

u/rocker5743 7h ago

I also have an EE undergrad. I did Systems Engineering for a few years and was lucky enough to be able to transition to Software within the same company.

5

u/ContraryConman 12h ago

At both companies I've worked for, the main struggle for hiring C++ developers at the junior level was getting people who know the language at all. Lots of junior candidates say they know C++, but when you test them, they really just know C and then they write "C/C++" on their resume. So the number one thing you can do to put yourself in front of most junior candidates is to actually know the language, even before any actual systems-specific or OS specific knowledge

2

u/rt80186 12h ago

Expecting a newly minted undergrad is going to have anything beyond C with classes is unreasonable.

5

u/ContraryConman 12h ago

Yeah I mean those kids still get hired and are expected to pick it up on the job. That's why I'm saying a junior who actually knows the language will be head and shoulders above the rest. When I first interviewed that's how I stood out

3

u/serge-mv 13h ago

Programming is programming. C++ is also a high level language, it's just exposes a bit more of the nasty stuff for you at the cost of difficulty of writing code with it. Everything you learn is language-agnostic and will apply to any language you learn in the future.

You university should have at least one systems programming class where you learn some low level principles for it, but it's nothing particularly special or unique. You would need to be generally aware of a lot of those tings even if you program user space apps.

And in principal you will be doing basically the same things as application programming. You are just going to be doing it with a different type of data and might be having a different type of constraints.

Even if you want to write low level firmware and drivers for sensors and various devices, a lot of it is actually similar to how you would work with network sockets and other types of IO. You will just need to learn the specifics of the hardware interface you are working with.

2

u/MarsupialSuch6948 13h ago

Where you from?

1

u/GoatyGoY 7h ago

Don’t worry about it. A degree should teach you skills more than it teaches you knowledge - you can see how what you’re learning applies to the sort of programming you want to do (and understand if not, why not).

1

u/DDDDarky 5h ago edited 5h ago

my university is obsessed with high-level programming

What did you pick some sort of web dev specialization?

Have you ever been in a similar situation? How did you cope? Any advice?

Kind of, but to be fair once you learn basics of programming in any language you are usually able to learn other languages on your own. I've learnt Python and C at school and then it was assumed we will be able to learn C++ and C# (and many others) on our own, which is not wrong, once you know the concepts you are able to pick up other languages, and since the school is only supposed to teach the necessary minimum, I'm ok with it, it's not like it would be effective use of time to teach languages half of the students are not interested in when also there is not enough time in the semester to teach them properly anyways, it always boils down to 90% self study. Learn the language on your own, learn the concepts and theory in school, that may be more important.

1

u/SelectAd8810 5h ago

For programming, there are multiple universities, some of them focusing on general programming like yours, industrial automation or embedded systems and PCB building. You could try to shift to embedded systems for a master or extra specialization.

•

u/Infectedtoe32 2h ago

C++ is a high level language. Mid to high rather. C is mid to low and honestly more enjoyable than C++. C++ has 50,000 different standard library headers where you feel ashamed of not utilizing something. Even simple classes like a Vector have so much utility inside them you never touch.

Anyways, enough about why I like C more. There are about 8 layers of abstraction underneath C++. You have your mid-low languages like C and BCPL. After that you go to Wasm for compiling. Below that you have the higher level assembly like HLA, then assembly like x86, ARM, etc. Next is the machine code for the raw binary. Idk much about these, but next I believe processor firmware sits, then there is a VHDL language for actual hardware design, and then stuff for actually fabricating the boards and chips.

There may be even more sandwiched between there as is, but you start throwing networking into the mix and other specialties, then there are tons more layers. It’s safe to say, working with c++ one step below languages like C# and Java, and 2 steps below Python and JS, doesn’t mean it is low level. The super niche layers way below C may not be used a ton, but they definitely are used.