Reviewing as Hana Petrova (external)
External reviewer · hana.petrova@example.com
External contactBlind review
DevFlow Conf 2027 — Round 1
AI EngineeringInfrastructure & ScaleProduct & Practice
5 / 18 doneLast active 3 Aug 2026 at 22:30
- From Notebook to Nine-Nines: Productionising MLTo reviewInfrastructure & ScaleProduct & Practice
- Evals as a Product Surface: Making Quality LegibleTo reviewAI Engineering
- Teaching Your Codebase to Answer QuestionsTo reviewAI EngineeringAgents & Tooling
- The Economics of Context WindowsTo reviewInfrastructure & ScaleAI Engineering
- Fine-Tuning Is a Data Problem, Not a Model ProblemTo reviewAI Engineering
- Human-in-the-Loop Without Being Human-HostileTo reviewProduct & Practice
- Structured Output Is a Distributed Systems ProblemTo reviewAI EngineeringAgents & Tooling
- Shipping Agents That Don't Melt Down at 3 A.M.To reviewAgents & ToolingInfrastructure & Scale
- Cutting Inference Costs 70% Without Touching the ModelTo reviewInfrastructure & Scale
- A Practical Taxonomy of LLM Failure ModesTo reviewAI Engineering
- Guardrails at the Edge: Safety Without the Latency TaxTo reviewInfrastructure & Scale
- Vector Databases: Choosing One You Won't RegretTo reviewAI EngineeringInfrastructure & Scale
- Zero-Downtime Model RolloutsTo reviewInfrastructure & Scale
Structured Output Is a Distributed Systems Problem
AI EngineeringAgents & ToolingTalkAdvanced
Schema drift, partial responses and retries: why validating model output belongs in the same mental model as any other unreliable network call.
Speaker details are hidden for this round. Score the proposal on its own merits.
From the application
- Have you presented this talk before?
- No
- Do you need travel support to attend?
- No
Your scorecard
Scoring as Hana Petrova (external).
Score 1-5 on relevance, novelty and the speaker's evidence for their claims. Most solid talks land at 3 or 4; reserve 5 for something you would rearrange your day to see. Leave a comment for anything you score 2 or below — we pass anonymised feedback back to submitters.
Shared with the programme team on the submission page. Never sent to the speaker automatically.