<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/going-fast-vs-slow-in-coding-gdcycdwaa" -->

---
title: Going Fast VS. Slow in Coding | daily.dev
description: A developer reflects on the trade-offs between moving fast and slow when coding with AI assistance. Going too fast risks producing broken or low-quality code...
canonical: https://daily.dev/posts/going-fast-vs-slow-in-coding-gdcycdwaa
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Going Fast VS. Slow in Coding | daily.dev
og:description: A developer reflects on the trade-offs between moving fast and slow when coding with AI assistance. Going too fast risks producing broken or low-quality code...
og:url: https://daily.dev/posts/going-fast-vs-slow-in-coding-gdcycdwaa
og:image: https://api.daily.dev/og/posts/GdcycdWAA.png
og:image:alt: Going Fast VS. Slow in Coding
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.

# Going Fast VS. Slow in Coding

**[NeetCode](https://daily.dev/sources/neetcode)** · 1 min read · 1 upvotes · 0 comments

## Summary

A developer reflects on the trade-offs between moving fast and slow when coding with AI assistance. Going too fast risks producing broken or low-quality code ('slop'), while going too slow means nothing ships. The author argues a happy medium is always necessary, noting that even with AI tools, they still rely on smaller-scoped tasks with faster models rather than fully delegating to AI systems. The ideal of AI autonomously filling in all the blanks isn't quite here yet.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.youtube.com/watch?v=X6fDJktYWg4>

## Similar posts on daily.dev

- [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
- [The Trap of Doing It Myself](https://daily.dev/posts/the-trap-of-doing-it-myself-uwcmxskdb) · Medium · 4 upvotes · 0 comments

---

Tags: [#productivity](https://daily.dev/tags/productivity), [#ai-coding](https://daily.dev/tags/ai-coding), [#vibe-coding](https://daily.dev/tags/vibe-coding)

[View this post on daily.dev](https://daily.dev/posts/going-fast-vs-slow-in-coding-gdcycdwaa)

```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":"Going Fast VS. Slow in Coding","url":"https://daily.dev/posts/going-fast-vs-slow-in-coding-gdcycdwaa","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/going-fast-vs-slow-in-coding-gdcycdwaa"},"datePublished":"2026-07-20T14:37:54.591Z","dateModified":"2026-09-14T08:16:45.840Z","description":"A developer reflects on the trade-offs between moving fast and slow when coding with AI assistance. Going too fast risks producing broken or low-quality code...","image":"https://i.ytimg.com/vi/X6fDJktYWg4/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/X6fDJktYWg4/sddefault.jpg","isAccessibleForFree":true,"articleSection":"NeetCode","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":"NeetCode","logo":"https://media.daily.dev/image/upload/s--xfR6ZV0s--/f_auto/v1729363595/logos/neetcode","url":"https://daily.dev/sources/neetcode"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/going-fast-vs-slow-in-coding-gdcycdwaa","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"productivity,ai-coding,vibe-coding","timeRequired":"PT1M","video":{"@type":"VideoObject","name":"Going Fast VS. Slow in Coding","description":"A developer reflects on the trade-offs between moving fast and slow when coding with AI assistance. Going too fast risks producing broken or low-quality code...","thumbnailUrl":"https://i.ytimg.com/vi/X6fDJktYWg4/sddefault.jpg","uploadDate":"2026-07-20T14:37:54.591Z","duration":"PT1M","url":"https://api.daily.dev/r/GdcycdWAA","embedUrl":"https://www.youtube.com/embed/X6fDJktYWg4"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"NeetCode","item":"https://daily.dev/sources/neetcode"},{"@type":"ListItem","position":3,"name":"Going Fast VS. Slow in Coding"}]}
```

