• squaresinger@lemmy.world
    link
    fedilink
    arrow-up
    20
    arrow-down
    1
    ·
    2 days ago

    Tbh, as a dev knowledge of transistors is about as essential as knowledge about screws for a car driver.

    It’s common knowledge and in general maybe a little shameful to not know, but it’s really not in any way relevant for the task at hand.

      • Euphoma@lemmy.ml
        link
        fedilink
        English
        arrow-up
        11
        ·
        2 days ago

        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.

        • Jiggle_Physics@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          7
          arrow-down
          1
          ·
          2 days ago

          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.

          • Jankatarch@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 day 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.

        • wieson@feddit.org
          link
          fedilink
          arrow-up
          2
          ·
          1 day ago

          I learned about transistors in Informatics class in highschool. Everything from the bottom up, from the material that makes a transistor possible to basic logic circuits sr flip flops, and, or, xor, addition, to the von-neumann-architecture, a basic microprocessor and machine code and assembly.

        • Warl0k3@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          2 days ago

          In my own uni’s coursework the closest we get are some labs where students breadboard 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.

      • squaresinger@lemmy.world
        link
        fedilink
        arrow-up
        10
        ·
        2 days ago

        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 ;)

        • Lehmanator@programming.dev
          link
          fedilink
          English
          arrow-up
          2
          ·
          11 hours ago

          Computational theory would be a better name, but it overlaps with a more specific subset of what is normally called CS.

          • squaresinger@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            10 hours ago

            We could also just call it Software Engineering. That’s at least the job everyone gets with a Computer Science degree.

        • atx_aquarian@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          1 day ago

          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.

          • squaresinger@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            1 day 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.

        • rizzothesmall@sh.itjust.works
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          2 days ago

          Ok, but he didn’t know what a transistor is. Like I get not knowing the mechanics or chemistry of it, but to literally not know it or how it applies to a computer boggles my mind.