you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 year ago (21 children)

Maybe for dev knowledge, but computer science? The science of computers?

  • source
  • parent
  • hideshow 21 child comments
  • [–] 12 points 1 year ago (8 children)

    What kind of cs degree did you get where you learned about electrical circuits. The closest to hardware I've learned is logic circuit diagrams and verilog.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 7 points 1 year ago (5 children)

    I mean, I graduated over 20 years ago now, but I had to take a number of EE courses for my CS major. Guess that isn't a thing now, or in a lot of places? Just assumed some level of EE knowledge was required for a CS degree this whole time.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 9 points 1 year ago (3 children)

    I got my BS in CSci about 15 years ago and it was 100% about programming in java. We didn't learn a fucking thing about hardware and my roommate was an EE major and we had none of the same classes except for calculus.

    By the time I graduated java was basically dead. Thanks state college.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 year ago

    My CS program had virtually no programming outside a couple of courses where C was used to implement concepts. Had one applications type course where mostly Java was used.

    CS is and should be a specialized math curriculum IMO. Teaching specific programming languages is time that would be better spent teaching theory that can't be taught by dev docs or code bootcamps, as exemplified by your anecdote. Unfortunately nowadays people tend to see degrees as glorified job training programs.

  • source
  • parent
  • Yeah, EE and CS had a lot of cross over where I went. At least in undergrad, grad school saw them diverge a lot more, but they still never disentangled, parts of each were important to both. Hell we had stuff like A+ labs, and shit.

  • source
  • parent
  • [–] 1 point 1 year ago*

    In my uni they kinda just teach java. There is one mandatory class that's in C and one that's in mips assembly tho.

    Everyone used AI when I took those classes. By the end of the year they were still having trouble on groupchat with syntax stuff.

  • source
  • parent
  • [–] 3 points 1 year ago

    In my own uni's coursework the closest we get are some labs where students some simple adder circuits, which we do just to save them from embarassing gaps in their knowledge (like happened in the inital comment). It doesn't add much beyond a slightly better understanding of how things can be implemented, if we're being honest.

  • source
  • parent
  • [–] 10 points 1 year ago (8 children)

    Well, computer science is not the science of computers, is it? It's about using computers (in the sense of programming them), not about making computers. Making computers is electrical engineering.

    We all know how great we IT people are at naming things ;)

  • source
  • parent
  • hideshow 8 child comments
  • [–] 3 points 1 year ago* (1 child)

    My BS in CS took its roots down to CMOS composition of logic gates and basic EE, on the hardware side, and down to deriving numbers and arithmetic from Boolean logic / predicate calculus, on the philosophy side. Then tied those up together through the theoretical underpinnings of computation and problem solving, like a trunk, and branched back out into the various mainstream technologies that derived from all that. It obviously all depends on the program at the school of choice, I suppose, and I'm sure it's evolved over the years, but it still seems important to have at least some courses that pull back the wizard's curtain to ensure their students really see how it's all just an increasingly elaborate, high-tech version of conceptually simple (in function) machinery carrying out fundamental building blocks of logic.

    Anyway, I'm going to go sniff my own cinnamon roll scented farts while gazing in the mirror, now.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    We did the same thing, going so far as to "build" a simple imaginary CPU. It was interesting but ultimately dead knowledge.

    I built an emulator for that CPU, which the university course took over and used for a few years for the course. But after that I never did anything with logic gates or anything like that.

    I got into DIY electronics lateron as a hobby, but even then I never used logic gates and instead just slapped a cheap microcontroller on to handle all my logic needs.

    I do use transistors sometimes e.g. for amplification, but we didn't learn anything about that in university.

    In the end it feels like learning how to theoretically mine sand when studying to become an architect. Interesting, but also ultimately pointless.

  • source
  • parent
  • [–] 0 points 1 year ago (1 child)

    It wasn't named by IT people, though. It was named by academics. And it's not about using computers, it's about computing. Computer science is older than digital electronics.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago*

    Mhm, and those academics were no IT people and had nothing to do with computers?

    Let's fact-check that.

    Computer Sciences as an academic course was first created by IBM at the Columbia University in 1946. Because IBM had made their first commercial computer two years prior and wanted to have people who could operate it and who could continue to develop it.

  • source
  • parent
  • [–] 3 points 1 year ago (1 child)

    If you want someone to know about the physical properties of transistors, find an electrical engineer.

  • source
  • parent
  • hideshow 1 child comment