--- title: Why "It Worked on My Machine" Still Happens in 2026 description: Environment drift — differences in runtime versions, dependencies, configuration, and OS between developer machines and production — remains a leading cause of... canonical: https://daily.dev/posts/why-it-worked-on-my-machine-still-happens-in-2026-wu83ivzac twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why "It Worked on My Machine" Still Happens in 2026 | daily.dev og:description: Environment drift — differences in runtime versions, dependencies, configuration, and OS between developer machines and production — remains a leading cause of... og:url: https://daily.dev/posts/why-it-worked-on-my-machine-still-happens-in-2026-wu83ivzac og:image: https://api.daily.dev/og/posts/wu83iVZac.png og:image:alt: Why "It Worked on My Machine" Still Happens in 2026 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why "It Worked on My Machine" Still Happens in 2026 **[freeCodeCamp](https://daily.dev/sources/freecodecamp)** · 14 min read · 49 upvotes · 2 comments ## Summary Environment drift — differences in runtime versions, dependencies, configuration, and OS between developer machines and production — remains a leading cause of engineering waste in 2026. The post explains why local test success doesn't guarantee production stability, how configuration mismatches cause more incidents than code bugs, and estimates that environment management consumes 15–25% of engineering capacity. It argues the root issue is an ownership problem, not a tooling one, and walks through how Platform as a Service (PaaS) tools like Render or Railway solve it by providing a single declarative application definition that runs identically across dev, staging, and production environments, including preview environments per pull request. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does 'it works on my machine' still happen even with containers and CI/CD in place? It happens because production depends on far more than source code: operating system, runtime versions, environment variables, databases, networking rules, file permissions, installed libraries, and CPU architecture all differ between machines. A typical Node.js app has 500-1,500 packages in its dependency tree, and even with lock files, runtime versions, system libraries, and base OS images in containers still drift across patch cycles. _Teams debugging environment drift can find practical PaaS setup guidance on daily.dev._ ### What does a basic setup for deploying an app to a Platform-as-a-Service look like? It involves five steps: connect a Git repository so the platform deploys on push, define the application once in a declarative file (runtime, build command, start command, services), set environment variables in the platform rather than in .env files, attach managed databases and caches, and use per-pull-request preview environments built from the same definition as production. A typical web service can go from repo to deployed app with a managed database in an afternoon. _Engineers weighing paas adoption can track setup patterns and comparisons on daily.dev._ ### How much engineering time do companies lose managing their own deployment infrastructure and environments? Estimates from engineering productivity research suggest infrastructure and environment-related tasks consume between 15-25% of total engineering capacity at companies that own their own deployment infrastructure. For a ten-engineer team, that equates to roughly two to three people running full time without producing customer-facing output. _Teams deciding whether to keep owning infrastructure can weigh this tradeoff via daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@shahbaz7** · 6 upvotes > I sent that line to a client yesterday, adding that I couldn't replicate the bug on my system using at least 5 browsers. **@jenueldev** · 3 upvotes > The ownership framing is stronger than treating this as another containerization problem: a declarative spec only helps if one team owns keeping runtime, config, and dependency policy aligned. Preview environments close much of the gap, but production-only state—data volume, traffic shape, external integrations—still needs contract tests and observability, or “same definition” can create false confidence. ## Similar posts on daily.dev - [Why Standardized Developer Environments Still Break DevOps Workflows](https://daily.dev/posts/why-standardized-developer-environments-still-break-devops-workflows-150xfnuxj) · DevOps.com · 10 upvotes · 1 comments - [Why Test Environments Fail—and What Top Teams Do to Avoid the Chaos](https://daily.dev/posts/why-test-environments-fail-and-what-top-teams-do-to-avoid-the-chaos-pgwp8qj0d) · SD Times · 1 upvotes · 0 comments - [Why Your “Simple Deploy” Turned Into a Week of Infrastructure Work](https://daily.dev/posts/why-your-simple-deploy-turned-into-a-week-of-infrastructure-work-zjw80nfm2) · freeCodeCamp · 5 upvotes · 0 comments - [Staging Environments Are a Deployment Problem, Not an Infrastructure Problem](https://daily.dev/posts/staging-environments-are-a-deployment-problem-not-an-infrastructure-problem-9pzhrxx0g) · CodeCraft Diary · 4 upvotes · 0 comments - [Working software runs locally](https://daily.dev/posts/working-software-runs-locally-acfymodik) · Lobsters · 0 upvotes · 0 comments --- Tags: [#devops](https://daily.dev/tags/devops), [#cicd](https://daily.dev/tags/cicd), [#docker](https://daily.dev/tags/docker) [View this post on daily.dev](https://daily.dev/posts/why-it-worked-on-my-machine-still-happens-in-2026-wu83ivzac) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Why \"It Worked on My Machine\" Still Happens in 2026","url":"https://daily.dev/posts/why-it-worked-on-my-machine-still-happens-in-2026-wu83ivzac","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-it-worked-on-my-machine-still-happens-in-2026-wu83ivzac"},"datePublished":"2026-07-15T21:45:37.132Z","dateModified":"2026-09-14T08:40:33.555Z","description":"Environment drift — differences in runtime versions, dependencies, configuration, and OS between developer machines and production — remains a leading cause of...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ec8b7909810c88e8846d86cd44a4c62a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ec8b7909810c88e8846d86cd44a4c62a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"freeCodeCamp","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"freeCodeCamp","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1628412854/logos/freecodecamp","url":"https://daily.dev/sources/freecodecamp"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/why-it-worked-on-my-machine-still-happens-in-2026-wu83ivzac","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":49},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"devops,cicd,docker","timeRequired":"PT14M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"freeCodeCamp","item":"https://daily.dev/sources/freecodecamp"},{"@type":"ListItem","position":3,"name":"Why \"It Worked on My Machine\" Still Happens in 2026"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/why-it-worked-on-my-machine-still-happens-in-2026-wu83ivzac","comment":[{"@type":"Comment","text":"I sent that line to a client yesterday, adding that I couldn’t replicate the bug on my system using at least 5 browsers.","datePublished":"2026-07-16T16:29:31.059Z","url":"https://daily.dev/posts/wu83iVZac#c-w6n4tV3CN","author":{"@type":"Person","name":"Shahbaz Ahmad Siddiqui","url":"https://daily.dev/shahbaz7","image":"https://media.daily.dev/image/upload/s--0wN8WvVK--/f_auto/v1722097587/avatars/avatar_g2gB9vXOh9MXsB10ydU35"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6}},{"@type":"Comment","text":"The ownership framing is stronger than treating this as another containerization problem: a declarative spec only helps if one team owns keeping runtime, config, and dependency policy aligned. Preview environments close much of the gap, but production-only state—data volume, traffic shape, external integrations—still needs contract tests and observability, or “same definition” can create false confidence.","datePublished":"2026-07-17T02:05:25.216Z","url":"https://daily.dev/posts/wu83iVZac#c-Fy74aeSET","author":{"@type":"Person","name":"Jenuel Oras Ganawed","url":"https://daily.dev/jenueldev","image":"https://media.daily.dev/image/upload/s--BadmiNyj--/f_auto/v1787625077/avatars/avatar_JJtZr4Sjm?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/why-it-worked-on-my-machine-still-happens-in-2026-wu83ivzac#faq","mainEntity":[{"@type":"Question","name":"Why does 'it works on my machine' still happen even with containers and CI/CD in place?","acceptedAnswer":{"@type":"Answer","text":"It happens because production depends on far more than source code: operating system, runtime versions, environment variables, databases, networking rules, file permissions, installed libraries, and CPU architecture all differ between machines. A typical Node.js app has 500-1,500 packages in its dependency tree, and even with lock files, runtime versions, system libraries, and base OS images in containers still drift across patch cycles. Teams debugging environment drift can find practical PaaS setup guidance on daily.dev."}},{"@type":"Question","name":"What does a basic setup for deploying an app to a Platform-as-a-Service look like?","acceptedAnswer":{"@type":"Answer","text":"It involves five steps: connect a Git repository so the platform deploys on push, define the application once in a declarative file (runtime, build command, start command, services), set environment variables in the platform rather than in .env files, attach managed databases and caches, and use per-pull-request preview environments built from the same definition as production. A typical web service can go from repo to deployed app with a managed database in an afternoon. Engineers weighing paas adoption can track setup patterns and comparisons on daily.dev."}},{"@type":"Question","name":"How much engineering time do companies lose managing their own deployment infrastructure and environments?","acceptedAnswer":{"@type":"Answer","text":"Estimates from engineering productivity research suggest infrastructure and environment-related tasks consume between 15-25% of total engineering capacity at companies that own their own deployment infrastructure. For a ten-engineer team, that equates to roughly two to three people running full time without producing customer-facing output. Teams deciding whether to keep owning infrastructure can weigh this tradeoff via daily.dev."}}]} ```