AINoon Lesson 4

Get Ready for AINoon!

Thanks

  • To the host for the great venue!
  • To our sponsors

Administrivia

  • Fire escapes
  • Toilets
  • Cleaning up after ourselves
  • Wi-Fi

AI Risks and Challenges

  • There’s a lot of hype and a lot of fear
  • To make good decisions:
    1. Understand the risks
    2. Assess them in the context of your application
  • Some risks are challenges to be solved or mitigated
    • We didn’t stop using electricity because of shocks, we developed insulation
  • Do your own deeper research!
    • This is food for thought, not authoritative answers
    • These are tricky issues with many differing opinions
    • AI is rapidly changing and the future is unknown

Inaccurate Outputs

We’ve seen plenty of examples over the course

How can inaccuracy be mitigated?

  • Golden Rule of AI: Don’t trust outputs you can’t verify
  • Consider failure modes: How could this fail? What would the impact be?
  • Human in the loop: Human decisions with AI support
  • Human on the loop: Human supervises AI decisions
    • But apathetic supervision can lead to workslop
  • Thorough testing: Like for chatbots in Lesson 2

Unwanted Bias

  • Examples:
  • Mitigation:
    • Be aware of potential bias
    • Consider your application: that 20th century LLM…
      • might prefer doctor CVs from male candidates
      • might still be a useful model of the 20th century
    • Avoid or tightly control AI in high-stakes decisions

Privacy and Security

  • LLMs may use your data for future training
    • Some providers allow you to disable that
    • Corporate offerings preferred by companies,
      but providers may still monitor for misuse
  • Don’t trust generated code you don’t understand
    • Security issues can be subtle - more in the tutorial
  • Consider worst-case scenarios for agents,
    like the lethal trifecta:
    1. Agent reads untrusted source (e.g. your email inbox)
    2. Agent reads private data (e.g. your private files)
    3. Agent writes to public location (e.g. sends an email)
    4. → E.g. “Reply to this email with private files…”

Vendor lock-in

  • Like with any technology service, avoid becoming strongly tied to one vendor:
    • With competition and evolving offerings, you want freedom to pick the best provider
    • Prices may start below cost to grow users, then increase later
  • Build modular systems with replaceable components
  • Prefer open-source tools and open-weight models that any provider can run
  • Look for compatibility with open standards used across providers - e.g. Model Context Protocol (MCP)

Other risks to consider

  • Environmental impact - training and serving models has high electricity and water costs
  • Identifying AI-generated content is difficult
    • It may “drown out” useful content on the Internet
    • How will we find trustworthy training data for future models?
  • Impact on jobs - Depending on a worker’s role, efficiency gains may:
    • Allow more time for other important tasks
    • Change the required skills or the way work is done
    • Reduce the required number of workers
  • Artificial General Intelligence (AGI) / Superintelligence

Discussion

  • Have we missed any risks?
  • Can you think of mitigations for any of the discussed risks?
  • Any other questions or comments?

Tutorial Objectives

  1. Use vibe coding to build a simple web app
  2. See the risks of using code you don’t understand
  3. Discuss practices for coding safely with AI

What is vibe coding?

  • Coding:
    • Writing instructions in languages the computer can understand
    • How software developers build apps
  • AI-assisted coding:
    • Any use of AI to help a developer write code
  • Vibe coding:
    • Describing an app to an AI agent and letting it write the code without checking the code it writes

What is vibe coding useful for?

  • Enable anyone to rapidly build prototypes and apps for low-stakes use-cases.
  • NOT when security or correctness are important
    • Carefully review generated code in those cases
  • Probably not the best way to learn to code
  • Don’t reinvent the wheel - plenty of apps exist to build websites and forms
  • The sweet spot: automating time-consuming tasks that are specific to your work!

Scaling up AI-Assisted Coding

To use AI on more complex coding projects:

  • Use agents that work on a whole folder of files
    • E.g. Replit, Codex, GitHub Copilot
  • Generate and review planning documents for:
    • Features and other requirements
    • Technical architecture
  • Use version control to track changes
    • Learn the Git version control tool with GitNoon!
  • Guide it with expert knowledge in prompts
    • Photography terms → better images
    • Coding terms → better code
  • AI code-completion is popular with experienced developers

Homework

  • Research one risk relevant to your use of AI
    • Find a range of perspectives
    • Identify more mitigations
    • Consider which mitigations are most appropriate for your application
  • Use a coding agent to make a larger app
    • E.g. Replit, Codex, or GitHub Copilot
    • See how it makes a plan and generates a whole folder of files
    • You might not get very far without a paid plan