WeAreDevelopers Europe 2026 - my takeaways in one sentence
By Xavier Sala, 10 July 2026
My takeaway from WeAreDevelopers Berlin 2026 in one sentence:
The software development lifecycle we have been using for the last 20 years has officially changed.
Here are some thoughts and quotes that really got me thinking.
From Przemysław Ładyński - Building Modern Distributed Systems using Less AI Tokens
- AI doesn’t replace engineering! Lets be a Software Engineer(ing Coordinator)
- AI follows either your engineering standards or the Internet average.
- Knowledge belongs in the repository and is expressed via policies, rules, skills (ie. to create diagrams with draw.io in the repository, etc.) and specs (architecture, code-style, security, user geatures, etc.).
- How AI understand knowledge you provided can be tested with evals/datasets and graders.
- Your competitive advantage is no longer creating high quality systems but orchestrating the statistical machines (LLMs) to deliver it in the most efficient manner.
- Same prompt. Different rules. Different result. -> reduced code volume, inreases token efficiency, PR readability, change locality and context efficiency.
- Before the AI Revolution.
From Dana Lawson
- The new most used programming language: English
- The builder is no longer just a developer.
- The rise of agentic development - intent as the input and working softeare as the output.
- Autonomouns development loops - CI/CD evolves from a passive pipeline into a continious, agent-driven feedback loop.
- Traditional systems exposes endpoints. Agent-native systems exposes intent-level operations that agents can reason about.
- Request-Response to Event-driven - agents perform best when they can observe system behavior and act autonomously - not poll and wait.
- Trust & Safety in agentic systems. When agents can deploy code, provision infrastructure, and modify production - trus isn’t optional. It’s the foundation.
From Thomas Dohmke - The agentic assembly line
- Jurassic era of the AI coding.
- More code is generated by AI agent -> increased numnber and changes in each PR.
- How to review inceased PRs and merge with confidence? by not logging only the diffs but also scores for risks, confidenly, etc.
- More AI changes are accepted without human review.
- New SDLC from intent to the outcome by merging without even openning a diff.
From Julian Wood - From vibe coding to viable code with spec-driven development
- AI is changing software: from completing development tasks to now proven correct, team-scale and iterative development.
- Spec-driven development:
- Persistent - lives in your repo as markdown
- Iterative
- Verifiable
- Shareable - git-versioned, PR-reviewable
- Vibe coding is still fine for some parts.
- Separate the design from the build of a project.
- Use AI to generate the code that fulfills your documented specifications.
- A spec formulates your intent.
- Updating your specs triggers the regeneration of code.
from Liran Hason - What 500+ Production Environments Taught Us About Shipping AI Agents
- Treat every model upgrade like a migration - not just as changing a string.
- A new model is a new teammate.
- Invoices will arrive.
- Check cache ratio not only number of tokens.
- UX matters - show to the user what the agent is doing - this is the line between users complaining about slowness and stop getting complaints.
Recap
-
I still have my own checks in regards to,
- How this new software development lifecycle is being gradually implemented accross differente industries (e.g. enterprise companies, startups, regulated sectors, etc.)
- the associated AI costs
-
Without a doubt, we are entering into an amazaing new era for the software systems.
-
Thanks to all the speakers for sharing your experiences and knowledge.
-
Thanks to WeAreDevelopers for such a great organisation and leading by example.
-
My recorded presentation in WeAreDevelopers World Congress 2026 Europe - Virtual Stage AI Agents & Agentic AI