4 ms·

My skip manager started asking for weekly status reports so my manager started pulling Jira reports and feeding them to ChatGPT. It turns out that my skip manag

My skip manager started asking for weekly status reports so my manager started pulling Jira reports and feeding them to ChatGPT. It turns out that my skip manager was using Copilot to summarize those reports into basically what you could get directly from Jira.

david38 1y ago
Wow. Full circle
hamburga 1y ago
This is how society collapses and OpenAI wins.
- hamburga 1y ago
  Also see Commandment 7 - https://muldoon.cloud/2023/10/29/ai-commandments.html https://muldoon.cloud/2023/10/29/ai-commandments.html
- daxfohl 1y ago
  It's already started, with AI resume spamming on one side and the associated AI assisted screening on the other. "Deep research" generated funding requests on one side and associated AI generated funding request summarization on the other.
  - jacob_rezi 1y ago
    what are the keywords to use to search for ai resume spam tools?
    - MonkeyClub 1y ago
      Unironically, "ai resume spam tools" seems to work well enough. Even more unironically, if you run the search through Google, you'll get a nice AI summary at the top as well. O tempora, o mores.
Terr_ 1y ago
Recycling a prediction from a year ago: > Ultimately a lot of this generative tech stuff is just counterfeiting extra signals people were using to try to guess at interest, attentiveness, intelligence, etc. > So yeah, as those indicators become debased, maybe we'll go back to sending something [...] all boiled down to bullet points.
ctkhn 1y ago
This is the kind of thing my manager and skip manager are up to. Most of our jira tickets now are written as a random jumble of ideas, fed into internal proprietary LLM and then turned into jira description and acceptance criteria. Totally pointless
hliyan 1y ago
I've seen this happen in emails too: "Recent outage was due to a retry loop for the Foo API exceeding rate limits. We're implementing a backoff algo" Sender, via ChatGPT: Hi, I wanted to provide more context regarding the recent outage. The issue was triggered by a retry loop in the Foo API integration. When the API began returning errors, our system initiated repeated retry attempts without sufficient delay, which quickly exceeded the rate limits imposed by the API provider. As a result, requests were throttled, leading to degraded service availability. To address this, we are implementing an exponential backoff algorithm with jitter. This approach will ensure that retries are spaced out appropriately and reduce the likelihood of breaching rate limits in the future. We are also reviewing our monitoring and alerting thresholds to detect similar patterns earlier. We’ll continue to monitor the system closely and share further updates as improvements are rolled out. Best regards, Receiver, via ChatGPT: "The outage was caused by excessive retry attempts to the Foo API, which triggered rate limiting and degraded service. To prevent recurrence, exponential backoff with jitter is being implemented"
- nullc 1y ago
  Would be a nice fine tuning target: training to close that loop.
whiplash451 1y ago
Funny how encoder-decoder architectures have led to decoder-encoder behaviors.

david38 1y ago

Wow. Full circle

hamburga 1y ago

This is how society collapses and OpenAI wins.

hamburga 1y ago
Also see Commandment 7 - https://muldoon.cloud/2023/10/29/ai-commandments.html https://muldoon.cloud/2023/10/29/ai-commandments.html
daxfohl 1y ago
It's already started, with AI resume spamming on one side and the associated AI assisted screening on the other. "Deep research" generated funding requests on one side and associated AI generated funding request summarization on the other.
- jacob_rezi 1y ago
  what are the keywords to use to search for ai resume spam tools?
  - MonkeyClub 1y ago
    Unironically, "ai resume spam tools" seems to work well enough. Even more unironically, if you run the search through Google, you'll get a nice AI summary at the top as well. O tempora, o mores.

Terr_ 1y ago

Recycling a prediction from a year ago: > Ultimately a lot of this generative tech stuff is just counterfeiting extra signals people were using to try to guess at interest, attentiveness, intelligence, etc. > So yeah, as those indicators become debased, maybe we'll go back to sending something [...] all boiled down to bullet points.

ctkhn 1y ago

This is the kind of thing my manager and skip manager are up to. Most of our jira tickets now are written as a random jumble of ideas, fed into internal proprietary LLM and then turned into jira description and acceptance criteria. Totally pointless

hliyan 1y ago

I've seen this happen in emails too: "Recent outage was due to a retry loop for the Foo API exceeding rate limits. We're implementing a backoff algo" Sender, via ChatGPT: Hi, I wanted to provide more context regarding the recent outage. The issue was triggered by a retry loop in the Foo API integration. When the API began returning errors, our system initiated repeated retry attempts without sufficient delay, which quickly exceeded the rate limits imposed by the API provider. As a result, requests were throttled, leading to degraded service availability. To address this, we are implementing an exponential backoff algorithm with jitter. This approach will ensure that retries are spaced out appropriately and reduce the likelihood of breaching rate limits in the future. We are also reviewing our monitoring and alerting thresholds to detect similar patterns earlier. We’ll continue to monitor the system closely and share further updates as improvements are rolled out. Best regards, Receiver, via ChatGPT: "The outage was caused by excessive retry attempts to the Foo API, which triggered rate limiting and degraded service. To prevent recurrence, exponential backoff with jitter is being implemented"

nullc 1y ago
Would be a nice fine tuning target: training to close that loop.

whiplash451 1y ago

Funny how encoder-decoder architectures have led to decoder-encoder behaviors.