Most corporate communications are unnecessarily fluffy to begin with because it makes it look like more work was done. Most of the time I don’t even understand why I’m explaining something and it feels like the only requirement is to have words on a page.
Sometimes the only requirement IS to have words on a page. Think about a disaster recovery plan, for example. Now, you probably don’t want an LLM to write your disaster recovery plan, but it’s a perfect example of something where the main value is that you wrote it down, and now you can be certified that you have one.
I just asked GPT to create a disaster recovery plan for a ransomware attack, and actually the information it gave wasn’t wrong or bad. But it’s also very generic, and it will rarely/never tell you correctly the specifics to your applications or where to click.
Most corporate communications are unnecessarily fluffy to begin with because it makes it look like more work was done. Most of the time I don’t even understand why I’m explaining something and it feels like the only requirement is to have words on a page.
Sometimes the only requirement IS to have words on a page. Think about a disaster recovery plan, for example. Now, you probably don’t want an LLM to write your disaster recovery plan, but it’s a perfect example of something where the main value is that you wrote it down, and now you can be certified that you have one.
I just asked GPT to create a disaster recovery plan for a ransomware attack, and actually the information it gave wasn’t wrong or bad. But it’s also very generic, and it will rarely/never tell you correctly the specifics to your applications or where to click.
there’s a whole book on the subject of bullshit jobs incidentally https://en.wikipedia.org/wiki/Bullshit_Jobs