Software engineer · Berlin

Isaac Bigsby Trogdon

I build and look after large Drupal and PHP platforms. For the past few years I’ve been bringing LLMs, retrieval and vector search into them, as features that have to keep working long after launch day, not as demos.

15+ yearsLOOM GmbH, since 2018English · German

Portrait of Isaac Bigsby Trogdon

About

I started on the other side of the CMS. Before I wrote code for a living I spent four years at artnet as a digital producer and photo editor, working inside editorial workflows and content management every day. Before that I studied Cultural Studies and German at UNC Chapel Hill.

In 2012 I moved to the building side as a junior Drupal developer, and I’ve been building Drupal platforms ever since, most of that time at LOOM in Berlin. Since 2022 my work there has been mostly AI: assistants, semantic search and content automation that live inside client platforms and get maintained like everything else.

Work

An AI assistant, in Drupal and Python

A production AI assistant that runs across several LOOM client projects. I built both halves: the Drupal side (module architecture, admin configuration, the assistant interface, content integration) and a companion Python service that does the LLM orchestration.

  • It started on Flask and the OpenAI API. I later moved it to LangChain so it isn’t tied to one model provider.
  • Retrieval runs on Qdrant, behind a REST contract I designed between the Python service and Drupal.
  • The work didn’t end at launch: production debugging, retrieval tuning and ongoing maintenance are part of it.

Semantic search that holds up in production

Semantic search backed by vector databases, taken from working to reliable. That meant choosing embeddings, deciding how to index, and working on retrieval quality end to end, and extending existing AI features until they met real reliability and performance requirements.

The hardest bugs were results that looked plausible and were wrong. That’s the failure mode that makes RAG systems hard to ship, and finding and fixing it was part of the job.

How I work with AI tools

Claude Code is my main development environment, for exploring architecture, implementing, refactoring, debugging, testing and research. Before that I used GitHub Copilot and ChatGPT heavily across VS Code, PhpStorm and the terminal. The point is working well with the tool so the code gets better, not handing the code over to it.

Open source

Path

  1. 2018–now
    LOOM GmbH, Senior Full-Stack Developer

    Enterprise platforms end to end, from architecture to long-term maintenance. AI-focused since 2022.

  2. 2016–2017
    Michely Web Engineering, Web Developer

    Drupal 7 and 8 applications for clients in pharmaceuticals, fashion and specialized web industries.

  3. 2014–2015
    Proventjobsfor.me AG, Web Developer

    Backend of a Drupal 8 recruitment platform: workflows, user management, business logic.

  4. 2012–2014
    Clubspo11.de AG, Junior Web Developer

    Front and back end of a Drupal-based sports marketing platform.

  5. 2007–2011
    artnet AG, Digital Producer / Photo Editor

    Digital publishing, editorial workflows and web project coordination.

  6. 1997–2002
    UNC Chapel Hill, B.A. with Honors

    Cultural Studies and German Studies.

Toolbox

Backend
PHP, Drupal 7–12, Symfony, Flask, REST APIs, webhooks, system integrations
AI / LLM
OpenAI API, LangChain, RAG, embeddings, vector databases, prompt engineering
Frontend
React, TypeScript, Gatsby
Data
MySQL, PostgreSQL, Qdrant, Milvus
Infra
Docker, Linux, Nginx, Git

Contact

mr@dyss.net

Outside of software I make music as Dyssembler.