NDC Conferences
Generative AI functions as an amplifier that makes deep technical expertise and rigorous human verification more critical to enterprise stability than ever before.
AI-assisted summary of For God's sake, keep the nerds! - Stein Inge Morisbak - NDC AI 2026 — original source. Check the original for full context.
Source published:
Key ideas
- A six-week pilot of Claude Code across 180 developers at Tet Digital resulted in 90% of engineers reporting increased productivity. (0:06)
- Productivity gains for developers do not always translate to faster delivery, as coding speed is often not the actual bottleneck in complex organizational environments. (9:12)
- Tet Digital implemented a mandatory three-step rollout process (training, team agreement, and signed declaration) rather than an unconstrained release. (15:22)
- AI functions as an amplifier: it elevates the performance of already disciplined, high-performing teams while exacerbating existing dysfunctions in struggling teams. (4:33)
Detailed notes
## Background This talk, titled "For God's sake, keep the nerds!" and presented by CTO Stein Inge Morisbak, was published on the NDC Conferences YouTube channel on July 1, 2026. The presentation explores the impact of AI on software development teams, detailing a six-week pilot program at Tet Digital and arguing for a deliberate, guardrail-focused approach to adopting AI coding assistants.
## TL;DR Stein Inge Morisbak argues that AI serves as an amplifier for engineering teams, magnifying both high performance and existing dysfunctions. Through a pilot study involving 180 developers, he demonstrates that while AI significantly boosts subjective productivity, it does not solve core organizational bottlenecks like meetings or complex dependencies. Ultimately, he posits that as AI handles routine syntax, the human role shifts toward quality control, orchestration, and critical verification, making deep technical expertise more essential than ever.
## Atmosphere & style The presentation carries the candid, weary, and slightly humorous tone of a seasoned tech leader addressing his peers at the end of a long conference day. Morisbak balances executive-level pragmatism with a grounded, "in the trenches" perspective, using lighthearted imagery—like his AI-generated gymnastics photo—to contrast with the serious risks of enterprise system failure. The overall feeling is one of measured, cautious optimism that prioritizes human craftsmanship over the allure of automated speed.
## Bulletin - [00:06](https://www.youtube.com/watch?v=Fda_-l6HB18&t=6s) A six-week pilot of Claude Code across 180 developers at Tet Digital resulted in 90% of engineers reporting increased productivity. - [09:12](https://www.youtube.com/watch?v=Fda_-l6HB18&t=552s) Productivity gains for developers do not always translate to faster delivery, as coding speed is often not the actual bottleneck in complex organizational environments. - [15:22](https://www.youtube.com/watch?v=Fda_-l6HB18&t=922s) Tet Digital implemented a mandatory three-step rollout process (training, team agreement, and signed declaration) rather than an unconstrained release. - [04:33](https://www.youtube.com/watch?v=Fda_-l6HB18&t=273s) AI functions as an amplifier: it elevates the performance of already disciplined, high-performing teams while exacerbating existing dysfunctions in struggling teams.
## Key takeaways - [04:33](https://www.youtube.com/watch?v=Fda_-l6HB18&t=273s) AI is best understood as an amplifier of existing organizational practices, not as a replacement for foundational technical skill. - [01:17](https://www.youtube.com/watch?v=Fda_-l6HB18&t=77s) Deep technical understanding is the essential insurance policy for preventing system collapse when AI generates code at high speed. - [11:12](https://www.youtube.com/watch?v=Fda_-l6HB18&t=672s) Human oversight is non-negotiable; engineers must shift their role from manual coders to orchestrators who verify and critique AI-generated output. - [09:12](https://www.youtube.com/watch?v=Fda_-l6HB18&t=552s) While developers report high productivity, there is a perceptual gap where product leads may see little to no change in actual shipping velocity or quality. - [11:12](https://www.youtube.com/watch?v=Fda_-l6HB18&t=672s) Generative AI can pose a threat to junior skill acquisition if senior engineers do not prioritize active mentorship and manual code reviews. - [00:06](https://www.youtube.com/watch?v=Fda_-l6HB18&t=6s) Security must be built directly into the agent’s workflow via hooks and standards rather than relying solely on developers catching errors manually. - [17:04](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1024s) Tet Digital’s security and usage policy was distilled into three simple rules: Human Responsibility, Confidentiality, and Using Your Head. - [11:12](https://www.youtube.com/watch?v=Fda_-l6HB18&t=672s) Tooling maturation takes time; observed productivity gains increased from 83% to 90% as engineers adapted to the new workflow during the pilot. - [09:12](https://www.youtube.com/watch?v=Fda_-l6HB18&t=552s) The bottleneck for delivery is often found in meetings, team dependencies, and prioritization, which are areas where AI coding assistants provide no solution. - [17:54](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1074s) AI adoption requires a dedicated enablement team to handle training, monitor failure modes, and manage organizational guardrails. - [18:56](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1136s) Expanding AI to non-technical staff like designers requires caution, as they lack the foundational technical skills necessary to safely manage the generated output. - [20:54](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1254s) Success in AI adoption is driven by effective change management and team culture, not simply by purchasing software licenses. - [11:12](https://www.youtube.com/watch?v=Fda_-l6HB18&t=672s) The role of the developer is evolving to prioritize quality control and the design of practices that catch AI mistakes before they reach production. - [06:17](https://www.youtube.com/watch?v=Fda_-l6HB18&t=377s) AI-generated code quality can be inconsistent, with 10% of pilot participants reporting a decline in output quality, justifying the need for strict guardrails.
## Detailed walkthrough ### [00:06](https://www.youtube.com/watch?v=Fda_-l6HB18&t=6s) Mobility at Scale: Who Tet Digital Is
Taking the stage for the final session of the day at NDC AI in Oslo, Stein Inge Morisbak acknowledges the audience's fatigue, joking that he is the only thing standing between them and the evening's party and beers. Introducing himself as the Chief Technology Officer of Tet Digital, he provides context on what the company does and why its infrastructure matters. Tet Digital is a technology company developing public mobility solutions across Norway. It is jointly owned by the country’s largest regional public transport authorities: Ruter in Oslo, Skyss in Vestland, Agder Kollektivtrafikk, AtB in Trøndelag, and Østfold Kollektivtrafikk. Today, fully 69% of all public transport journeys throughout Norway run directly through Tet Digital's systems, meaning stability and correctness in their codebase are critical public infrastructure concerns.
[01:17](https://www.youtube.com/watch?v=Fda_-l6HB18&t=77s) Executive Hype vs. Developer Reality: The Insurance Policy
The media and executive landscape is flooded with euphoric claims regarding artificial intelligence. Stein Inge shares headlines from the Norwegian newspaper *VG*—featuring his own English translations placed onto the slides via AI—highlighting statements made by senior executives from prominent companies including Telenor, Schibsted, DNB, and Microsoft. While corporate leaders project massive productivity windfalls and celebrate the notion that technical barriers are evaporating, developers on the ground push back with legitimate caution regarding mounting technical debt and the surrender of code ownership. This caution is not mere pessimism or resistance to change; it is an act of engineering stewardship.
> “The developers, they aren't being negative, they are being responsible, because when AI produces code at enormous speed, deep technical understanding is the only insurance you have against total system collapse.” — Stein Inge Morisbak
- Executive optimism contrasts sharply with the lived realities of maintaining complex enterprise codebases. - The tension is not purely top-down: high-performing engineers also clamor for cutting-edge tools, fearing they will be left behind if held back by cautious leadership.
[04:33](https://www.youtube.com/watch?v=Fda_-l6HB18&t=273s) The AI Amplifier and Doing the Splits
Stein Inge invokes DORA’s research on software teams to define the core operational dynamic: AI functions strictly as an amplifier. It magnifies an organization's existing baseline—elevating the strengths of high-performing, well-disciplined teams while violently exacerbating the dysfunction of teams that are already struggling. Displaying an AI-generated image of himself wearing a festive Christmas sweater while physically stretched in a gymnastics split, he explains that it captures his exact role as CTO when kicking off their pilot just before the holidays. He is not split between management and engineers, but rather balanced between a shared organizational ambition to move faster and a shared responsibility to avoid driving the company over a cliff.
```mermaid flowchart TD accTitle: The DORA AI Amplifier Effect accDescr: Diagram illustrating how AI amplifies both high-performing teams and struggling engineering teams.
A["AI Tooling Adoption"] --> B["Amplifier Effect"]
subgraph Outcomes ["Organizational Outcomes"] B -->|"Strong practices & discipline"| C["High-Performing Teams<br/>(Strengths Amplified)"] B -->|"Poor practices & debt"| D["Struggling Teams<br/>(Problems Exacerbated)"] end ```
To resolve this tension, Tet Digital targeted their core asset: their code and the developers who work directly at the production boundary. Mistakes made here propagate immediately to end-users and represent the most expensive failures to remediate. Establishing robust guardrails at this critical juncture creates a safe foundation that the rest of the organization can build upon.
[06:17](https://www.youtube.com/watch?v=Fda_-l6HB18&t=377s) The Pilot Design: Scope, Productivity, and Quality
Tet Digital structured a six-week pilot utilizing Claude Code across 6 teams and 30 engineers, examining three core vectors: the impact on people and daily work, the concrete utility of Claude Code, and the requisite safety guardrails. In practice, Claude Code excelled at large-scale, repetitive tasks: bulk refactoring, test generation, documentation, and debugging. Conversely, it performed poorly on highly complex assignments tangled up in intricate cross-system and cross-team dependencies typical of enterprise mobility architectures.
Measuring the human and technical outcomes yielded clear shifts across the six weeks: - **Productivity:** A striking 90% of participating developers reported an increase in productivity, 10% observed no change, and zero developers reported a decline. - **Wellbeing:** 60% experienced improved wellbeing, while 40% saw no change. Significantly, multiple engineers had initially reported lower wellbeing at the outset before finding their footing. - **Mastery:** 65% reported a stronger sense of personal mastery, 25% saw no change, and 10% noted a decline. - **Code Quality:** Results were split. While 45% reported higher quality and 45% reported no change, 10% reported a distinct decline in quality—a statistic that underscores why rigid guardrails remain non-negotiable.
[09:12](https://www.youtube.com/watch?v=Fda_-l6HB18&t=552s) The Delivery Paradox: Writing Code Isn't the Bottleneck
When product leads were surveyed to determine if they observed the same productivity leap reported by their developers, the results revealed a stark perceptual gap. Product managers reported no noticeable change in overall delivery speed and very little difference in code quality, though they conceded that team quality was already quite high. What product leads did observe was simply that their developers felt significantly more productive and were visibly enjoying their day-to-day work.
This disconnect carried over into delivery confidence. Despite 90% of developers feeling more productive, many remained uncertain about whether their teams would hit their quarterly OKRs on schedule. Stein Inge emphasizes that this apparent contradiction exposes a fundamental truth about software engineering: producing lines of code is rarely the actual bottleneck in delivery. The actual delays in modern organizations stem from endless meetings, complex inter-team dependencies, ambiguous priority setting, and sluggish decision-making—none of which an AI coding assistant can solve.
[11:20](https://www.youtube.com/watch?v=Fda_-l6HB18&t=680s) Four Hard Lessons: Why We Keep the Nerds
Reflecting on the deeper takeaways from the pilot data, Stein Inge outlines four lessons that require human engineering expertise rather than algorithmic automation:
1. **AI makes mistakes:** Because generative models inevitably introduce errors, team discipline, code review practices, and verification processes matter more than ever. Rolling AI out to a team that already struggles does not fix its foundational issues; it compounds them. 2. **Reduced learning for juniors:** Heavy reliance on AI generation poses a serious threat to junior skill acquisition if senior engineers do not actively mentor them. Organizations must be deliberate about pairing, rigorous code reviews, and structured study to ensure foundational engineering skills still develop. 3. **Task transformation:** The engineer's day-to-day role is shifting away from manual syntax typing toward orchestrating, evaluating, and critically verifying AI outputs. Hands-on coding skill is no longer just the job itself; it is the prerequisite judgment required to determine if the generated output is safe to deploy. 4. **Tool maturation takes time:** Measuring developers at multiple intervals showed maturation in real time. Early on, 83% reported higher productivity, 13% saw no change, and 4% reported a decline. By the close of the pilot, that 4% decline dropped to zero, while higher productivity climbed to 90%.
> “People who can design the practices that catch AI mistakes, people whose technical debt doesn't erode, people who can verify AI output because they can read it, people who can drive maturation—and this is exactly the reason why we keep the nerds.” — Stein Inge Morisbak
[15:22](https://www.youtube.com/watch?v=Fda_-l6HB18&t=922s) A Deliberate Three-Step Rollout and Three Simple Rules
When expanding Claude Code from the 30-person pilot group to all 180 developers across the company, Tet Digital deliberately rejected an unconstrained "open tap" approach. Access was gated behind a formal three-step onboarding framework:
1. **Mandatory Training:** A targeted session centered on AI as an amplifier, security boundaries, and practical usage patterns (leaving specific tool syntax and prompting techniques to developer communities of practice). 2. **Team Leadership Agreement:** A team-wide consensus where leaders and engineers mutually commit to adopting the tool, acknowledging that the entire team shares collective responsibility for business and architectural outcomes. 3. **Signed Declaration:** An explicit confirmation that the developer has read, understood, and agreed to adhere to organizational usage guidelines.
Rather than authoring an unreadable corporate document, Stein Inge and his team distilled their entire security and quality policy into three memorable directives designed to fit comfortably in a single Slack message:
- **Rule 1: Human Responsibility.** You remain fully responsible for every single line of code generated by an AI; human review and output verification are strictly mandatory. - **Rule 2: Confidentiality.** Never input sensitive data, personal identifiable information (PII), credentials, secrets, or business-confidential logic into the model. - **Rule 3: Use Your Head.** If you are ever uncertain whether an action aligns with policy, pause and ask for guidance rather than guessing.
### [17:54](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1074s) Establishing the AI Enablement Team Stein Inge Morisbak explains that Tet Digital has formed a dedicated AI enablement team. The primary responsibilities of this team include conducting training, maintaining organizational guidelines, providing hands-on assistance to teams that get stuck, and monitoring for the specific failure modes identified during the pilot phase. Measuring the success of these initiatives remains a complex challenge. While the company has implemented necessary guardrails, Morisbak notes that determining whether productivity is truly increasing—rather than just relying on the subjective feelings of the staff—remains a persistent struggle.
* The goal is to ensure that AI adoption remains a "deliberate, not accidental" process. * The team acts as a central hub for measuring organizational performance across various dimensions.
### [18:57](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1137s) Expanding the Scope: Designers and Product Managers Beyond software developers, the company is now testing AI tools with designers and product managers. This shift highlights a critical tension: these new user groups are often uncomfortable with technical environments, such as the command-line interface or terminal, which they find intimidating. Morisbak argues that this discomfort reinforces the necessity of having technical experts available to act as guardrails. If non-technical groups are to use tools like Claude Code effectively, the company must first ensure they possess a foundational understanding of developer skills.
* "AI doesn't remove the need for technical debt just shows you where the debt is missing," according to Morisbak. * The pilot phase is transitioning from a small test to a company-wide initiative, which requires a focus on sustainable, long-term value rather than abstract, all-encompassing strategy.
### [20:56](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1256s) Scaling from Pilot to Practice To scale successfully, Tet Digital is maintaining a controlled and responsible approach. The AI enablement team remains the bedrock for support, and the company views legal, security, and ethics considerations as absolute foundations. Morisbak emphasizes the importance of community-of-practice groups, suggesting that in this era of rapid change, everyone has essentially become a "newbie." He strongly encourages industry collaboration and sharing learnings between companies and academia to keep pace with the technology.
* "Value isn't created when you buy licenses," Morisbak observes, noting that success is fundamentally about effective change management rather than the tooling itself. * The human element is paramount; the expertise of the people doing the work remains more vital today than it ever has been.
### [22:54](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1374s) Final Takeaways and the "Nerds" In his closing remarks, Morisbak urges the audience to start experimenting with AI, emphasizing that "you can't learn when you're standing on the sidelines." However, he underscores that this must be done with discipline and proper oversight. He reiterates his central thesis with a final, firm plea to the audience: "And remember, for God's sake, keep the nerds." He concludes by clarifying that rather than eliminating the need for experts, AI actually makes their specialized knowledge and technical judgment more important than ever before.
* AI is framed not as a replacement for human skill, but as an amplifier that necessitates even higher levels of expertise to govern and verify the output. * The talk concludes with an invitation for further discussion, as Morisbak stays on to field questions from the conference attendees.
## Notable quotes > [01:17](https://www.youtube.com/watch?v=Fda_-l6HB18&t=77s) The developers, they aren't being negative, they are being responsible, because when AI produces code at enormous speed, deep technical understanding is the only insurance you have against total system collapse. — Stein Inge Morisbak
> [20:54](https://www.youtube.com/watch?v=Fda_-l6HB18&t=1254s) Value isn't created when you buy licenses. — Stein Inge Morisbak
## Mentioned Stein Inge Morisbak, Tet Digital, Claude Code, NDC AI, Ruter, Skyss, Agder Kollektivtrafikk, AtB, Østfold Kollektivtrafikk, DORA, VG, Telenor, Schibsted, DNB, Microsoft
## Video description This talk was recorded at NDC AI in Oslo, Norway. #ndcai #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you: https://ndcconferences.com https://ndc-ai.com/
Subscribe to our YouTube channel and learn every day: / @NDC
Follow our Social Media!
https://www.facebook.com/ndcconferences https://twitter.com/NDC_Conferences https://www.instagram.com/ndc_conferences/
#api #code #ai
Anyone can spin up an app, generate an API, and ship to production — without writing a line of code themselves. Top executives are declaring that technical expertise is becoming optional, that "anyone can be a technologist" without learning to code. Meanwhile, developers are reporting the opposite: FOMO, dread, and the sense that bad teams get worse with AI, not better. Both can't be right. This talk shows a better approach: shift the focus from chasing specific attacks to teaching solid defensive coding principles. We'll build security knowledge directly into the agent — using skills, hooks, and standards — so it looks up the right guidance, plans for it, and reviews its own work. You'll leave knowing how to make your agent produce secure code far more often, by default.
At Tet Digital, we ran a six-week Claude Code pilot across 6 teams and 30 developers, then rolled it out to 180. 90% reported higher productivity. But productivity isn't the whole picture: AI makes mistakes, so team practices for catching and correcting them matter more, not less; there's reduced learning, so skill development needs continued focus; the developer role is shifting toward orchestration and quality control; and like any tool, this one needs maturation, not just access.
In this talk, Stein Inge Morisbak (CTO) shares the concrete findings from the pilot, why Tet chose a deliberate three-step rollout with mandatory training and guardrails instead of an open tap, and why AI is best understood as an amplifier — one that makes deep technical understanding more valuable, not less. When anyone can ship, someone has to know what we're actually shipping.
[Source](https://www.youtube.com/watch?v=Fda_-l6HB18)