> For the complete documentation index, see [llms.txt](https://program.hackyourfuture.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://program.hackyourfuture.dk/course-content/shared-modules/using-ai-in-development/week1/assignment.md).

# Assignment

## Part A: Review and Improve Portfolio

In the previous AI module, you created an initial version of your portfolio. In this assignment, you'll use AI to review, improve, and document your work.

1. **Get a code review** - Use AI to review your portfolio code. Ask for feedback on readability, best practices, potential bugs, and security.
2. **Note improvements** - From the feedback, identify at least 3 improvements or changes you want to make. Write these down.
3. **Implement the changes** - Make the improvements to your code. Use AI to help if needed, but make sure you understand each change.
4. **Generate a diagram** - Use AI to generate an ASCII diagram that describes the structure of your portfolio project.
5. **Reflect on learnings** - Write down 3 new things you learned from the review and implementation process.

## Part B: Ethics and Risks

Choose 3 ethical issues or risks associated with the use of AI in development (refer to the session material if you need a reminder).

For each one, describe:

* What the issue/risk is, in your own words
* How you will personally mitigate it in your own use of AI

## Submission

Submit your updated portfolio code, along with a `reflection.md` file containing:

* Your list of improvements from Part A
* Your diagram from Part A
* Your 3 learnings from Part A
* Your 3 ethical issues and mitigations from Part B


---

# 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://program.hackyourfuture.dk/course-content/shared-modules/using-ai-in-development/week1/assignment.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.