What was the point of UML diagrams, anyway

@vaporeon_ so software engineers have something to learn while getting their master's degree

@wallhackio ... I learned lots of worthwhile things in my studies that aren't UML diagrams

Such as [in basic terms] how CPU works, how Ethernet & TCP/IP & HTTP works
How to parse things in order to build a compiler (but I have forgotten most of it )
Haskell and functional programming concepts
Assembly
Numerical calculations for science and how to do them efficiently
Various neat low-level programming that you get to do in the IT security courses

@wallhackio And also Java, but I did not like Java

@vaporeon_ i was exaggerating. there are plenty of useful things to learn in computer science program

@vaporeon_ unfortunately my undergrad program taught us java for the introductory classes ​

@wallhackio Same

@vaporeon_ i did take an extremely fun class that taught us perl, C, and racket

@wallhackio Wow, all of these in one class? Sounds super cool
We did have lessons that taught us C, but I already knew C by then
They never taughts us Perl nor Racket (that's a LISP dialect, right?)

@vaporeon_ yeah racket is a lisp. it was a blast ​​

i remember during a lecture we were asked to write a factorial function, and i decided to input something absurd like, 10,000,000 as the input during lecture and 20 minutes later my function finished and took five full minutes to print the digits of the resulting number on my terminal which made the lecture very hard to pay attention to