Upgrade to Pro — share decks privately, control downloads, hide ads and more …

VibeKode Berlin 2026 - Hard Guardrails, not Vib...

Sponsored · SiteGround - Reliable hosting with speed, security, and support you can count on. →

VibeKode Berlin 2026 - Hard Guardrails, not Vibes - How I build a High-Quality SaaS Product Solo

Slides for my talk at VibeKode Berlin, November 19th, 2026

Sebastian Gingter

November 19, 2026

Transcript

29 slides
  1. Hard guardrails, not vibes How I built a high-quality SaaS

    product solo A rule as text is a request. A rule in the compiler is a law of nature. VibeKode Berlin 2026 · Nov 19, 2026 Sebastian Gingter [email protected] Developer Consultant
  2. Hard guardrails, not vibes VibeKode Berlin 2026 Sebastian Gingter Developer

    Consultant @ Thinktecture AG ▪ Generative AI in business settings ▪ AI-driven developer productivity & software quality ▪ All things .NET ▪ Microsoft MVP for .NET [email protected] https://www.thinktecture.com
  3. Hard guardrails, not vibes VibeKode Berlin 2026 January 2026 vs.

    today Jan 10, 2026 · internal review November 2026 ~15 % test coverage 8,500+ tests 0 null-forgiving ! 4 custom Roslyn analyzers 134 architecture tests 440 merged pull requests 0 / 76 controller actions tested 34 / 37 POST actions without CSRF Verdict: “NOT production-ready” Same developer. Same agents. A different environment.
  4. Hard guardrails, not vibes VibeKode Berlin 2026 For archers: register

    yourself and others Wizard: several archers, class per archer, free places per group
  5. Hard guardrails, not vibes VibeKode Berlin 2026 For organizers: the

    back office Registrations per target and position: class, distance, face Payments: transfer codes in, reminders out, refunds tracked Payment flow Request with code + GiroCode → bank transfer → organizer enters codes → reminder, overdue, refund Reminder with GiroCode
  6. Hard guardrails, not vibes VibeKode Berlin 2026 Why it is

    not CRUD: targets and faces 122 / 80 cm 60 cm 40 cm Triple spot Vegas triple Mixed butt A–D share one face A+C | B+D one per archer vertical strip triangle 40 + Vegas + 2 strips 1 distance Faces must fit Positions A–D Waitlist, rebooking per target spatially on one butt reservable per class if face + distance fit 8 face types · 3 setup modes · waitlist, rebooking, late registration on top
  7. Hard guardrails, not vibes VibeKode Berlin 2026 How big is

    it? production 76,380 unit tests integration tests E2E tests Domain 43,111 · 126,381 lines of production code Web 202,059 31,181 · 64,332 Cli 1,225 · 2,318 Infrastructure 384 · 263 lines of test code Plus Aspire host, analyzers, architecture tests and test utilities. 1 : 2.6 Bitwarden server (password manager, C#) — 2.5× our size · tests 1 : 1.6 production : tests Redmine (project management, Ruby) — about our size · tests 1 : 1.2
  8. Hard guardrails, not vibes VibeKode Berlin 2026 Fail gallery from

    the January review The lost event var expiredEvents = new List<IDomainEvent> { new MagicLinkExpiredEvent(…) }; return CommandResult .Failure("Der Code ist abgelaufen…"); // expiredEvents: never used Event sourcing silently loses a fact. The apology loop foreach (var remaining in _members.Where(m => m.Position > removed)) { // TeamMember doesn't have // UpdatePosition, so we // work around this // In real implementation, // you'd want to handle… } A plausible shape with nothing inside. The unreplayable clock public bool IsOverdue => !IsPaid && DateTimeOffset.UtcNow > DueDate; Same events, different answer tomorrow.
  9. Hard guardrails, not vibes VibeKode Berlin 2026 I wrote it

    louder. It did not help. Use relative paths. Do NOT use absolute paths. NEVER use absolute paths! Zero exceptions. Do NOT generate code that uses DateTime.Now — use TimeProvider injection instead. 52 → 87 ! in production code that month Use TimeProvider instead of DateTime.Now or DateTime.UtcNow. Instructions: 49 → 671 lines (×14) 21 → 33 DateTime.Now, same month A rule as text is a request. A rule in the compiler is a law of nature.
  10. Hard guardrails, not vibes VibeKode Berlin 2026 The first hard

    guardrail <!-- Directory.Packages.props, Mar 7, 2026 (0adc360cb) --> - <PackageVersion Include="Microsoft.EntityFrameworkCore.InMemory" Version="10.0.3" /> 5 1 0 sentences of prose before deleted line violations since: it no longer compiles
  11. Hard guardrails, not vibes VibeKode Berlin 2026 The enforcement ladder

    asks enforces Impossible Architecture test CI gate Analyzer Git hook Script Skill Prose
  12. Hard guardrails, not vibes VibeKode Berlin 2026 Act II Guard

    the guards Learnings — and how they are enforced
  13. Hard guardrails, not vibes VibeKode Berlin 2026 Quality gates —

    per method, not per project 100 % ≤ 10 ≤ 10 branch coverage, changed files cyclomatic complexity CRAP score per method Hook + CI gate prose Mar 18 → enforced Mar 30
  14. Hard guardrails, not vibes VibeKode Berlin 2026 Still 99 %

    — and the push is blocked // added for this slide, no tests public static decimal Calculate(int age, string bowType, bool isClubMember, bool isLate, bool isSecondStart, bool isHandicap, int startsInSeason) { var fee = 15m; if (age < 12) fee = 8m; else if (age < 18) fee = 10m; else if (age >= 50) fee = 12m; if (bowType == "Compound" && age >= 18) … else if (bowType is "Langbogen" or …) … if (isClubMember && !isHandicap) fee -= 3m; if (isLate) fee += age < 18 ? 2.5m : 5m; if (isSecondStart) fee = startsInSeason > 3 … return fee < 0 ? 0 : fee; } $ ./scripts/quality-verification.ps1 Methods with CRAP Score > 10 LegacyFeeCalculator.Calculate CC=28 CRAP=812 Coverage vs. Baseline Branch: 99.59 % → 99.28 % (−0.31 pp) Quality gates FAILED. Fix issues before pushing.
  15. Hard guardrails, not vibes VibeKode Berlin 2026 BSC0001: no “!”,

    no exceptions May 3 BSC0001 ships — with a carve-out for = null! May 4 Review calls it an “escape hatch” → removed May 6 Same PR: the agent sneaks four null! back in — into tests, still exempt until May 19 Aug 14 Blind spot: Razor views — 236 ! in 58 views The fence ends where you cannot see it. 877 → 0 production 49 · tests ~828
  16. Hard guardrails, not vibes VibeKode Berlin 2026 Four analyzers BSC0001

    No ! BSC0002 CancellationToken required The null-forgiving operator is a build error — in code, tests and Razor views. Every async method takes a token as its last parameter. since Jul 28 since May 3 BSC0003 Async suffix BSC0004 No assertion behind ?. Every async method name ends in Async — controller actions too. subject?.Value.Should()… checks nothing when subject is null. since Jul 28 since Jul 29 Plus 1,141 rules I did not write — every warning is a build error Sonar 468 · Microsoft .NET 324 · code style 121 · xUnit 90 · ASP.NET Core 51 · SecurityCodeScan 32 · EF Core 3
  17. Hard guardrails, not vibes VibeKode Berlin 2026 Known CVEs break

    the build dotnet build CI locally, before any push on every push NuGet audit — every known CVE, direct or transitive, down to severity low gitleaks — secrets in every commit, Markdown included SDK check — an SDK with a known CVE or out of support (.NET 11) SecurityCodeScan + Sonar — SQL injection, XSS, weak crypto, hard-coded secrets OSV-Scanner — a second, independent vulnerability database Trivy · DevSkim — container config · insecure source patterns Dependabot — weekly update PRs for NuGet and Actions Nov 10: main turned red without a code change — two new advisories. The gate working as designed.
  18. Hard guardrails, not vibes VibeKode Berlin 2026 July: what the

    guardrails bought 24.5 6.3 1.2 h 3.2 commits / active day PRs / active day median PR lifetime parallel branches Dec – May: 12.8 Dec – May: 2.8 The autonomous loop: /autoissue /issue Gates Draft PR average · before: ≤ 2.3 only if the rebase changed code Copilot review Fix or refute Rebase Auto-merge Worktree or sandbox per agent · local self-hosted runners · 2.9 review rounds per PR on average Merge watch /cleanup
  19. Hard guardrails, not vibes VibeKode Berlin 2026 Act III The

    safety net Impossible by design — and senses for the agent
  20. Hard guardrails, not vibes VibeKode Berlin 2026 134 architecture rules

    — each with a canary NetArchTest + Mono.Cecil 1.x DbContext access 2.x Dependency direction 3.x Naming & sealed 4.x Forbidden APIs 5.x Cancellation tokens // Never called. Exists only to be found. internal static class ForbiddenApiCanary { public static DateTime ReadsClockViaNow() => DateTime.Now; public static HttpClient ConstructsHttpClient() => new(); public static TimeZoneInfo ReadsServerZone() => TimeZoneInfo.Local; } 6.x Test-project inventory 7.x Docs = code The detector must flag every canary — otherwise the rule fails instead of staying green while checking nothing: a false negative.
  21. Hard guardrails, not vibes VibeKode Berlin 2026 Top of the

    ladder: physically impossible Web Cli MVC + API second host “… a rule a test asserts rather than a fact the compiler knows.” ADR-0019, on what the split replaced Domain plain Microsoft.NET.Sdk — no ASP.NET Core 839 files Infrastructure zero package or project references moved as a pure move
  22. Hard guardrails, not vibes VibeKode Berlin 2026 Give the agent

    senses, not just rules Aspire MCP + skill Resources, logs, traces No browser needed Playwright / DevTools Drive the real UI Console, network # a CLI as second host — built for the agent $ cli query GetFederationList $ cli describe CreateFederation $ cli command CreateFederation \ --json '{"name":"DSB","abbreviation":"DSB"}' “give the AI better means to diagnose issues that are based on faulty data in the DB” Roslyn MCP Memory & skills Symbols, references Far fewer tokens ~100 entries, 30 skills Corrections captured once Issue #297 No MVC reference — proves the layering every build
  23. Hard guardrails, not vibes VibeKode Berlin 2026 What guardrails don't

    catch Missing rules Whole-system flaws Code that doesn't exist Manual run, August: 2 high-severity bugs, all tests green — age and gender limits not checked, late registration not blocked. Review, October: 108 findings — e.g. stored DOM XSS in inline JS. “Unusually mature … not ready for go-live.” 100 % branch coverage only measures the code that was written.
  24. Hard guardrails, not vibes VibeKode Berlin 2026 Five rules 1

    Every repeated correction becomes a gate. 2 Gates need canaries. 3 Make the right way the easiest way. 4 Give the agent senses, not just rules. 5 Humans decide what. Machines enforce how. Prose is where a rule starts, not where it lives. A check that finds nothing might be blind. Test helpers, CLI, MCP — agents copy what is easy. Logs, traces, a browser, the real database.
  25. Hard guardrails, not vibes VibeKode Berlin 2026 Where do your

    rules live? asks enforces Impossible CI gate Analyzer Git hook Script Skill Prose “Pretty please” 671 lines of CLAUDE.md 21 skills testing patterns migrations UI, views, e-mails coverage.ps1 quality gate: CC, CRAP format.ps1 run-checks pre-push CSharpier dotnet format markdownlint commit-msg: English 1,145 rules BSC0001–4 Sonar, SecurityCodeScan .NET, ASP.NET Core, EF Core, xUnit NuGet audit, SDK CVEs warnings = errors every push build + all tests coverage regression hotspot gate gitleaks, OSV, Trivy, DevSkim Copilot review light-CI guard Architecture test InMemory provider removed 134 rules assembly split (ADR0019) no reference, no dependency + canaries forbidden APIs layering, naming action names in IL docs = code

More Decks by Sebastian Gingter

Other Decks in Programming