• Vlyn@lemmy.zip
    link
    fedilink
    English
    arrow-up
    70
    ·
    1 year ago

    Most of the entries were just funny, the last one is a nuke:

    1. I heard that the only real application for that technology was child pornography. How did you hear about it?
  • xmunk@sh.itjust.works
    link
    fedilink
    arrow-up
    48
    ·
    1 year ago

    Trying to build a team behind that technology would be a staffing nightmare.

    An incredibly valid consideration that too often goes ignored.

    • BrianTheeBiscuiteer@lemmy.world
      link
      fedilink
      arrow-up
      13
      ·
      1 year ago

      Oh, this one stings. My company uses a proprietary platform for it’s most critical records but we require a technical certification to even use its API. Pretty much an entire division said, “Fuck you! We’re not tying up our people for 3 months to study and acquire a certification. We just won’t use it!”

  • SpaceNoodle@lemmy.world
    link
    fedilink
    arrow-up
    44
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I like your idea. Why don’t you write up a white paper and we’ll review it at the next staff meeting?

    I think I might have said this verbatim before

    • xmunk@sh.itjust.works
      link
      fedilink
      arrow-up
      22
      ·
      1 year ago

      That one feels too cruel. If you said that to some junior dev they’d likely do it… and probably in their free time.

      That said with fellow senior devs if someone suggests something completely off the wall I will occasionally respond with, essentially, prove it first.

      • Carighan Maconar@lemmy.world
        link
        fedilink
        arrow-up
        14
        ·
        edit-2
        1 year ago

        “It’s* better** to do things*** by this approach.”

        Always throw a spanner in there with:

        *: [citation needed]
        **: According to who exactly?
        ***: Please specify exact use cases

      • Socsa@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        1 year ago

        With a senior engineer it’s perfectly reasonable to just say “ok, implement it and let me know how it works.”

        Like the whole point is that they should be relatively independent and capable of taking ideas from paper to product.

    • idunnololz@lemmy.world
      link
      fedilink
      arrow-up
      13
      ·
      1 year ago

      I was told to write my idea into an article to share internally with engineers. Then someone internally reached out to post it on our company tech blog. Then it got published on the tech blog. So I guess that’s something?

  • waz@lemmy.world
    link
    fedilink
    arrow-up
    29
    ·
    1 year ago

    As a started reading I thought “Hmm, some of these remind me of [coworker x]”. As I continued I realized all of these remind me of [coworker x].

    I might have to turn some of these into bingo cards.

  • computergeek125@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    ·
    1 year ago

    I’ve got one to add that should be used more often than it is.

    Wouldn’t that require running the service as an admin?

  • huntrss@feddit.de
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Didn’t read all, however, thanks for sharing. Made me laugh and I certainly needed a good laugh today

  • mateomaui@reddthat.com
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    If we go with that idea, we’re going to have Don Marti camped out in the front lobby with 300 angry software jihad supporters.

    do it