<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/im-going-back-to-writing-code-by-hand-ykd6wl6dt" -->

---
title: Im going back to writing code by hand | daily.dev
description: A developer spent 7 months vibe-coding a GPU-aware Kubernetes TUI (k10s) with Claude, then archived it after the codebase collapsed under its own weight. The...
canonical: https://daily.dev/posts/im-going-back-to-writing-code-by-hand-ykd6wl6dt
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Im going back to writing code by hand | daily.dev
og:description: A developer spent 7 months vibe-coding a GPU-aware Kubernetes TUI (k10s) with Claude, then archived it after the codebase collapsed under its own weight. The...
og:url: https://daily.dev/posts/im-going-back-to-writing-code-by-hand-ykd6wl6dt
og:image: https://api.daily.dev/og/posts/yKd6Wl6dT.png
og:image:alt: Im going back to writing code by hand
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.

# Im going back to writing code by hand

**[Hacker News](https://daily.dev/sources/hn)** · 17 min read · 415 upvotes · 43 comments

## Summary

A developer spent 7 months vibe-coding a GPU-aware Kubernetes TUI (k10s) with Claude, then archived it after the codebase collapsed under its own weight. The post dissects five concrete failure patterns that emerge from AI-assisted coding without architectural guardrails: AI builds features not architecture (leading to god objects), the god object as default AI artifact, velocity illusion causing scope creep, positional data as a time bomb, and AI mishandling state transitions causing data races. Each tenet includes real code examples from the failed codebase and specific CLAUDE.md/AGENTS.md directives to prevent the same mistakes. The author is rewriting from scratch in Rust, doing architecture design by hand before any AI-generated code.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.k10s.dev/im-going-back-to-writing-code-by-hand>

## Community discussion

Top comments from developers on daily.dev.

**@coppnic** · 85 upvotes

> Great. What I've noticed by working with AI in development is, how lazy I became. "Wait, this can be done quickly with AI" only to end up like 1 out of 3 times with wrong code and having to fix it by hand anyway.
>
> I am reducing the use of AI while coding and making more thought through decisions on where to use AI and where not.
>
> Where do you people used AI and stopped using it? Where did you focus your AI use in coding?

**@dccodes** · 24 upvotes

> AI can generate code faster than teams can properly review it. That’s becoming a real problem.
>
> A lot of people treat “it compiles” as “it’s correct” and end up inflating the codebase with poorly understood abstractions, duplicated logic, and architectural inconsistencies. Eventually the maintenance and debugging cost gets pushed onto engineers reviewing and operating the system later.
>
> There was also a recent large-scale empirical study on AI-generated code across 6,299 GitHub repositories and 302k+ verified AI-authored commits. The researchers found that AI-assisted commits frequently...

**@baessodiego** · 9 upvotes

> True, AI assisted coding is a nice way to go but using agents like Claude Code or Cursor makes you reeeeeally lazy

**@snazzie** · 8 upvotes

> This is failure in applying knowledge to vibe coding. LLM is good for accelerating your ideas into code. If you have no clue about the topic, no shit its going to spit out sub optimal result.
>
> If you want good architecture, you need to have prior knowledge and guide the AI.

**@radmilomarkovic** · 6 upvotes

> The more you use ai the more you start to depends on it. To use it properly you need to form your own opinions and than build knowledge on top of it. Only that way you are sharpening your skills.

## Similar posts on daily.dev

- [After two years of vibecoding, I'm back to writing by hand](https://daily.dev/posts/after-two-years-of-vibecoding-i-m-back-to-writing-by-hand-mvxk3c8r1) · Hacker News · 82 upvotes · 14 comments
- [10 things I learned writing 49,000 words about vibe coding](https://daily.dev/posts/10-things-i-learned-writing-49-000-words-about-vibe-coding-nwk379qys) · Dynatrace · 1 upvotes · 0 comments
- [I used AI. It worked. I hated it.](https://daily.dev/posts/i-used-ai-it-worked-i-hated-it--selogov58) · Lobsters · 99 upvotes · 18 comments

---

Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#architecture](https://daily.dev/tags/architecture), [#golang](https://daily.dev/tags/golang), [#rust](https://daily.dev/tags/rust), [#vibe-coding](https://daily.dev/tags/vibe-coding)

[View this post on daily.dev](https://daily.dev/posts/im-going-back-to-writing-code-by-hand-ykd6wl6dt)

```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":"Im going back to writing code by hand","url":"https://daily.dev/posts/im-going-back-to-writing-code-by-hand-ykd6wl6dt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/im-going-back-to-writing-code-by-hand-ykd6wl6dt"},"datePublished":"2026-05-11T03:28:09.235Z","dateModified":"2026-05-11T03:28:35.808Z","description":"A developer spent 7 months vibe-coding a GPU-aware Kubernetes TUI (k10s) with Claude, then archived it after the codebase collapsed under its own weight. The...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/80b9b7812a2af53c3a35a45c95253596?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/80b9b7812a2af53c3a35a45c95253596?_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":43,"discussionUrl":"https://daily.dev/posts/im-going-back-to-writing-code-by-hand-ykd6wl6dt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":415},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":43}],"keywords":"kubernetes,architecture,golang,rust,vibe-coding","timeRequired":"PT17M"}
{"@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":"Im going back to writing code by hand"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/im-going-back-to-writing-code-by-hand-ykd6wl6dt","comment":[{"@type":"Comment","text":"Great. What I’ve noticed by working with AI in development is, how lazy I became. “Wait, this can be done quickly with AI” only to end up like 1 out of 3 times with wrong code and having to fix it by hand anyway.\nI am reducing the use of AI while coding and making more thought through decisions on where to use AI and where not.\nWhere do you people used AI and stopped using it? Where did you focus your AI use in coding?","datePublished":"2026-05-11T09:11:52.487Z","url":"https://daily.dev/posts/yKd6Wl6dT#c-o6oKHZ1ce","author":{"@type":"Person","name":"coppnic","url":"https://daily.dev/coppnic","image":"https://media.daily.dev/image/upload/s--8VyNl1cb--/f_auto/v1732889303/avatars/avatar_z5bNZJIOpNguomDjmmrE2"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":85}},{"@type":"Comment","text":"AI can generate code faster than teams can properly review it. That’s becoming a real problem.\nA lot of people treat “it compiles” as “it’s correct” and end up inflating the codebase with poorly understood abstractions, duplicated logic, and architectural inconsistencies. Eventually the maintenance and debugging cost gets pushed onto engineers reviewing and operating the system later.\nThere was also a recent large-scale empirical study on AI-generated code across 6,299 GitHub repositories and 302k+ verified AI-authored commits. The researchers found that AI-assisted commits frequently introduced code smells, correctness issues, and even security issues, with more than 22% of those issues still remaining in the latest repository versions instead of being fixed quickly. The study basically argues that AI can accelerate development, but without strong review and architectural discipline it also introduces long-term technical debt and maintenance overhead.\nArticle Link","datePublished":"2026-05-12T07:50:16.510Z","url":"https://daily.dev/posts/yKd6Wl6dT#c-N75YEW4CP","author":{"@type":"Person","name":"DC CODES","url":"https://daily.dev/dccodes","image":"https://media.daily.dev/image/upload/s--LHhmS6dY--/f_auto/v1780455291/avatars/avatar_xqkbmxS61OKdC4f1OttBw?_a=BAMAMiWQ0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":24}},{"@type":"Comment","text":"True, AI assisted coding is a nice way to go but using agents like Claude Code or Cursor makes you reeeeeally lazy","datePublished":"2026-05-12T09:49:05.515Z","url":"https://daily.dev/posts/yKd6Wl6dT#c-70V3lvZ22","author":{"@type":"Person","name":"baessodiego","url":"https://daily.dev/baessodiego","image":"https://avatars.githubusercontent.com/u/46634034?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":9}},{"@type":"Comment","text":"This is failure in applying knowledge to vibe coding. LLM is good for accelerating your ideas into code. If you have no clue about the topic, no shit its going to spit out sub optimal result.\nIf you want good architecture, you need to have prior knowledge and guide the AI.","datePublished":"2026-05-13T14:02:51.107Z","dateModified":"2026-05-13T14:03:49.774Z","url":"https://daily.dev/posts/yKd6Wl6dT#c-jhdI88sS5","author":{"@type":"Person","name":"aaron cooper","url":"https://daily.dev/snazzie","image":"https://avatars.githubusercontent.com/u/19627023?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":8}},{"@type":"Comment","text":"The more you use ai the more you start to depends on it. To use it properly you need to form your own opinions and than build knowledge on top of it. Only that way you are sharpening your skills.","datePublished":"2026-05-12T15:20:35.393Z","url":"https://daily.dev/posts/yKd6Wl6dT#c-heWr1meqU","author":{"@type":"Person","name":"Radmilo Markovic","url":"https://daily.dev/radmilomarkovic","image":"https://media.daily.dev/image/upload/s--gblKAFwc--/f_auto/v1774901807/avatars/avatar_pw9CkxZCzHWQjy1MHbhtO?_a=BAMAMiWQ0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6}}]}
```