--- title: Why “Clean Code” is Killing Your Velocity | daily.dev description: Argues that common clean-code practices like wrapping every dependency in interfaces, repositories, and extra layers often add no real value and just slow... canonical: https://daily.dev/posts/why-clean-code-is-killing-your-velocity-5oncq2nqu twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why “Clean Code” is Killing Your Velocity | daily.dev og:description: Argues that common clean-code practices like wrapping every dependency in interfaces, repositories, and extra layers often add no real value and just slow... og:url: https://daily.dev/posts/why-clean-code-is-killing-your-velocity-5oncq2nqu og:image: https://api.daily.dev/og/posts/5oncq2Nqu.png og:image:alt: Why “Clean Code” is Killing Your Velocity 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 “Clean Code” is Killing Your Velocity **[CodeOpinion](https://daily.dev/sources/codeopinion)** · [@codeopinion](https://daily.dev/codeopinion) · 8 min read · 0 upvotes · 0 comments ## Summary Argues that common clean-code practices like wrapping every dependency in interfaces, repositories, and extra layers often add no real value and just slow teams down. Using a Stripe payment example and an order-fulfillment example, the piece shows how a single-use interface or repository/mapper/domain-model chain can be replaced with direct, simple code. The real goal of architecture patterns like Clean, Onion, Hexagonal, or Ports and Adapters is managing coupling and controlling blast radius, not abstraction for its own sake. Vertical slices are offered as a way to let different parts of a system have different levels of structure based on actual complexity, rather than applying the same layered template everywhere. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Do I need to create an interface for a third-party dependency like Stripe if there's only one implementation and one usage? No, a single-use interface with only one implementation typically adds no real value and is often just liability rather than architecture. If there's genuinely only one implementation and one usage, the command handler itself already acts as the seam, so you can call the Stripe SDK directly there and change it in that one place if needed later. _When deciding how much abstraction a dependency really needs, developers compare approaches and trade-offs on daily.dev._ ### When does adding an interface or abstraction layer actually make sense in software architecture? An abstraction is worth adding when you have uncontrolled coupling, such as hundreds or thousands of usages of something, not when there's a single implementation and a single usage. The underlying goal of patterns like Clean Architecture, Hexagonal, or Ports and Adapters is managing coupling and controlling blast radius, not abstraction as a default rule. _Developers weighing when abstraction pays off can track architecture discussions like this on daily.dev._ ## Similar posts on daily.dev - [Clean Architecture Explained: Building Software That Stands the Test of Time](https://daily.dev/posts/clean-architecture-explained-building-software-that-stands-the-test-of-time-acdblphuf) · Medium · 1 upvotes · 0 comments - [Why Your Software Sucks: Inheritance](https://daily.dev/posts/why-your-software-sucks-inheritance-pnnmgu4k8) · Aaronontheweb · 28 upvotes · 3 comments - [You're Not Building Netflix: Stop Coding Like You Are](https://daily.dev/posts/you-re-not-building-netflix-stop-coding-like-you-are-fvaumfnpy) · DEV · 673 upvotes · 55 comments - [Velocity: Why the Best Software Architects Move the Slowest](https://daily.dev/posts/velocity-why-the-best-software-architects-move-the-slowest-gi13ouii7) · Atomic Spin · 69 upvotes · 10 comments --- Tags: [#architecture](https://daily.dev/tags/architecture), [#design-patterns](https://daily.dev/tags/design-patterns) [View this post on daily.dev](https://daily.dev/posts/why-clean-code-is-killing-your-velocity-5oncq2nqu) ```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 “Clean Code” is Killing Your Velocity","url":"https://daily.dev/posts/why-clean-code-is-killing-your-velocity-5oncq2nqu","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-clean-code-is-killing-your-velocity-5oncq2nqu"},"datePublished":"2026-10-04T13:07:21.693Z","dateModified":"2026-10-05T10:00:18.696Z","description":"Argues that common clean-code practices like wrapping every dependency in interfaces, repositories, and extra layers often add no real value and just slow...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c74f4482515b2633d3b461c5274e8d91?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c74f4482515b2633d3b461c5274e8d91?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"CodeOpinion","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":"Person","name":"Derek Comartin","url":"https://daily.dev/codeopinion","image":"https://lh3.googleusercontent.com/a-/AOh14GgoQapb7NmLN1TZ6L-UCxkRpDZ4H7LKwud1DUZCTSI=s100","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":940}},"commentCount":0,"discussionUrl":"https://daily.dev/posts/why-clean-code-is-killing-your-velocity-5oncq2nqu","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,design-patterns","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"CodeOpinion","item":"https://daily.dev/sources/codeopinion"},{"@type":"ListItem","position":3,"name":"Why “Clean Code” is Killing Your Velocity"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/why-clean-code-is-killing-your-velocity-5oncq2nqu#faq","mainEntity":[{"@type":"Question","name":"Do I need to create an interface for a third-party dependency like Stripe if there's only one implementation and one usage?","acceptedAnswer":{"@type":"Answer","text":"No, a single-use interface with only one implementation typically adds no real value and is often just liability rather than architecture. If there's genuinely only one implementation and one usage, the command handler itself already acts as the seam, so you can call the Stripe SDK directly there and change it in that one place if needed later. When deciding how much abstraction a dependency really needs, developers compare approaches and trade-offs on daily.dev."}},{"@type":"Question","name":"When does adding an interface or abstraction layer actually make sense in software architecture?","acceptedAnswer":{"@type":"Answer","text":"An abstraction is worth adding when you have uncontrolled coupling, such as hundreds or thousands of usages of something, not when there's a single implementation and a single usage. The underlying goal of patterns like Clean Architecture, Hexagonal, or Ports and Adapters is managing coupling and controlling blast radius, not abstraction as a default rule. Developers weighing when abstraction pays off can track architecture discussions like this on daily.dev."}}]} ```