• WagnasT@iusearchlinux.fyi
    link
    fedilink
    English
    arrow-up
    21
    ·
    8 months ago

    I put the data in excel and make colorful charts to show management that their ideas are possible but expensive. Then do the same to show the cost of not purchasing maintenance equipment is in fact more costly than the necessary equipment.

      • crapwittyname@lemm.ee
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        8 months ago

        And then they point the finger six months later when the fan is covered in shite, am I right? An engineer is just an “I-fucken-told-you-so” generator. Sometimes.

  • ArchAengelus@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    19
    ·
    8 months ago

    As an engineer:

    1. Receive or identify a problem.
    2. Design a solution that solves or mitigated the problem.
    3. Usually pay someone to make a prototype or do it ourselves
    4. Test the prototype and see if it solves the problem. If no, go back to #2 until a workable solution is found
    5. Get someone else to build the final thing.
    6. Make sure thing works. Ship it.

    This is a recursive and iterative process. Meaning you will find problems inside your solutions and need to fix them.

    Eventually you finish the thing and get a new problem and do the whole game over again. It’s like a puzzle that requires absurd amounts of knowledge to play well, but anyone could try to solve the problem. That’s why good engineers are paid pretty well.

    • crapwittyname@lemm.ee
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      8 months ago

      That’s a pretty good run down. There’s all sorts of soft skills required for that as well, and hard skills specific to the industry they’re in, but I think you’ve got the essence of it. Also in step 6, add: “take responsibility for everything that will go wrong with thing in the future” aka “sign off”.

  • matlag@sh.itjust.works
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    8 months ago

    Half of the job is to fix issues with existing suff, the other half is to make working stuff more complicated and problematic (aka “upgrade”), so that we’re still paid to do the first half.

  • acockworkorange@mander.xyz
    link
    fedilink
    arrow-up
    7
    ·
    8 months ago

    “The Engineering Method” by Mark Hammond aka the engineer guy is a great read…

    …is what I would say if I actually purchased books from my wishlist.

  • nadiaraven@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    8 months ago

    I interned at a mechanical engineering firm. We contracted out field workers to do the real work at construction sites, installing big hvac systems, while we coordinated between them and the general contractor. Much of engineering is about designing things using math and cad

    • copernicurious@lemmynsfw.com
      link
      fedilink
      arrow-up
      2
      ·
      8 months ago

      Scientists make something new. One time. In a lab. Under ideal conditions. With 3 PhDs assembling, testing, and running it.

      Engineers have to make the same thing so that their cheap-ass company can hire any gaggle of idiots off any street around the world and train them to assemble, test, and run 500 of the thing.

      Alternatively so those same idiots can buy the product and do all manner of stupid things to it without it breaking.

      Note: not saying all technicians are idiots, but the good ones get paid more so companies eventually go for the idiots instead.

  • Waterdoc@lemmy.ca
    link
    fedilink
    arrow-up
    2
    ·
    8 months ago

    Math using janky excel spreadsheets, tell drafters what we want drawings to look like, but mostly a lot of reading and writing. The secret to engineering (at least in my area) is that communication skills are just as important as technical understanding.

  • Someonelol@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 months ago

    As an engineer I can say it can be a “hurry up and wait” kind of job. Around the 20% mark of a project timeline I’m 80% finished but then have to rely on a non-responsive authority to answer me back over some obscure part of the project. After that I just nag them and the project manager about it in email to cover my ass then do fuck all until they respond. At the 95% mark they answer back and I have to hurry up to finish. It can be stressful at times but it’s not bad otherwise.

    • OceanSoap@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      I’m a designer that works with a bunch of engineers and yeah. I’ve got two projects that we had to rush in a two week deadline. Now we’ve been waiting for months on a reply about something. Just waiting.

  • key@lemmy.keychat.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

    It’s an elaborate money laundering scheme. Most “engineers” secretly cook meth and stuff. It’s actually super easy to make like buildings and planes because God holds them up until He decides they should fall.