re: What’s something that should be obvious that developers seem to misunderstand? VIEW POST

FULL DISCUSSION
 

I'd say this is vaguely related, but ever time I hear from a friend that they're taking a college/uni course that is literally just learning a language, I just sigh on the inside. My college had every course represented as a skillset you were learning, not a language/tool.

For example, even the most introductory CS course was structured as an intro to programming concepts (and not just "learning Python"), and the next level up was an intro to object-oriented development (and not just "learning Java"). I could maybe see the appeal in courses being linked to tools if the tool represents a whole ecosystem or something, but just having an "Intro to C++" course makes no sense to me, yet I see it everywhere.

On an even-more tangential note, C++ should never be a first language, and yet I see that everywhere too.

 

I took Intro C++ as my first academic dive into programming and it almost ruined me lol

 

When I started my studies in CS, all our courses were meant to teach us concepts, paradigms, sometimes they would even involve an obscure language to force us to use a certain concept as there was no other way around.

At first I hated it, I wanted to build things, learn to make software and applications and all I was doing was some exercices. Now, with a step back I really appreciate what I learned and understand why the courses were built that way and I use it as a strength, I can easily switch tools and languages, all I need is to learn the syntax and the specificities.

I think it really depends on what you want, learning that way can kill your motivation but if you overcome it you will end up with a great adaptability.

code of conduct - report abuse