Learning C before C++ is underrated.

Reply to this note

Please Login to reply.

Discussion

Learning c before any high level language is underrated. If you don't understand how high-level quality of life features like objects, namespaces, generics, polymorphism, garbage collection etc are helping you, then neither do you understand how they are shooting you in the foot.

I say this as one who could stand to learn c.

Yeah, you don't really understand computers until you've spent some time with C.

...And performing integer and floating point arithmetic on paper, building a register machine, and trying some Assembly.

(I'll see myself out, now...)

Punch cards...

I've actually worked with those, before, because my dad was using them to keep me busy, while he finished in the server room. πŸ˜‚ He was using the big magnetic tapes, for important stuff.

I barely remember it, tho. Must have been in 4th grade, or something.

I think that's why I immediately "got" register machines.

Dang you go way back.

I have an older coworker who had to work with punch cards in college.

Meanwhile the "worst" I had to do is write a C++ project in vim.

I'm actually missing about 10 years, right in the middle, when my kids were young. So, I sometimes seem weirdly clueless to younger devs, and I cover it up by pretending I'm _actually_ clueless.

Too long; didn't explain.

You have the principles down, which is most important.

It's also a strategic advantage to claim to know nothing, but understand most things. You can avoid the work, but still constructively critique. πŸ˜‚

Me: Oh, this is so hard and who understands computers, gosh, thank you, I'll make you a sammich, you must be so smart! 🀩

Them: Okay, here, you go! What do you think?

Me:

I'll take the sammich though πŸ˜†

I do make awesome sammiches.

It's crazy that I'd sit in there and do my homework. πŸ˜‚

The guards would just wave me past.

I had to always wait for him, for a ride. I would go to the library and get books πŸ“š to read, on the way to his office. That's why I read so many books and why I don't mind my husband hacking away, all the time. Grew up with it. Can entertain myself, indefinitely, even just with whatever is going on in my own head.

Yes, jumping into C++ is absurd πŸ˜‚

This is my coding path

1) C

2) C++

3) Rust

4) HTML, CSS, JS

5) Python

Mine is

1) QBasic on MS-DOS

2) Fortran and Cobol on mainframe

3) HTML and CSS

4) Java

5) C#

6) PHP

7) C

8) Java again

9) SAS/R

10) Python

Guys are saying I need to learn C++ and Typescript, but I'm just winging it, so far.

Taking an online JavaScript course for work, since they use Cypress.

TypeScript is JavaScript playing dress up. Sure it uses types, but I can dump those at a moment's notice.

I guess my order has been:

1) C++

2) Racket

3) Java

4) Python

5) JS/TS

6) C#

I've dabbled in others, but not enough to be worth mentioning.

I must have missed the Racket Era. πŸ˜‚

That must be right after the PowerBuilder Era.

Maybe? It's also a toy language, derived from Lisp, for learning purposes. I don't think anyone uses it for realz.

PowerBuilder was very pointy-clicky. Lots of finance/insurance apps with Oracle behind it.

Was it one of those drag and drop UI things that turns layouts into code?

I guess PL/SQL is in there, someplace, too. Near PHP.

I think before PHP because it was Oracle and the PHP was usually MySQL.

Learning bash scripting, now, to take over someone else's stuff, and I hate it. πŸ™ˆ Unreadable gobbledygook.

This could be us, bro, but you make me maintain a 200-line bash script, bro. 😭

I took one look at it, and was like, yeah this all gonna be rewritten in Python. πŸ˜‚

We're actually relatively similar. Seems like most people start with Python or JavaScript, now, and their stuff is often bizarrely buggy and inefficient.

The high level is far easier to get into than low level machine code

But that's where the electrons flow

Hah I cracked a book on C++ and it said the two are different enough it's worth learning C++ independently of C, and that C devs going to C++ can carry over some habits that don't work well in object-oriented C++ world.

It's sorta true, but C++ devs hardly ever go back and learn C.

The book is also written by the creator of C++, so he has a bias 🀣

Wait, what’s C++ ?

Newfangled stuff. It'll never catch on.