JevMade Sign in
← Back to videos

JevMade field notes / Video guide

Why TypeSafe puts decisions inside ordinary software

TypeSafe co-founder Diogo Almeida explains why Jev returns bounded judgments instead of writing replies, and argues for combining those decisions with software rules.

Original by ModalGetting startedBeginner13 min 10 sec Published

Before you press play

What you’ll find in the video

  1. Almeida proposes putting bounded decisions inside ordinary software, rather than asking an agent to invent each next step.
  2. His distinction between assistance and automation is an argument about how models are trained, not a demonstrated universal rule.
  3. A benchmark chart and adoption claims are part of the pitch. They do not replace tests on the tasks your software needs to handle.
Worth knowing

Vendor conference talk, not an independent performance or adoption audit. The speaker's capability, usage and infrastructure claims remain attributed statements. The talk's criticism of benchmarks is an opinion, not a reason to omit task-specific tests. It does not establish safe autonomous decisions in high-stakes work.

Why TypeSafe puts decisions inside ordinary software

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.