Snowflake Environments
Each environment is hand-configured and unique. Nobody knows exactly what is running where. Configuration drift is constant.
9 minute read
Tag: Environment-Consistency
No Infrastructure as Code
Servers are provisioned manually through UIs, making environment creation slow, error-prone, and unrepeatable.
8 minute read
Configuration Embedded in Artifacts
Connection strings, API URLs, and feature flags are baked into the build, requiring a rebuild per environment and meaning the tested artifact is never what gets deployed.
8 minute read
No Environment Parity
Dev, staging, and production are configured differently, making “passed in staging” provide little confidence about production behavior.
8 minute read
Shared Test Environments
Multiple teams share a single staging environment, creating contention, broken shared state, and unpredictable test results.
10 minute read
Hard-Coded Environment Assumptions
Code that behaves differently based on environment name (if env == ‘production’) is scattered throughout the codebase.
10 minute read
The Build Runs Again for Every Environment
Build outputs are discarded and rebuilt for each environment. Production is not running the artifact that was tested.
3 minute read
Database Migrations Block or Break Deployments
Schema changes require downtime, lock tables, or leave the database in an unknown state when they fail mid-run.
4 minute read
Tests Pass in One Environment but Fail in Another
Tests pass locally but fail in CI, or pass in CI but fail in staging. Environment differences cause unpredictable failures.
3 minute read
Getting a Test Environment Requires Filing a Ticket
Test environments are a scarce, contended resource. Provisioning takes days and requires another team’s involvement.
3 minute read
Setting Up a Development Environment Takes Days
New team members are unproductive for their first week. The setup guide is 50 steps long and always out of date.
3 minute read
Test Environments Take Too Long to Reset Between Runs
The team cannot run the full regression suite on every change because resetting the test environment and database takes too long.
5 minute read
Staging Passes but Production Fails
Deployments pass every pre-production check but break when they reach production.
3 minute read
Deploying Stateful Services Causes Outages
Services holding in-memory state drop connections, lose sessions, or cause cache invalidation spikes on every redeployment.
3 minute read
Tests Interfere with Each Other Through Shared Data
Tests share mutable state in a common database. Results vary by run order, making failures unreliable signals of real bugs.
4 minute read
Tests Randomly Pass or Fail
The pipeline fails, the developer reruns it without changing anything, and it passes.
3 minute read
It Works on My Machine
Code that works in one developer’s environment fails in another, in CI, or in production. Environment differences make results unreproducible.
3 minute read