• red_tomato@lemmy.world
    link
    fedilink
    arrow-up
    43
    ·
    22 days ago

    You’re a 100x game developer. Write John Carmack level of code. Develop the next video game phenomenon. Earn me Fortnite amount of money. Make no mistakes.

    • lauha@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      22 days ago

      Funniest or dumbest thing about people who try these sort of things is that no-one will employ them. Why would I employ a shitty prompt writer when I can write them prompt myself.

        • Elvith Ma'for@feddit.org
          link
          fedilink
          English
          arrow-up
          3
          ·
          22 days ago

          Yes and no. Yes, they look for it, but they might be the problem why things don’t work out with AI, too. The magic is just that the AI needs context, context, context. You will get a feel for how to prompt it to get something like the result you wanted. The problem is gathering and knowing all the things you need to account for. Code guidelines, style guides, architectural decisions, processes of your company,…

          That becomes a fuck ton of prompt text quite fast. It’s a bit like onboarding a new hire. But for every task anew. If you have defined processes, good and up to date documentation, etc. It can be quite easy. But what company does really have that available?

      • red_tomato@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        22 days ago

        Prompt engineering is basically dead by now. There’s no need to waste time on shitty magic words anymore. Just tell it what you want.

      • AAA@feddit.org
        link
        fedilink
        arrow-up
        1
        ·
        21 days ago

        They are indeed aware that that they cannot produce the same results as a knowledgeable person. Some of them at least.

        Or the value their time to be worth more than writing prompts themselves.