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”.
as a point of principle for me, I want to be correct, so if I’m not correct, I’d rather be corrected.
Couldn’t have said it better myself. It stings at first to be wrong, but once you get used to it all that remains is the joy of learning something
It is pretty wild how quickly endless hieroglyphs turn into barely hints.
My sorta boss and I started building this accounting system for our customer a few months out. We knew nothing about accounting. What’s the difference between a sales receipt and an invoice or payment? What’s the difference between the identical objects, customers and vendors? Wtf is a class… It was just a flag you can put on things. What’s the difference between a chart of accounts, journal entry, and a ledger?
I still don’t half understand the why (half of these things are combined versions of other things), but 3 months in I suddenly understood what double entry accounting was, I had heard of it in an anime but had no idea how you would do it. 6 months in and we’re brainstorming if we want to drop journal entries and just do in chart of accounts
I have zero interest in accounting (it literally gave me headaches for the first few weeks), my dad likes doing that sort of thing. I found myself explaining accounting to him the other day
How the turn tables indeed… It just creeps up on you one day
I feel this. I started a new job recently and the place I’m working at now specializes in IT for accountants, so all of my clients are some form of certified accountant. I didn’t think it was a big deal at first, since I’ve done some work for accounting firms before while working for more generalist IT support companies (who were not picky about what their clients did), but the requests I get at this place are way more in depth for accounting than at previous jobs. Sure, we get the usual requests about file permissions, password resets, etc… But the clients seem to also expect us, as IT, to know way more about accounting than I have ever known. Preparer profiles for taxes, managing the nuances of how some accounting programs interact with eachother, just crazy stuff I’ve never gotten before. The list goes on.
My co-workers tend to shrug it off, since they’ve been dealing with it for a while, but I’m frequently asking them about that stuff while thinking, are we really expected to know this?
I’m no stranger to accounting. I took business in college with my IT diploma (I actually have two college diplomas, one is for business, which includes accounting), and all of this stuff is still way over my head.
But, ask me about the nuances of instruction scheduling in a VM hypervisor and I’ll run circles around whatever you think you know about the subject… At least for most people. Routing protocols? You want a list of them? And what they do? And how they do it? I’m your man.
But show me a general ledger and I’ll know some of what I’m looking at. I don’t know enough to know if it’s “in balance” or anything, I’m just privy enough to make sense of the words and numbers, not enough to know if it’s correct, or even how to tell if it’s correct.
Luckily, my manager has pretty clearly stated that we’re IT, and we shouldn’t be expected to know things like that, but my co-workers often know more about it than I do. I have no shame or pride that I know or don’t know something, I’ll ask others all day long about it, and learn everything I can. If I can’t figure it out, I just tell the user to ask the company that made whatever software they’re referring to and that’s it.
Life is an adventure, you’re bound to get more wrong than right, the important part is how you handle those situations. IMO, that’s what defines you. I want to be known as someone who isn’t afraid to ask, isn’t afraid to be wrong, and isn’t afraid to learn something new in order to be helpful.
My least favorite response that I hear when dealing with users is that “I’m not techy” because it demonstrates a willful ignorance of the technology that they use every single day, and an unwillingness to learn that technology. I don’t expect them to learn IT, and all is nuance, because I’d be out of a job, but c’mon Deborah, this is the third time this week that your problem has been that OneDrive isn’t connected to your account. You should know to log into OneDrive when this happens. FFS.
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.
That’s imposed by the job market, not natural thing to exist. In fact, it’s very much unnatural.
I mean, maybe my first job was an outlier, but I literally mean chose to specialize. Out of the people who graduated within 5 years of me, two got into Python because of the project, and just stayed there like you said… One of them could only never have run his code before pushing commits, the other one was middle of the road.
Another went strict UI - he wasn’t unable to do other things, he got hired after a couple years and said this is what he wanted to do.
Two more started in Python, then decided they wanted to do exploit stuff, the guy ended up going back to programming after he was let go for non-work reasons, and I don’t know where he ended up… He worked for Amazon for a while.
I guess a good chunk did keep using what they’re using and happen to specialize like you say, but I saw a lot of people choose something intentionally, a few years after doing something different too. Most of the team looked for something using their existing languages or even stack when we all moved on, regardless if they picked it or fell into it
I don’t think it’s difficulty - like you say, if you’ve learned a couple high level languages, jumping to a new one is mostly syntax
Maybe it’s a comfort/effort thing? A lot of the people who chose to specialize left their work at work. Only one person I worked with was like me - several would adapt to whatever was practical without difficulty, but without a clear best opinion I always pick something new, because it makes things more fun… He was fun to work with, because the client loved him and he pitched the weirdest and most fun features
Maybe it’s just personality thing… I’m now convinced my school probably wasn’t an outlier though
![Death by PowerPoint [Work Chronicles]](https://lemmy.world/pictrs/image/4f415e52-28ad-4ac6-86ca-2947f664acb8.jpeg){kind=link}
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.
Couldn’t have said it better myself. It stings at first to be wrong, but once you get used to it all that remains is the joy of learning something
It is pretty wild how quickly endless hieroglyphs turn into barely hints.
My sorta boss and I started building this accounting system for our customer a few months out. We knew nothing about accounting. What’s the difference between a sales receipt and an invoice or payment? What’s the difference between the identical objects, customers and vendors? Wtf is a class… It was just a flag you can put on things. What’s the difference between a chart of accounts, journal entry, and a ledger?
I still don’t half understand the why (half of these things are combined versions of other things), but 3 months in I suddenly understood what double entry accounting was, I had heard of it in an anime but had no idea how you would do it. 6 months in and we’re brainstorming if we want to drop journal entries and just do in chart of accounts
I have zero interest in accounting (it literally gave me headaches for the first few weeks), my dad likes doing that sort of thing. I found myself explaining accounting to him the other day
How the turn tables indeed… It just creeps up on you one day
I feel this. I started a new job recently and the place I’m working at now specializes in IT for accountants, so all of my clients are some form of certified accountant. I didn’t think it was a big deal at first, since I’ve done some work for accounting firms before while working for more generalist IT support companies (who were not picky about what their clients did), but the requests I get at this place are way more in depth for accounting than at previous jobs. Sure, we get the usual requests about file permissions, password resets, etc… But the clients seem to also expect us, as IT, to know way more about accounting than I have ever known. Preparer profiles for taxes, managing the nuances of how some accounting programs interact with eachother, just crazy stuff I’ve never gotten before. The list goes on.
My co-workers tend to shrug it off, since they’ve been dealing with it for a while, but I’m frequently asking them about that stuff while thinking, are we really expected to know this?
I’m no stranger to accounting. I took business in college with my IT diploma (I actually have two college diplomas, one is for business, which includes accounting), and all of this stuff is still way over my head.
But, ask me about the nuances of instruction scheduling in a VM hypervisor and I’ll run circles around whatever you think you know about the subject… At least for most people. Routing protocols? You want a list of them? And what they do? And how they do it? I’m your man. But show me a general ledger and I’ll know some of what I’m looking at. I don’t know enough to know if it’s “in balance” or anything, I’m just privy enough to make sense of the words and numbers, not enough to know if it’s correct, or even how to tell if it’s correct.
Luckily, my manager has pretty clearly stated that we’re IT, and we shouldn’t be expected to know things like that, but my co-workers often know more about it than I do. I have no shame or pride that I know or don’t know something, I’ll ask others all day long about it, and learn everything I can. If I can’t figure it out, I just tell the user to ask the company that made whatever software they’re referring to and that’s it.
Life is an adventure, you’re bound to get more wrong than right, the important part is how you handle those situations. IMO, that’s what defines you. I want to be known as someone who isn’t afraid to ask, isn’t afraid to be wrong, and isn’t afraid to learn something new in order to be helpful.
My least favorite response that I hear when dealing with users is that “I’m not techy” because it demonstrates a willful ignorance of the technology that they use every single day, and an unwillingness to learn that technology. I don’t expect them to learn IT, and all is nuance, because I’d be out of a job, but c’mon Deborah, this is the third time this week that your problem has been that OneDrive isn’t connected to your account. You should know to log into OneDrive when this happens. FFS.
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.
That’s imposed by the job market, not natural thing to exist. In fact, it’s very much unnatural.
I mean, maybe my first job was an outlier, but I literally mean chose to specialize. Out of the people who graduated within 5 years of me, two got into Python because of the project, and just stayed there like you said… One of them could only never have run his code before pushing commits, the other one was middle of the road.
Another went strict UI - he wasn’t unable to do other things, he got hired after a couple years and said this is what he wanted to do.
Two more started in Python, then decided they wanted to do exploit stuff, the guy ended up going back to programming after he was let go for non-work reasons, and I don’t know where he ended up… He worked for Amazon for a while.
I guess a good chunk did keep using what they’re using and happen to specialize like you say, but I saw a lot of people choose something intentionally, a few years after doing something different too. Most of the team looked for something using their existing languages or even stack when we all moved on, regardless if they picked it or fell into it
I don’t think it’s difficulty - like you say, if you’ve learned a couple high level languages, jumping to a new one is mostly syntax
Maybe it’s a comfort/effort thing? A lot of the people who chose to specialize left their work at work. Only one person I worked with was like me - several would adapt to whatever was practical without difficulty, but without a clear best opinion I always pick something new, because it makes things more fun… He was fun to work with, because the client loved him and he pitched the weirdest and most fun features
Maybe it’s just personality thing… I’m now convinced my school probably wasn’t an outlier though
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.