---
title: "Talk: Error 103: Secure code | Daniel Christensen"
canonical_url: "https://danielchristensen.no/en/talks/error-103"
last_updated: "2026-09-02T13:55:00.089Z"
locale: en
meta:
  description: "Built for development teams. Drawn from the mistakes I keep seeing in the codebases I pentest, plus lessons from the years I spent developing myself.…"
  "og:description": "Built for development teams. Drawn from the mistakes I keep seeing in the codebases I pentest, plus lessons from the years I spent developing myself. Tailored to your stack and team."
  "og:title": "Error 103: Secure code"
---

Talk + workshop · 45 min

# Error 103: Secure code

Built for development teams. Drawn from the mistakes I keep seeing in the codebases I pentest, plus lessons from the years I spent developing myself. Tailored to your stack and team.

TailoredDev teams45 min

Made for: Development teams · tech leads

[Book this talk →](https://danielchristensen.no/en/contact?talk=error-103) [See all talks](https://danielchristensen.no/en/talks)

02![Browser illustration](https://danielchristensen.no/_nuxt/browser-1.CRodknai.svg)

## About the talk

As a [pentester](https://danielchristensen.no/en/glossary/pentest) I read other people’s code every single week, and the same mistakes show up again and again. Not because developers are lazy, but because security is rarely part of everyday work until something goes wrong. This talk takes the most common vulnerabilities I find in real codebases and shows both how they’re exploited and how they’re avoided.

I have a background as a developer myself, so this is not a finger-wagging talk. It’s a colleague showing you the attacker’s perspective on the code you write.

## What your team takes away

- The most common vulnerabilities I find in pentests, with real (anonymized) examples
- How an attacker thinks when reading your code and your APIs
- Concrete habits and tools that catch the mistakes before they reach production
- What’s actually worth spending time on, and what’s just noise

## How the session is structured

The talk runs about 45 minutes and can be extended with a hands-on workshop where we look at examples in your own stack. The content is tailored in advance: your languages, frameworks and maturity level decide which examples I bring.

## Practical details

Built for development teams, tech leads and architects. Delivered in Norwegian or English, at your office or remote. Tell me what you’re building and I’ll tailor the rest.

Next step

## Sound like a fit?

Send a request with your preferred dates and a few words about the audience, and you'll get a concrete quote the same day.

[Book this talk →](https://danielchristensen.no/en/contact?talk=error-103)

## More talks

[01**Security in the workplace**Talk · 40 min + Q&A→](https://danielchristensen.no/en/talks/sikkerhet-arbeid) [03**The road to your dream job**Talk · 45 min · interactive→](https://danielchristensen.no/en/talks/drommejobben) [04**Hacker becomes bank manager (by accident), and anti-scam tricks**Signature talk→](https://danielchristensen.no/en/talks/banksjef)