--- title: The Gospel According to Graybeard | daily.dev description: A critique of the tech industry's obsession with speed as a moral virtue rather than a practical tool. The author argues that most 'speed' is actually... canonical: https://daily.dev/posts/the-gospel-according-to-graybeard-nazmdjupa twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The Gospel According to Graybeard | daily.dev og:description: A critique of the tech industry's obsession with speed as a moral virtue rather than a practical tool. The author argues that most 'speed' is actually... og:url: https://daily.dev/posts/the-gospel-according-to-graybeard-nazmdjupa og:image: https://api.daily.dev/og/posts/NazMDJUpa.png og:image:alt: The Gospel According to Graybeard 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. # The Gospel According to Graybeard **[Hacker News](https://daily.dev/sources/hn)** · 6 min read · 6 upvotes · 1 comments ## Summary A critique of the tech industry's obsession with speed as a moral virtue rather than a practical tool. The author argues that most 'speed' is actually impatience disguised as urgency — vague requirements, half-made decisions, and skipped thinking that accumulates into broken systems, burned-out teams, and technical debt. Real speed, the author contends, comes only after understanding the work clearly. The piece distinguishes between urgency (appropriate when time genuinely matters) and haste (seeking emotional relief from action without clarity), and argues that slowing down to understand before deciding is what actually enables sustainable, fast execution. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community take How the wider developer community reacted, aggregated from 1 discussion and 106 comments across hackernews (as of 2026-07-31). **TL;DR:** The community broadly agrees that the 'cult of speed' in tech workplaces is real and harmful, with many sharing personal anecdotes validating the article's thesis; however, a significant minority pushes back noting that speed and urgency do have genuine value, and the debate over first-mover advantage spawns its own lively sub-thread. **Sentiment:** 35% positive · 45% mixed · 20% skeptical **The case for** - 'Slow is smooth and smooth is fast' — commenters with military and racing backgrounds affirm that deliberate, controlled execution consistently outperforms panicked rushing. - Several experienced engineers note that taking time to understand a problem before acting almost always results in faster overall resolution and smaller blast radius during incidents. - The article's framing resonates with ICs who feel pressured by management to perform urgency rather than deliver quality. - Commenters observe that the 'cult of speed' is often driven by VC time horizons rather than genuine product or customer needs. **The pushback** - Some commenters argue speed genuinely matters — YouTube, Uber, and Airbnb are cited as companies with real first-mover or fast-mover advantages. - One commenter points out the article never mentions 'deadlines,' which are a concrete, unavoidable driver of speed pressure in most workplaces. - Excessive planning without action is also a failure mode; one commenter notes they were usually wrong when they thought constraints were fully understood. - The religion-of-speed critique is seen as potentially one-sided: being slow can mean stagnation and ceding market share in competitive software markets. **By community** - hackernews (mixed): Commenters largely sympathize with the anti-speed-worship thesis but actively debate its limits, with notable pushback on first-mover advantage claims and the omission of deadlines from the discussion. **Hottest debate:** Whether first-mover advantage is real or illusory, with examples like Google, YouTube, and Uber pulled in opposite directions by different commenters. **Open questions** - How should individual contributors practically resist speed pressure from above without being labeled slow or ineffective? - The article never addresses deadlines — how does the 'make sense before moving' philosophy apply when hard external deadlines exist? - Is there a reliable way to distinguish genuine urgency from performative urgency in the moment? **Highlights** > Use to work with a pretty jaded Army Colonel. He'd often say: "even periodic motion looks like progress on short enough time scales." And also, "Slow is smooth and smooth is fast." > — [eluusive on hackernews · 2 comments](https://news.ycombinator.com/item?id=49118764) > The religion of speed is the religion of VC investment backing, because VCs have set time horizons for delivering returns to their own investors. You can only get their interest if you can make them believe you can deliver 10x growth on their schedule. Committing to that schedule — and really believing in that commitment — is what turns someone into the sort of person who sets arbitrary project timelines that disregard technical practicality, and then kills projects when they fail per those arbitrary timelines. > — [derefr on hackernews · 4 comments](https://news.ycombinator.com/item?id=49119367) > Felt this in my bones. It’s painful how accurately this describes my current work situation. The pressure comes from the top - leaders that have no idea what they want but they want _something_ to happen NOW. This has only gotten worse with the recent AI thoughtleadering because now the expectation has been seeded that every random brainwave should take at most one hour to implement (given enough tokens). What can an IC do in an environment like this? If you slow down and attempt to find any clarity, you’re labeled as slow and ineffective. If you cave to the pressure and start slinging slop with the rest of them, you’re just perpetuating the spiral. Genuinely asking - how do others thread this needle? > — [thearrow on hackernews · 2 comments](https://news.ycombinator.com/item?id=49118632) > Impossible to disagree with the author, and yet something seems missing in the discussion... Let me check: Ctrl-F, 'deadline' 0 result. Oh, yeah, that's what missing from the discussion. And without any trolling, I'm curious about what the author would have to say about this matter. Not all "need for speed" comes from a vacuum. Is it always legit ? Should we push back ? Sure. Do we always meaningfully, practically, realistically have a choice anyway ? > — [phtrivier on hackernews](https://news.ycombinator.com/item?id=49121425) > "The better work is usually calmer than people expect. It still moves[...] It does not worship motion for its own sake." There's two architects, Reiser and Umemoto who wrote a book called The Atlas of Novel Tectonics about maybe 20 years ago and a sentence that always stuck with me was "in a moving world the nomad is the one standing still". The whole cult of speed irony, like digital nomads who only ever seem to camp out in Starbucks, is that they're the most homogenous, like-minded, incapable of independent thought people you will ever meet. They'll tell you they've done 50 things and stayed in 50 countries and somehow seem less travelled than someone who just stood still. Same with the whole productivity software velocity, ship this or that crowd. They always have 20 projects but seemingly never actually do anything, or do the same thing everyone else does. > — [Barrin92 on hackernews](https://news.ycombinator.com/item?id=49119484) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=49117284) · 80 points · 106 comments ## Similar posts on daily.dev - [The Urgency Trap: How “Agile” Became an Excuse to Skip Thinking](https://daily.dev/posts/the-urgency-trap-how-agile-became-an-excuse-to-skip-thinking-cpnjdstqs) · Medium · 0 upvotes · 0 comments - [Some Things Just Take Time](https://daily.dev/posts/some-things-just-take-time-qcqpkxnrs) · Armin Ronacher · 0 upvotes · 0 comments - [What's the facts, Charity? How do I get my leaders to stop running teams Into the ground?](https://daily.dev/posts/what-s-the-facts-charity-how-do-i-get-my-leaders-to-stop-running-teams-into-the-ground--m2ed4wi1e) · Stack Overflow Blog · 2 upvotes · 0 comments --- Tags: [#leadership](https://daily.dev/tags/leadership), [#company-culture](https://daily.dev/tags/company-culture), [#technical-debt](https://daily.dev/tags/technical-debt) [View this post on daily.dev](https://daily.dev/posts/the-gospel-according-to-graybeard-nazmdjupa) ```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":"The Gospel According to Graybeard","url":"https://daily.dev/posts/the-gospel-according-to-graybeard-nazmdjupa","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-gospel-according-to-graybeard-nazmdjupa"},"datePublished":"2026-07-31T04:01:33.126Z","dateModified":"2026-07-31T10:49:59.769Z","description":"A critique of the tech industry's obsession with speed as a moral virtue rather than a practical tool. The author argues that most 'speed' is actually...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/00ce9149ef9633dd81ba1ba31285d41d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/00ce9149ef9633dd81ba1ba31285d41d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","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":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/the-gospel-according-to-graybeard-nazmdjupa","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"leadership,company-culture,technical-debt","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"The Gospel According to Graybeard"}]} ```