Post on: 2026-6-15Last edited: 2026-6-15Words 248Read Time 1 min

type
Post
status
Published
date
Jun 15, 2026
slug
bluedot-ai-safety-certificate
summary
A short note on completing BlueDot Impact AI Safety Fundamentals, receiving the certificate, and sharpening my direction toward agent safety evals, tool-use safety, and reliable AI infrastructure.
tags
AI
AI Safety
Reflection
Recommend
category
Essays
icon
password
paired_with
3801d487-a2a1-81e8-88c6-c69a7115aa49
lang
translation_locked
source_hash
💭
I recently completed BlueDot Impact's AI Safety Fundamentals course and received the certificate. This was a small milestone, but it helped me make a bigger shift: from simply building useful AI applications toward asking how those systems fail, how to evaluate them, and how to make tool-using agents safer before people depend on them.

What I Took From The Course

BlueDot gave me my first structured map of AI safety. Before the course, I had already built RAG and full-stack AI projects, but I did not have a clean vocabulary for the failure modes I kept seeing: wrong retrieval, missing permissions, over-trust in fluent answers, weak evaluation, and unclear deployment boundaries.
The course helped me connect those problems to larger safety ideas: specification, evaluation, deployment risk, AI control, interpretability, and scalable oversight. I came away less interested in "AI app building" as a standalone identity and more interested in reliable AI infrastructure.

Where It Points Me Next

The direction I want to keep pushing is agent safety evaluations for tool-using systems. My current project, daily-admin-agent-security-eval, is a small AgentDojo-compatible eval suite for daily-admin workflows. It tests whether agents can complete useful tasks while treating retrieved app content as untrusted data.
That feels like the right wedge for me: concrete enough to build, safety-relevant enough to matter, and close to the systems I already know how to ship.

Bottom Line

Finishing BlueDot is not the endpoint. It is a marker that my direction is getting sharper: agent evals, prompt injection, tool-use safety, access control, and reliability for AI systems that touch real workflows.
The certificate matters less than the change in frame. I do not just want to build AI systems that work in demos. I want to understand how they fail when the environment is messy, adversarial, and full of permissions.

References


Loading...
Next.js or Remix: What OpenAI’s Migration Suggests

Next.js or Remix: What OpenAI’s Migration Suggests

Using OpenAI’s move from Next.js to Remix as the case study, this post compares the two React frameworks around data loading, server rendering, hydration costs, and when each one is a better fit.


Distinguishing Saints from Sycophants and Schemers

Distinguishing Saints from Sycophants and Schemers

AI safety requires distinguishing saints from sycophants and schemers during training.


Announcement
This site is still updating…