Why DevOps for Data?
A hand-edited production view, no history, no rollback. The story of why data teams need GitOps — and how Git, dbt, and Snowflake fit together.
Read →~/thepolygloter
Learnings from a developer who won't pick just one stack.
Languages, infrastructure, and the craft of shipping software. Written by someone who loves to try, experiment, fail, and fix — then write down what the failing taught.
Browse all blogsLatest
Other recent blogs
Environment Setup: dbt + Snowflake Basics
Elin gets her first dbt model running against Snowflake — warehouses, profiles, and the edit-run loop, deliberately without Git yet.
Read →Version Control: Monorepo & CODEOWNERS
Elin puts the dbt project under version control: branching, pull requests, monorepo vs. many repos, and CODEOWNERS for approvals.
Read →Automating with CI: GitHub Actions for dbt
A screenshot of passing tests isn't CI. Elin wires up GitHub Actions to run dbt build on every pull request, so a broken model can never merge silently.
Read →Full GitOps Flow: Deploy, Promote, Rollback
Three months on, Elin faces Johan's Monday-morning problem — and the loop closes: automated deploys, dev-to-prod promotion, and real rollback.
Read →Two Robberies, One Warning
A 2024 deepfake heist and a 2026 AI-aided ransom, two years apart, expose the same root cause — and the boring fixes that would have stopped both.
Read →Welcome to The Polygloter
A new beginning: why I'm starting this blog to share the knowledge and hard-won lessons from a career spent building software.
Read →Monday Morning Musing: Burnout
On developer burnout — spotting the physical, emotional, behavioural, and productivity signs, and preventing it as an individual, team lead, and organization.
Read →