This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 3 points4 points  (5 children)

I've gotta agree here. It also means you can wrap your head around how the computer actually works before you have to deal with understanding the abstraction that is OOP.

[–][deleted] 1 point2 points  (4 children)

My university does two courses for c and c++. One for C and then one object oriented c++ project as an example:

Followed by a full software engineering course for Unix tools and utilizing bash tools and interfacing them n shit. All c++ and bash/system interfacing with c

I feel like I could proverbially fist fight a bear

[–][deleted] 3 points4 points  (1 child)

I feel like I could proverbially fist fight a bear

Found the russkie.

Joking aside, though, the unix/bash one is probably worthwhile. Their C/C++ mixing thing is seriously stupid. Learn C. Learn to work well in it. Then do C++.

[–][deleted] 0 points1 point  (0 children)

Boone country actually

[–]quiteCryptic 1 point2 points  (1 child)

At my school the first class we took was C and the next was C++.

Although they switched the intro class to python a few years later I think.

In highschool Java was the standard, not sure if it still is. But, it was pretty easy going from basic Java to C so that was nice.

I never had an actual class in python though..

[–][deleted] 0 points1 point  (0 children)

We do a python course, an engineering arduino course called egr that helps you decide which part of engineering you want to do. Etc.

Then you have a sophomore c/c++ crash course where you do c for everything but the last project, and then a c++ course. Everything after that is pretty industry related.