• MasterBlaster@lemmy.world
    11·
    13 hours ago

    No. The proper term is GEEK. Needs are uncoordinated, awkward, have no fashion sense, and occasionally tape their broken glasses (or say sheepishly, “did I do that?”)

    Geeks have in-depth, we’ll researched knowledge on topics that are obscure to the “mundanes”, have intellectual curiosity, and sometimes gain in wealth as a result. In many cases, they tend to make non-geeks (and geeks for other topics) completely befuddled. This sometimes results in insecurity on the part of non-geeks, which negatively impacts their social lives. On rare occasions, such geeks are so over the top smart that they transcend such petty attitudes (see: Neil deGrasse Tyson)

  • epicstove@lemmy.caEnglish
    3·
    2 days ago

    If you’re programming in assembly, regardless of what it is, you are the biggest nerd of them all. And I have massive fucking respect for you.

  • Log in | Sign up@lemmy.world
    29·
    3 days ago

    I am not in this chart because my favourite programming languages are too nerdy for the cool programming nerds to include in their nerd chart.

        • Trimatrix@lemmy.world
          5·
          3 days ago

          A ton of people. Anything aerospace, DoD, Space, or critical infrastructure. All those industries have to use VHDL to support legacy products from the 80s and 90s. At that point everyone is like, “Sure its 2025, by why switch to SystemVerilog? We already know VHDL.” and thus you got a whole army of engineers making next gen satellites, augmented reality headsets, etc. …… in VHDL 93.

            • Trimatrix@lemmy.world
              3·
              2 days ago

              Not really, HDL is HDL. At the end of the day, as long as you know what you want to do electrically then everything else is an exercise of translating that desire into VHDL, Verilog, or SystemVerilog. The only real hassle is creating test-benches and verification simulations. But at that point it’s discretionary towards the designer. A lot of tools coming from Intel, Xilinx, and Synopsys allow you to “black box” components. So a module written in VHDL can be incorporated into a design or test bench written in verilog and vis-versa. IMHO VHDL is still dominant because grey beard chief engineers throw a little hissy fit at design reviews when they learn the junior engineers did everything in verilog.

              • white_nrdy@programming.dev
                1·
                4 hours ago

                Tbf, I am not a grey beard chief engineer, and I strongly prefer VHDL for design. For verification I actually really like SystemVerilog.

                VHDL is strongly types, which prevents a lot of issues with types that I’ve hit with [System]Verilog.

                Also, having learned VHDL first, I think it is easier to go from VHDL to Verilog, as opposed to vice versa. And this is mainly because VHDL is stricter.

        • Zink@programming.dev
          1·
          3 days ago

          I do mostly c/c++ for an embedded product, but one of the modules in the system uses an FPGA programmed w/ VHDL. So I’ve gotten to do a few deep dives into that code in the past couple years.

          It’s been decades since I’ve had to write new VHDL or Verilog though.

  • omega_x3@lemmy.world
    2·
    2 days ago

    Wow I’m an old engineer nerd. I feel so exposed. Zero is nothing always start at one for life.

  • TimeSquirrel@kbin.melroy.org
    25·
    4 days ago

    Cobol: you are old, and a nerd, and probably making some sweet cheddar right now propping up a mid to late 20th century beast somewhere.

    Assembly: you are a cyborg.

    • anomnom@sh.itjust.worksEnglish
      10·
      4 days ago

      Assembly: you are a cyborg.

      Or programming a tiny microcontroller to blink a led as efficient as possible.

      • TimeSquirrel@kbin.melroy.org
        6·
        4 days ago

        Something wrong with:

        #include <Arduino.h>


void loop()  {
digitalWrite(13, HIGH);
delay(1000);
digitalWrite(13, LOW);
delay(1000);
}

        ? 😂🤮

        • Scrath@lemmy.dbzer0.com
          11·
          3 days ago

          Obviously the only correct way to blink an LED is to use a hardware timer to trigger a DMA transfer which stores a bit in the pin toggle register at a set interval

          • anomnom@sh.itjust.worksEnglish
            2·
            3 days ago

            yeah! Or or use the interrupt pins and a 555 timer! both options are better than python though at least.

  • QuazarOmega@lemy.lol
    21·
    4 days ago

    I know who made this included React and HTML specifically to trigger us programmers, to that I say… well played >:(

  • echolalia@lemmy.ml
    14·
    3 days ago

    R

    We can reject the null hypothesis that you are not a nerd at significance $\alpha < 0.001$.

    oh wait, shit let me run that again, my data frame is full of NA somehow, again.