Uploaded April 2026 | Updated September 2026, 3 weeks ago
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
We don’t lose engineering velocity because we can’t write code fast enough, we lose it because every change adds hidden complexity. Over time, that complexity turns delivery into a high‑risk activity, slows teams down, and makes even small changes feel dangerous. This effect is amplified in large, regulated organizations where autonomy, safety, and speed must coexist.
In this keynote, we’ll explore how we approach scalable engineering as a system, not a set of best practices. You’ll see how a distributed engineering model—spanning customer-facing teams, platform capabilities, and core engineering functions can still behave coherently at scale.
We’ll dive into how self‑service, productized, hardened‑by‑default platforms, combined with guardrails and policy‑as‑code, reduce cognitive load and eliminate entire classes of failure. The outcome isn’t more process or bureaucracy, it’s less friction: clearer ownership, safer change, faster feedback, and an engineering value chain that continues to scale as the organization grows.
If you care about shipping faster without breaking things, this talk is for you.
Please subscribe to our YouTube channel @ youtube.com/@DevoxxForever
Subscribe to LinkedIn @ linkedin.com/company/voxxed-days-amsterdam
Follow us on Twitter @ twitter.com/voxxedamsterdam
We don’t lose engineering velocity because we can’t write code fast enough, we lose it because every change adds hidden complexity. Over time, that complexity turns delivery into a high‑risk activity, slows teams down, and makes even small changes feel dangerous. This effect is amplified in large, regulated organizations where autonomy, safety, and speed must coexist.
In this keynote, we’ll explore how we approach scalable engineering as a system, not a set of best practices. You’ll see how a distributed engineering model—spanning customer-facing teams, platform capabilities, and core engineering functions can still behave coherently at scale.
We’ll dive into how self‑service, productized, hardened‑by‑default platforms, combined with guardrails and policy‑as‑code, reduce cognitive load and eliminate entire classes of failure. The outcome isn’t more process or bureaucracy, it’s less friction: clearer ownership, safer change, faster feedback, and an engineering value chain that continues to scale as the organization grows.
If you care about shipping faster without breaking things, this talk is for you.
