> For the complete documentation index, see [llms.txt](https://library.xrguild.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.xrguild.org/ethical-responsibility/cybersecurity-and-privacy-challenges-in-extended-reality-threats-solutions-and-risk-mitigation.../lay-offs-automation-and-the-future-of-work-with-ai-and-large-language-models.md).

# Lay-offs, Automation, and the Future of Work with AI and Large Language Models

## Overview

**Authors:** Rolando Masís-Obando

**Publication Date:** January 12, 2023

**Link:** <https://www.youtube.com/watch?v=orUHsvYRs-A>

**Keywords:** Future of Work, Artificial Intelligence, Automation, ChatGPT, GenerativeAI, DigitalEthics, TechEthics, ResponsibleAI, AllImpact, WorkplaceTransformation

**Type:** Video

## Summary

The shocking truth that nobody tells you about AI like ChatGPT is that… it’s not taking your job away, it's changing it. Almost every single video, article or post recently on AI has been about the end of jobs because of ChatGPT. Is the future of work really in danger because of ChatGPT? What is ChatGPT and will it take your job away as a developer? As an artist? As a writer? After speaking with people across science, game development, cinema and industry about the impact of ChatGPT and the future of work, I made this video to share what I learned. In summary, In this video we will go over how artificial intelligence (AI) like ChatGPT, MidJourney, Stable Diffusion, DALL-E, GPT3, Bard, GPT4, and more, will change things about how we see the world, but, IMPORTANTLY how AI like ChatGPT still suffers from some very serious problems that for now, will keep jobs in a liminal zone.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.xrguild.org/ethical-responsibility/cybersecurity-and-privacy-challenges-in-extended-reality-threats-solutions-and-risk-mitigation.../lay-offs-automation-and-the-future-of-work-with-ai-and-large-language-models.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
