Seeking: full-time senior backend / platform role, ideally in sustainability, energy, science, developer infrastructure or AI platforms.
I modernize platforms around what already works instead of rewriting them, until operations are boring, developers are productive, and users get what they've been waiting for. Most recently a biodiversity research platform at Helmholtz (UFZ):
- Developers: consolidated the apps and their git-subtree'd shared packages into one monorepo, built CI/CD from scratch, automated releases and hotfixes, made backend tests 6-10x faster
- Operations: Helm and ArgoCD across dev, stage and prod; logs used to hide inside pods, now it's OpenTelemetry/SigNoz with alerts as code
- Users: shipped a legacy data import that had been overdue for two years (1.94M volunteer field observations back to 1991), and brought a plant-traits database back online after years offline, rebuilt from the bytecode of its old Java app and verified record by record
Before that: Head of Backend at a location-based sustainability startup, led 7 engineers. Instead of rewriting the old-school Python API I inherited, I wrapped it in a TypeScript GraphQL layer that all native and web clients use, and took the platform to AWS/EKS. Long before: built, ran and sold metareddit, a Reddit analytics site whose crawlers ran almost without interruption for five years.
I work agent-first (Claude Code, Codex, my own agent memory system) and verify everything against reality. Python since 2009, TypeScript since 2016. Fluent in German and English.
When the five cubes a bit down on the page spin diagonally, my whole browser window including address bar and tab bar starts glitching. Chrome on macOS.
Full-stack engineer turned engineering leader, 13+ years building and scaling web platforms. Most recently modernized a biodiversity monitoring platform at Helmholtz (UFZ) — consolidated scattered repos into a monorepo, built the entire CI/CD pipeline, designed Helm umbrella charts, and deployed observability from zero. Before that, led backend and frontend teams (7 engineers) at a location-based mobile startup — designed the GraphQL architecture from scratch, single-handedly executed the AWS EKS migration, and built the push notification system. Equally comfortable writing resolvers and writing Helm charts. TypeScript and Kubernetes are home turf. Fluent in German and English.
Good to see Sarah mentioned here, it's the same for me. Her music is the one constantly good thing that I'm always looking forward to in the last year, highly recommended.
The metareddit monitor doesn't search through an index. It's a crawler that constantly fetches all new comments and submissions and looks for the (several thousand) keywords in each of them.
If that is the only problem, flipping one bit in every response seems like a really simple solution. Why hasn't Cloudfront fixed it yet, do they know about this?
Yes they know about it. Below is the response from Amazon. The logic they employ is that since it is broken in an old version of Squid, it is fine for it to be broken on Cloudfront.
While we are aware of the issue with range request HTTP/1.0 206 responses and Chrome, we cannot provide an ETA for a fix. Since this issue is specific to range requests, an immediate workaround is to disable range requests on your origin server if this is possible for your use case.
It is also worth mentioning that multiple web proxy and cache application vendors have using HTTP/1.0 as a de facto standard for many years, so you will probably sporadically get similar reports from your end users using Chrome, but not other browsers such as Firefox or Safari. For example, here is a discussion between a Chrome developer on the mailing list for the popular Squid web cache about a similar report:
http://www.squid-cache.org/mail-archive/squid-dev/201204/011...
I am not saying that always returning HTTP/1.0 will stick around forever, but it is fairly common in real world situations today.
Remote: Yes (preferred)
Willing to relocate: Yes
Technologies: Python, TypeScript, Node.js, NestJS, React, Next.js, GraphQL, PostgreSQL/PostGIS, Kubernetes, Helm, ArgoCD, Docker, Terraform, AWS (EKS, S3), GitLab CI, OpenTelemetry, SigNoz, Datadog, Claude Code, Codex, MCP
Résumé/CV: https://misera.org/cv
Email: thomas[@]misera.org
Seeking: full-time senior backend / platform role, ideally in sustainability, energy, science, developer infrastructure or AI platforms.
I modernize platforms around what already works instead of rewriting them, until operations are boring, developers are productive, and users get what they've been waiting for. Most recently a biodiversity research platform at Helmholtz (UFZ):
- Developers: consolidated the apps and their git-subtree'd shared packages into one monorepo, built CI/CD from scratch, automated releases and hotfixes, made backend tests 6-10x faster
- Operations: Helm and ArgoCD across dev, stage and prod; logs used to hide inside pods, now it's OpenTelemetry/SigNoz with alerts as code
- Users: shipped a legacy data import that had been overdue for two years (1.94M volunteer field observations back to 1991), and brought a plant-traits database back online after years offline, rebuilt from the bytecode of its old Java app and verified record by record
Before that: Head of Backend at a location-based sustainability startup, led 7 engineers. Instead of rewriting the old-school Python API I inherited, I wrapped it in a TypeScript GraphQL layer that all native and web clients use, and took the platform to AWS/EKS. Long before: built, ran and sold metareddit, a Reddit analytics site whose crawlers ran almost without interruption for five years.
I work agent-first (Claude Code, Codex, my own agent memory system) and verify everything against reality. Python since 2009, TypeScript since 2016. Fluent in German and English.