By low level, I mean like kernel work. I’m told he worked on one of the 'nixes way back when.
It was a data structures class, we did Java or Python in the into classes, php & js for Web + db basics and C++ for theory classes. Then you pick your path
Anyways, the guy taught OS, language design, and data structures. He could code fine, he was just a terrible lecturer - extremely disorganized, no lesson plans. He only wasted the one full class forgetting why we were there, but reading his code (labeled by week) then scribbling on the whiteboard was his lecture
I guess I ended up understanding data structures and I never fell asleep, so maybe he wasn’t a bad teacher. It was just mostly just assignments, he didn’t really do quizzes and the final wasn’t much of the grade
I’d call that hardware - if you’re code enough to the metal to be writing machine code (or even assembly), the physical architecture of the hardware is part of your code
Low level generally is one step up - manual access to memory, compiling to an architecture rather than a virtualization layer, etc
Strangely, the guy that taught OO theory did our hardware class, we built bit shifters and wrote programs in risc assembly… And ONE program in machine code with the promise we’d never have to do it again
I could understand someone who writes in assembly, but machine code is a nightmare…I think I got it without any mistakes, but my butthole was clenched for 4 hours, terrified I’d have to debug it
Nah, you’ve got the concepts down, I always try to drip feed this kind of information to people when it comes up.
It’s a lot - it takes years to absorb all of it even with a degree in it, and new concepts are always spreading. Gently correcting and being corrected is the only way
It’s part of the methodology my brother passed to me when I was learning - using the same terms as everyone else is critical, because if you can describe it correctly you can search it
And if your understandings don’t line up, you have to iron out the differences or you’ll waste time talking past each other
Knowing there is a difference between assembly and machine code isn’t something most people know, are you technical or interested in programming?
I work in IT. I don’t have much use for knowing the difference, but as a point of principle for me, I want to be correct, so if I’m not correct, I’d rather be corrected.
So I appreciate it.
Also the fact that there’s a lot to know, phew, you said it brother (or sister? Idk, doesn’t matter). IT is a minefield of information on all kinds of things. I used to get overwhelmed by spec sheets, now I look at them and think “there isn’t enough information here”.
Why data structures weren’t in C/C++? It would make sense to care about structures, cache locality, SoA/AoS, indirections and stuff in some language that compiles in native code.
Ah, I phrased that ambiguously - it was in C++, all of our computing theory type classes were.
I just got distracted realizing I graduated proficient in 9 languages and reasonably comfortable in another 3. 2 were from internships, but the rest were all from coursework. The last couple years, I was juggling 2-4 at all times, plus the odd scripts
I always thought I was really good at picking up and switching languages, but I just realized my program was designed that way.
That feels like a lot, do other colleges do something similar?
(I guess you could knock off 3 because we ended up switching every semester in software engineering because cross platform apps were pretty bad at the time)
My undergrad officially required Pascal, C, C++, Java, PHP, Prolog, Lisp, x86 and MIPS assembly. You couldn’t work around those. There was also Tiger, VHDL, and Bash that were required, but you would probably not count as languages. (I’m certainly forgetting some stuff too.)
There was a virtual certainty you’d need some more languages, but not everybody would need the same ones.
Damn… That list sounds terrifying. I’m working on a legacy code base in VB (although I finally have time to try out this c# converter to start the slow march out of depreciation), and 8 months later I still feel gross with VB. I’m pretty sure VB is uniquely horrible because of the inconsistency. .
I’ve heard good things about pascal and lisp… But lisp syntax also makes me irrationally uncomfortable
I did prolog as well in an elective, that was a weird and interesting language. It’s not very practical, but it was fun. Plus graph theory is one of the weird maths that pops up everywhere, maybe one day I’ll find an excuse to try to use it for something
So it sounds like you had even more than me, I’m now wondering why even my relatively young co-workers all seemed to specialize so hard straight out of school
What did you end up working in? Did you specialize, or keep up with the language juggling?
Picking up languages is quite easy, you just have to learn it. Turns out nowadays I mostly work with SQL (it’s on the required list too, I just forgot about it) and C#. Learning new paradigms is harder, but there aren’t that many of those.
I’m now wondering why even my relatively young co-workers all seemed to specialize so hard straight out of school
That’s imposed by the job market, not natural thing to exist. In fact, it’s very much unnatural.
![Death by PowerPoint [Work Chronicles]](https://lemmy.world/pictrs/image/4f415e52-28ad-4ac6-86ca-2947f664acb8.jpeg){kind=link}
So what was the lesson supposed to be about?
“sometimes it’s okay to skip class”
Semaphores. It was obviously C++ code with a bunch of threads, but as it was a standalone C++ program it wasn’t really clear why it was lol
By low level guys, you mean he knew about circuits and EE? But he got stuck teaching a C++ class but he couldn’t code?
By low level, I mean like kernel work. I’m told he worked on one of the 'nixes way back when.
It was a data structures class, we did Java or Python in the into classes, php & js for Web + db basics and C++ for theory classes. Then you pick your path
Anyways, the guy taught OS, language design, and data structures. He could code fine, he was just a terrible lecturer - extremely disorganized, no lesson plans. He only wasted the one full class forgetting why we were there, but reading his code (labeled by week) then scribbling on the whiteboard was his lecture
I guess I ended up understanding data structures and I never fell asleep, so maybe he wasn’t a bad teacher. It was just mostly just assignments, he didn’t really do quizzes and the final wasn’t much of the grade
I was thinking that you meant like, machine code, by “low level” and yeah. C wouldn’t make a lot of sense to someone who handles machine code.
I’d call that hardware - if you’re code enough to the metal to be writing machine code (or even assembly), the physical architecture of the hardware is part of your code
Low level generally is one step up - manual access to memory, compiling to an architecture rather than a virtualization layer, etc
Strangely, the guy that taught OO theory did our hardware class, we built bit shifters and wrote programs in risc assembly… And ONE program in machine code with the promise we’d never have to do it again
I could understand someone who writes in assembly, but machine code is a nightmare…I think I got it without any mistakes, but my butthole was clenched for 4 hours, terrified I’d have to debug it
Right. That’s my bad. I’m not a programmer or developer, so I conflate machine code and assembly far too frequently.
Nah, you’ve got the concepts down, I always try to drip feed this kind of information to people when it comes up.
It’s a lot - it takes years to absorb all of it even with a degree in it, and new concepts are always spreading. Gently correcting and being corrected is the only way
It’s part of the methodology my brother passed to me when I was learning - using the same terms as everyone else is critical, because if you can describe it correctly you can search it
And if your understandings don’t line up, you have to iron out the differences or you’ll waste time talking past each other
Knowing there is a difference between assembly and machine code isn’t something most people know, are you technical or interested in programming?
I work in IT. I don’t have much use for knowing the difference, but as a point of principle for me, I want to be correct, so if I’m not correct, I’d rather be corrected.
So I appreciate it.
Also the fact that there’s a lot to know, phew, you said it brother (or sister? Idk, doesn’t matter). IT is a minefield of information on all kinds of things. I used to get overwhelmed by spec sheets, now I look at them and think “there isn’t enough information here”.
How the turn tables.
Why data structures weren’t in C/C++? It would make sense to care about structures, cache locality, SoA/AoS, indirections and stuff in some language that compiles in native code.
Ah, I phrased that ambiguously - it was in C++, all of our computing theory type classes were.
I just got distracted realizing I graduated proficient in 9 languages and reasonably comfortable in another 3. 2 were from internships, but the rest were all from coursework. The last couple years, I was juggling 2-4 at all times, plus the odd scripts
I always thought I was really good at picking up and switching languages, but I just realized my program was designed that way.
That feels like a lot, do other colleges do something similar?
(I guess you could knock off 3 because we ended up switching every semester in software engineering because cross platform apps were pretty bad at the time)
Once you are in the industry long enough, you won’t even remember how many different languages you have worked with.
A good education and experience should get you to the point where you are comfortable picking up and using any language, even if it is new to you.
My undergrad officially required Pascal, C, C++, Java, PHP, Prolog, Lisp, x86 and MIPS assembly. You couldn’t work around those. There was also Tiger, VHDL, and Bash that were required, but you would probably not count as languages. (I’m certainly forgetting some stuff too.)
There was a virtual certainty you’d need some more languages, but not everybody would need the same ones.
Damn… That list sounds terrifying. I’m working on a legacy code base in VB (although I finally have time to try out this c# converter to start the slow march out of depreciation), and 8 months later I still feel gross with VB. I’m pretty sure VB is uniquely horrible because of the inconsistency. .
I’ve heard good things about pascal and lisp… But lisp syntax also makes me irrationally uncomfortable
I did prolog as well in an elective, that was a weird and interesting language. It’s not very practical, but it was fun. Plus graph theory is one of the weird maths that pops up everywhere, maybe one day I’ll find an excuse to try to use it for something
So it sounds like you had even more than me, I’m now wondering why even my relatively young co-workers all seemed to specialize so hard straight out of school
What did you end up working in? Did you specialize, or keep up with the language juggling?
Picking up languages is quite easy, you just have to learn it. Turns out nowadays I mostly work with SQL (it’s on the required list too, I just forgot about it) and C#. Learning new paradigms is harder, but there aren’t that many of those.
That’s imposed by the job market, not natural thing to exist. In fact, it’s very much unnatural.
Oh no, synchronization primitives!
Well, you can end up implementing synchronization primitive if you are writing game. Sometimes game engine is kernel in userspace.
I’ve done it in a Python system at work before. We used a mutex?(The int, not the lockout) to track worker threads
It’s a hell of a lot easier these days… It’s amazing how quickly programming advances when you look back
I’m interested in how this came up in a game engine though, and how recent it was