Apply Now
Agentic Engineering 101 | Parsity
Saturday, December 12 · 10am until the questions run out · $495, no call needed
Sat, Dec 12 10am–ish to 4pm–ish $495 For coders, any language

Learn to actually use these tools in one Saturday.

Pre-AI, you learned a new skill from Udemy, Stack Overflow, and the docs. Now your company handed you a Claude subscription, one YouTuber is yelling that this changes everything, and another is yelling that you can't trust any of it. Hyperbole is great for engagement and terrible for your career.

The truth is boring: things have changed less than you think, and more than you think, at the same time. The engineering judgment you always needed still applies. You just need a different way of using the tools than whatever's going viral this week.

$495

One Saturday · no call, no six-week commitment · sign up and you're in

December 12 only, for now. No pitch call — it's too cheap to bother either of us with one.

This is not a beginner class, and it's not a 10x miracle either.

  • You already write and ship software for a living, or close enough that nobody would question it
  • You've used Claude, Cursor, Copilot, or Codex enough to have opinions about them
  • You have a laptop and an active AI coding tool subscription. Free tiers are fine
  • You want to get measurably better with these tools, not just faster for one afternoon
If you're already cracked with these tools: seriously, save your $495. This class will bore you.
Set your baseline

We're not promising you'll 10x by Monday.

We start by looking honestly at where you actually are with these tools today. Most people leave at least 30% more effective, not because we handed you a magic prompt, but because you stop doing the things quietly wasting your time.

You don't trust the output

So you re-read every line like it's a stranger's PR. We'll show you when that instinct is right, and when it's costing you nothing but time.

You don't have a system

Just vibes and whatever prompt worked last time. We'll give you an actual repeatable workflow, and the guardrails to keep it from turning into chaos.

Your team can't agree

What "good" looks like when a model writes the first draft is still a live argument at most companies. You'll leave with a workflow you can actually explain and defend.

The one day

One Saturday. One real workflow.

No toy examples. You spend the day inside one company's actual, messy production codebase.

The company: Driftwood Logistics

  • A logistics company we built for this — not a repo swept clean for a demo. Node/Postgres backend, a Rust service, Python scripts, the works.
  • Docs split across three places that don't fully agree with each other. Part of the job is figuring out which one to trust.
  • A contractor who shipped a chunk of it and is long gone. Sound familiar?
  • At least one bug currently live that nobody's caught yet. You might be the one who does.
It's fictional. Nothing about the mess is staged for the sales page — it was actually built, and actually tested, before this page went up.
Morning

The mental model

Starting at 10am
  • Your actual baseline. A quick, honest look at how you're using these tools today, no judgment.
  • Why "10x" is mostly marketing. And what a real, durable gain actually looks like.
  • Agent vs. autocomplete vs. chat. The mental model for picking the right one, and when all three are wrong.
  • Guardrails. How to keep an agent from quietly ballooning the scope of what you asked for.
By lunch you have language for what you're actually doing right and wrong.
Afternoon

The workflow

Until the questions run out
  • Real tickets, not a demo. A bug report, a vague feature ask, something that needs investigating before it needs fixing — the actual shape of the job.
  • Reviewing output like an engineer. Not rubber-stamping it because it compiled.
  • Avoiding slop while still actually moving faster, not slower.
  • Bringing it back to your team. How to show this on Monday without becoming the office's cautionary tale.
You leave with a workflow, a certificate, and a two-week follow-up to make sure it stuck.
Why this, not another tutorial

This isn't a tools tutorial, and it isn't hype or fear either.

It's judgment, not buttons

You already know where the buttons are. This is what to trust, what to check, and what you never let an agent touch unsupervised.

Neither extreme is right

Half the internet says AI writes all your code now. The other half says never trust it. Both make for good engagement and bad career advice.

It's the React moment, again

When React showed up, courses were everywhere, plenty of them good, and a whole generation of developers leveled up together in public. This is that, for agentic engineering.

Your company probably bought you the tools and forgot to explain how to actually use them. That's the gap this Saturday closes.
Sign up and you're in

One Saturday, $495.

Cheap enough that we skip the sales call. You know if this is for you from the page above.

$495
Saturday, December 12 · 10am until the questions run out
  • A full day building one real, end-to-end agentic workflow
  • A repeatable process and guardrails, not just a prompt
  • A certificate when you're done
  • A two-week follow-up to make sure you actually implemented it
  • Small room, real Q&A, not a webinar
Save My Seat, $495
Sign up, pay, you're in. No call needed. Your employer can probably expense this — ask for an invoice at assistant@parsity.io.
Who runs it

Meet your instructor.

Brian Jenney

Brian Jenney

Founder, Parsity

Brian has built and led production AI systems, including complex RAG pipelines and production agents, at two companies with very different products. He also runs Parsity's mentor-led AI Engineering Program.

Light on theory, heavy on practical judgment. The mistakes you'll avoid on Saturday are ones he's already made in production, on someone's payroll.

Continue?

Questions we get.

What do I need to bring?

A laptop, and an active subscription to Claude Code, Codex, or even GitHub Copilot if you're still holding onto 2023. Free tiers are fine.

What am I actually working on all day?

Driftwood Logistics — a fictional logistics company we built specifically for this, so it feels like joining a real one: a Node/Postgres backend, a Rust service, sparse and sometimes contradictory docs, real bugs seeded in on purpose. You work real tickets against it — a bug, a vague feature request, something that needs investigating — not a cleaned-up tutorial repo.

I'm already really good with these tools. Should I come?

Honestly, probably not. If you're not copying and pasting between chats, you don't double-guess every line, and your team already agrees on what good looks like, skip this one.

Is this going to teach me to replace my team with agents?

No. If you're looking to build a software factory, automate yourself out of a job, or become a full-time meat proxy just forwarding tickets to a model, look elsewhere. This is for engineers who want to get better, not disappear.

Do I need a specific language?

No. This is for coders. The language you use doesn't matter, the judgment does.

Do I need to book a call first?

No. It's $495 for one Saturday, a call would cost more than it's worth to either of us. Sign up, pay, show up.

What if I can't make December 12?

Email assistant@parsity.io and we'll let you know when the next one's scheduled.

Is this the same as the mentor-led program?

No, different thing. That's six weeks of 1:1 mentorship for $1,997 if you want to actually become an AI engineer. This is one Saturday to get dramatically better at using the tools you already have. Check out the mentor-led program here.

Ready player one

Your company bought you the tools and forgot to explain how to use them.

You may be too young to remember, but when React came out, courses were everywhere. A lot of them were actually good. A whole generation of developers leveled up together, in public, in real time. This is that, for agentic engineering.

▶ ▶ ▶ PRESS START ◀ ◀ ◀
Saturday, December 12. No call needed. Questions? assistant@parsity.io