Kasper Grøntved

Lectures & talks

Knowledge dissemination

Explaining the work — internally, at conferences, and to anyone who inherits a system I built. Each deck below is a single HTML file that runs in your browser, so every slide has its own URL and nothing depends on a hosting service that might not be here in five years.

Featured

★ Featured

ML and Data at Colourbox

Why content understanding is the only answer to DAM cold start, what EU sovereignty actually commits you to architecturally, how dense embeddings and patch-level late interaction divide the work between a stock library and a DAM system — then the multimodal field case, the production objections, and why a benchmark score is not a customer finding their asset.

53 slidesSearch Self-hosted inferenceDraft
Explore the deck →

Archive

How these work

The engine is about 200 lines of vanilla JavaScript in /deck/deck.js — no framework, no build step. Slides live on a fixed 1920×1080 canvas that gets scaled to whatever window you open it in, so a deck looks identical on a laptop, a projector, and a phone.

While presenting

  • → / space / PageDown next slide, ← / PageUp back
  • o contents drawer · n speaker notes · r sources for the current slide · f fullscreen
  • t light/dark · p print to PDF, one slide per page

Slides carry their own citations: press r and the drawer lists the papers, code and lectures behind whatever is on screen, with a count badge in the corner so you can see at a glance whether a claim is sourced.

Swipe works on touch. The URL tracks the slide number, so /knowledge/<name>/#7 opens directly on slide 7 — useful when someone asks you to send "that one chart".

Borrow it if you like: copy /deck/ and /knowledge/_template/ from the repo.