• pastermil@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 month ago

    That IT people can pretty much fix anything like TVs, HVACs, stoves, water heaters, fridges, toasters, rice cookers, and many more.

    Just because we work in tech, doesn’t mean we can deal with every technology known to mankind.

    And no, we’re not certified electricians.

  • intensely_human@lemm.ee
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    As an uber driver: that I know where building G is. Your housing complex is like ten acres of apartment buildings and speed bumps I have to go over while I search around for building G.

    For anyone unaware, you can fine-tune the pickup point in the Uber app by holding and dragging the map.

    You set the pickup point, then I meet you there. That’s my side of this job.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    That we IT people know everything about every bussiness application that is used in an org of more than 5 employees.

    If I new that I would be automating your job and you would be out of a job.

  • rockSlayer@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    no one QA’d this AAA game

    Actually, that game breaking bug was caught weeks ago by QA. Unmoving deadlines set by upper management meant that a fix couldn’t be made in time for the content schedule.

    • Mad_Punda@feddit.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      1 month ago

      Also, by the time the game has been released for 1 hour, the players have already racked up more playtime than the full QA team could reasonably achieve throughout several years of development (and for most of that time QA were playing an older version…). So, if your game has a lot of player choice, randomization, simulation, complex systems, chances are the players are seeing things that QA never did. And then the players wonder how QA could miss such an obvious bug.

      • rockSlayer@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        1 month ago

        I’ve mothballed multiple RCs from finding P0 issues by pure chance. In my experience, 90% of bugs are already caught by QA, 8% were isolated bugs that would realistically never get caught in QA, and 2% just slip through.

    • grrgyle@slrpnk.net
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      That’s why bugs can be labeled “in shipped version.”

      They know. It’s just they balanced it against everything else and it wasn’t worth spending time on or delaying the game for.

      I won’t say that it’s purely a AAA problem, but it’s harder to excuse there.

  • bigboismith@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    “IT is mainly introverts doing mysterious stuff no one understands”

    It is a very cooperative field where everyone has different roles with different responsibilities, but everyone has a vague idea what everyone else is doing. Most of the time is spent making sure everyone else can also use the systems you build, not just yourself.

  • dunz@feddit.nu
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    (IT support) I actually don’t know where that random setting in your application is, I’m just really fast and good at guessing from doing it a million times in applications I’ve never heard of before.

    • Brad@beehaw.org
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      Similar to that, just because someone works in IT, doesn’t mean they can fix your computer problem. I’ve worked with a lot of developers who were great coders but couldn’t resolve networking or random OS issues.

      • dunz@feddit.nu
        link
        fedilink
        arrow-up
        0
        ·
        1 month ago

        Oh yes. I support a lot of developers, and being a good programmer is not the same as understanding networking in a corporate environment or even knowing anything about printers. That’s why I’m needed 😃

      • sexual_tomato@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        0
        ·
        1 month ago

        I’m a developer. Most of the time when I contact IT it’s because they broke something I rely on, like our vCenter appliance or network communications between some Linux appliances with static IPs.

  • Bo7a@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    That the folks in IT have any sway over microsoft or facebook’s ui plans.

    NO Karen, I can not make Teams go back to the way it used to be. No matter how many times you ask.

  • rozodru@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    I work with the homeless. the main misconception is that they’re all either addicts or mentally ill. This is far, far, from true. The ones you see daily, chances are they are addicts or mentally ill but the “hidden” homeless vastly out weighs the ones you see on the streets.

    Most have jobs or are actively looking for work. A lot are escaping domestic abuse or are LGBTQ+ and escaping hostile home environments. There are A LOT of families and elderly people who simply can’t afford to keep a roof over their heads.

  • cynar@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    I work with radio camera links. The number of people who get upset over the receivers is depressing. They can make the 5G conspiracy theorists look educated.

    Receive equipment is incapable of radiating at all.

    The part that radiates is completely safe!

    Seriously, any danger would be at the camera end. I am happy to sit with it fully powered and the antenna between my legs. (It stops the camera getting knocked over). It can’t put out enough power to do any harm. It’s comparable to home WiFi and weak compared to the mobile phone you are happy to put to your head!

  • wellDuuh@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    In any software development timeline given, triple it to be safe!

    Programmers don’t just pull perfect codes from their butts.

    Programming languages (yes, in some scenarios, even python) are hell to work with. And yes, I know developer experience has gotten so much better compared to 5 years ago. Still, there are too many unknowns.

    It’s like trying to shush a crying baby. Trying every trick on the book to put her back to sleep. But naaah, all she does is cry (no reasons, no hints)

    This makes a half-an-hour job take 2 days (hence the unknown delays and setbacks)

    If you meet a programmer that pulls a rough prototype of a single module inside a program in a few seconds and works immediately. Know that he/she has 10+ years of experience in that language domain.

    Like a granny that “feels the baby” and knows what it wants, making the baby calm immediately.

      • wellDuuh@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 month ago

        LoL Buddy, I’m not.

        One word: “patience”

        Patience in trying and trying until a solution sticks :)

    • ECB@feddit.org
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      And even then, it just meant that whatever solution they thought up worked first try.

      With experience you get better at finding good, working solutions quicker, but there will always be times when things take a bit of iteration.

  • Treczoks@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    That I could fix Windows PCs. Nope. When my work PC has issues, I call IT. I design computer chips.

    • choss@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      Hey! Can I ask you about that? What type of chips? What are your most used skills/technologies and what helped get started when you were new? I want to work with fpgas, and I’d love to know what your experience with that has been like

      • Treczoks@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 month ago

        I started with programming about anything that is programmable and not up on a tree at the count of three. I did industrial control units, and I worked on a Cray X-MP, and about anything between. I wrote computer games, compilers, an OS, database engines, and loads of applications. I’ve probably forgotten more programming languages than todays students have heard of. One day I ended up in embedded systems.

        As our company had only one FPGA developer, I got sent on a three day course to learn VHDL from the source (Eugen Krassin, one of the original key developers of ISE). Right after that, I started developing FPGA firmware for our company. Luckily, I had some hardware experience from my work on the C64 and earlier, so I had a good understanding of clocks and signals. I know that even seasoned programmers really hit a wall when entering the world of HDLs.

        I started with ISE back then on Spartan S3 and S6, then Xilinx f-ed us up so hard that the boss slammed the phone down after the last call with those guys and told me to find a more reliable company STAT. We now use Efinix FPGAs which has the big advantage that people there actually listen and help when I ask a question.

        My field is isosynchronous low-latency networks for audio applications.

        • choss@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          1 month ago

          Woah, you’re on OG! I’m unfamiliar with a lot of those things and had to look them up. Crazy!

          Hah! ISE - I used that for a hot second, and you still see tutorials using it as well.

          My goodness, tell me about it, I’m new and I already find myself frustrated with Xilinx sometimes. It feels like there are very few resources from them for learning, but I thought that was just because it’s a niche subject. I’ll have to take a look at Efinix. I guess I thought it was safer to stick to the biggest name while I’m trying to get established. At the moment I’m trying to get some example projects working on a Zybo Z7. I’m finding out that it’s a lot to take in

          Thanks for taking the time to reply! I feel strangely honored to hear from such an OG :) Cheers!

          • Treczoks@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            1 month ago

            Whenever you are looking for a supplier for something, keep in mind that there are advantages and disadvantages when choosing one.

            If you are in a small niece company, and your supplier is THE BIG OLD COMPANY, you are completely at their mercy. On the other hand, they usually have vast resources you can tap, like training capabilities and software you won’t get elsewhere, or at least nor for the price.

            That was our relationship with Xilinx. Yes, you get trainings and tutorials for everything, and they have a “light” version of ModelSim thrown in for free in their IDE, but on the other hand, they basically cut us off from one day to the next. And that was not even our fault.

            So we went looking and found Efinix. Small, but growing, their IDE has a few edges that need to be rounded off, and they can’t afford to throw in a free simulator, so we had to spend quite a few bucks to buy that (and it was not even ModelSim we bought, so I had to re-train). But at least they are open and helpful. You ask a question in their forum, and they come back to you to help. I’ve been talking to real people who are directly in contact with the dev team. When I had a strange compiler problem, I had a fix within 48 hours. THAT is gold in a supplier.

            I’m finding out that it’s a lot to take in

            Yes, indeed. The step from CPU-based programming languages to Hardware definition languages is hard for most programmers, and for some, it is even insurmountable. Once you get the hang of it, it gets way easier.

            I met a student once in a Reddit sub once who had issues with her code. I helped her and gave her a few tips how to improve it, and at the end, she asked me of my opinion of the project. I told her that it was a nice little beginner project, something to pass a boring Friday afternoon. Her reply: “Thats my Bachelor Thesis!*”. What looks big and difficult to master will one day look simple and meek when you look back, so don’t let it drag you down if things don’t work on the first try.

    • BangersAndMash@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      When I lost my credit card overseas I was issued an emergency replacement by MasterCard and it only had MasterCard branding. I guess sometimes they issue cards (unless they got a bank to print it without their branding).

      • knightly the Sneptaur@pawb.social
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        1 month ago

        That’s technically not a card issuance, which in CC terms only happens when the bank associates an account on their end with a new card profile from the CC company. No actual card needs to be issued either, a token in a digital wallet works the same way.

        Deactivating a lost card and activating a replacement (temporary or otherwise) are just maintenance activities on an existing card profile. They get recorded to the original profile both for record-keeping and so that the bank doesn’t get billed extra for issuing a new one.

          • knightly the Sneptaur@pawb.social
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            1 month ago

            I did too! Turns out there’s a lot of weirdness and jargon that gets built into the system after 44 years of continuous operation, and of course the CC companies wanted to be able to bill separately for issuing new cards and printing replacements. XD

  • QuarterSwede@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    We aren’t trying to screw you, the actual solutions (not bandaids) are just expensive (paying for knowledge, skill, equipment, and parts). That 5 min fix took years to know to look for and how to fix quickly, plus have the part on the truck for immediate installation. Typically a quick tech is a good tech if the problem is solved.