Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Engineering problem

Engineering problem

Scheduled Pinned Locked Moved The Lounge
helptutorial
4 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    progload
    wrote on last edited by
    #1

    The fastest way to get an engineer to solve a problem is to declare that the problem is unsolvable. No engineer can walk away from an unsolvable problem until it's solved. No illness or distraction is sufficient to get the engineer off the problem. These types of challenges quickly become personal a battle between the engineer and the laws of nature (or microsoft). Engineers will go without food and hygiene for days to solve a problem. (Other times just because they forgot.) And when they succeed in solving the problem they will experience an ego rush that is better than sex (and I'm including the kind of sex where other people are involved). Nothing is more threatening to the engineer than the suggestion that somebody has more technical skill. Normal people sometimes use that knowledge as a lever to extract more work from the engineer. When an engineer says that something can't be done (a code phrase that means it's not fun to do), some clever normal people have learned to glance at the engineer with a look of compassion and pity and say something along these lines: "I'll ask Bob to figure it out. He knows how to solve difficult technical problems." At that point it is a good idea for the normal person to not stand between the engineer and the problem. The engineer will set upon the problem like a starved Chihuahua on a pork chop. -found somewhere on the net.

    W S R 3 Replies Last reply
    0
    • P progload

      The fastest way to get an engineer to solve a problem is to declare that the problem is unsolvable. No engineer can walk away from an unsolvable problem until it's solved. No illness or distraction is sufficient to get the engineer off the problem. These types of challenges quickly become personal a battle between the engineer and the laws of nature (or microsoft). Engineers will go without food and hygiene for days to solve a problem. (Other times just because they forgot.) And when they succeed in solving the problem they will experience an ego rush that is better than sex (and I'm including the kind of sex where other people are involved). Nothing is more threatening to the engineer than the suggestion that somebody has more technical skill. Normal people sometimes use that knowledge as a lever to extract more work from the engineer. When an engineer says that something can't be done (a code phrase that means it's not fun to do), some clever normal people have learned to glance at the engineer with a look of compassion and pity and say something along these lines: "I'll ask Bob to figure it out. He knows how to solve difficult technical problems." At that point it is a good idea for the normal person to not stand between the engineer and the problem. The engineer will set upon the problem like a starved Chihuahua on a pork chop. -found somewhere on the net.

      W Offline
      W Offline
      Watever_4
      wrote on last edited by
      #2

      So true, so true :) !

      1 Reply Last reply
      0
      • P progload

        The fastest way to get an engineer to solve a problem is to declare that the problem is unsolvable. No engineer can walk away from an unsolvable problem until it's solved. No illness or distraction is sufficient to get the engineer off the problem. These types of challenges quickly become personal a battle between the engineer and the laws of nature (or microsoft). Engineers will go without food and hygiene for days to solve a problem. (Other times just because they forgot.) And when they succeed in solving the problem they will experience an ego rush that is better than sex (and I'm including the kind of sex where other people are involved). Nothing is more threatening to the engineer than the suggestion that somebody has more technical skill. Normal people sometimes use that knowledge as a lever to extract more work from the engineer. When an engineer says that something can't be done (a code phrase that means it's not fun to do), some clever normal people have learned to glance at the engineer with a look of compassion and pity and say something along these lines: "I'll ask Bob to figure it out. He knows how to solve difficult technical problems." At that point it is a good idea for the normal person to not stand between the engineer and the problem. The engineer will set upon the problem like a starved Chihuahua on a pork chop. -found somewhere on the net.

        S Offline
        S Offline
        Steven Campbell
        wrote on last edited by
        #3

        I don't like to say "something can't be done". My phrase, when needed, is that "it is not feasible". Sometimes I'm asked what that means, at which time I say something like: "it is possible, but will take a long time and will probably introduce bugs into the system". No-one has used the "I'll ask Bob to figure it out" line on me yet, but I'm pretty sure I would fall for it. At the very least, Bob would receive a lot of unwanted help and advice ;)


        my blog

        1 Reply Last reply
        0
        • P progload

          The fastest way to get an engineer to solve a problem is to declare that the problem is unsolvable. No engineer can walk away from an unsolvable problem until it's solved. No illness or distraction is sufficient to get the engineer off the problem. These types of challenges quickly become personal a battle between the engineer and the laws of nature (or microsoft). Engineers will go without food and hygiene for days to solve a problem. (Other times just because they forgot.) And when they succeed in solving the problem they will experience an ego rush that is better than sex (and I'm including the kind of sex where other people are involved). Nothing is more threatening to the engineer than the suggestion that somebody has more technical skill. Normal people sometimes use that knowledge as a lever to extract more work from the engineer. When an engineer says that something can't be done (a code phrase that means it's not fun to do), some clever normal people have learned to glance at the engineer with a look of compassion and pity and say something along these lines: "I'll ask Bob to figure it out. He knows how to solve difficult technical problems." At that point it is a good idea for the normal person to not stand between the engineer and the problem. The engineer will set upon the problem like a starved Chihuahua on a pork chop. -found somewhere on the net.

          R Offline
          R Offline
          Roger Wright
          wrote on last edited by
          #4

          progload wrote: -found somewhere on the net. Scott Adams, author/creator of Dilbert. "My kid was Inmate of the Month at Adobe Mountain Juvenile Corrections Center" - Bumper Sticker in Bullhead City

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups