Skip to content

Itd AI guidance - #1950

Open
Poonam-raj wants to merge 8 commits into
mainfrom
itd-ai-edit
Open

Itd AI guidance#1950
Poonam-raj wants to merge 8 commits into
mainfrom
itd-ai-edit

Conversation

@Poonam-raj

@Poonam-raj Poonam-raj commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

This PR will

  • Update small Slack and ITD references that are out of date.
  • Extend and amend Step Three instructions to reflect the wider CYF Ai Guidance.
  • remove answer 8 from the third question in the Step Three task
  • Amend step 6 and 7 where AI is encouraged to make it more generic to the internet whilst still exploring AI, also referencing step three more.

Areas review is especially needed

  • Whether step six and step seven still push AI in a way that doesn't align with our AI guidelines. Is it pushing it too hard? Or is it enabling exploration to inform trainees?
  • Do the questions in step three align with AI guidance, does anything stand out as misleading? (I was thinking of making these multiple choice elements but then realised a submission relies on it going into a google doc so couldn't. Would love a way of getting feedback to a student and make step three have a submission that makes sense at the same time.)
  • Does the opening explanation in step three ramble too long and lose the trainee before getting to the "acceptable" criteria?

@netlify

netlify Bot commented Jul 22, 2026

Copy link
Copy Markdown

Deploy Preview for cyf-curriculum ready!

Name Link
🔨 Latest commit 5d39aa6
🔍 Latest deploy log https://app.netlify.com/projects/cyf-curriculum/deploys/6a6a1b414af18700086a3073
😎 Deploy Preview https://deploy-preview-1950--cyf-curriculum.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 85 (🔴 down 13 from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jul 22, 2026

Copy link
Copy Markdown

Deploy Preview for cyf-common ready!

Name Link
🔨 Latest commit 5d39aa6
🔍 Latest deploy log https://app.netlify.com/projects/cyf-common/deploys/6a6a1b41c9946d000840c918
😎 Deploy Preview https://deploy-preview-1950--cyf-common.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@Poonam-raj

Copy link
Copy Markdown
Contributor Author

Related ticket: #1901

@Poonam-raj
Poonam-raj marked this pull request as ready for review July 22, 2026 15:07

@illicitonion illicitonion left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all LGTM, left a few suggestions, the side-by-side CV may be a little work to put together but I think is probably really worthwhile? I've definitely had a lot of experiences of pointing out to a trainee (particularly on ITD when we used to have them generate CVs/cover letters with GenAI) how bad their AI-generated cover letter was

Comment thread common-content/en/module/itd/step-3/instructions/index.md Outdated
Success at CYF is not about using AI to rush through the course and tick all the boxes. It's about building a deep understanding of the concepts we teach for yourself. Using AI to do the work for you wastes everyone’s time. You will end the course without the coding skills you wanted (which means you won't get a job) and our volunteers will have wasted their time marking AI work.
This means that all output from AI is potentially untrustworthy, we should keep a critical eye on the output of AI tools.

### Why do we need to be careful as ITD trainees?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd be tempted to split this into two sub-sections:

  1. We need to build understanding
  2. Sometimes it lies

I think the "we need to question and verify and explain" could do with being split into those two sections too:

  • In the "building understanding" section we can talk more about how we should be able to spot problems in AI output, and we should be able to delete AI output and write it ourselves because we know how.
  • In the "sometimes it lies" section, we can talk a bit about looking up other sources


You need to exercise CAUTION and avoid the following situations:

- Letting AI write your CV

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Letting AI write your CV
- Letting AI write something for you (e.g. your CV)

And let's explain why this is bad - that it will generate generic CVs which don't sell you, which aren't personal, that use filler words, that make things up about your background, etc.

Maybe we could even include side-by-side a bad AI generated CV and a good personally written CV, and give trainees a prompt for some criteria to use to compare them, and have them submit their comparison? (On average our ITD trainees don't know what a good CV looks like, so I think we would need to give them criteria to evaluate from)

Co-authored-by: Daniel Wagner-Hall <daniel@codeyourfuture.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 📋 Backlog

Development

Successfully merging this pull request may close these issues.

2 participants