> For the complete documentation index, see [llms.txt](https://cs61b-2.gitbook.io/cs61b-textbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cs61b-2.gitbook.io/cs61b-textbook/33.-software-engineering-iii/33.4-summary.md).

# 33.4 Summary

In this fun lecture, we steered a bit away from core CS61B exam material and discussed a high-level overview of the impacts that students can have on society and on their own lives using the skills obtained in CS 61B and beyond.

We covered specific societal impacts in the realm of economics within the context of industry, and social impacts with how humans in our global civilization interact with one another using the digital products that we can create using our coding skills. Most importantly, we delved into the potential *harms* to society that our coding skills could have – from the psychological foundations that could be altered on our youth to the reconfiguration of politics and governmental leaders are elected.&#x20;

With great power comes great responsibility, and it is evermore vital that we consider the deep, all-encompassing question of ethics in creating software for humanity.&#x20;

With the demand for software engineers and the financial impact that creating software solutions to the worldwide marketplace has, the value added to you as a worker in our society is immense & very fruitful. However, it is important to consider factors beyond just work to create a multifaceted thing called your life. We only work so many hours in the weeks in our lives– so it is incredibly important to ensure that work (and learning CS to become a software engineer, etc.) is just a subpart of what we consider our entire life. Have fun on the journey!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cs61b-2.gitbook.io/cs61b-textbook/33.-software-engineering-iii/33.4-summary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
