frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

I'm going back to writing code by hand

https://blog.k10s.dev/im-going-back-to-writing-code-by-hand/
65•dropbox_miner•1h ago

Comments

archleaf•1h ago
So what you really mean is you are going to do better and more detailed skills files so you can get an architecture that you've thought through rather than something random?
dropbox_miner•57m ago
Partly, but the order matters. The CLAUDE.md constraints only work if you designed the architecture first. They're just how you communicate it to the AI. The mistake I made wasn't writing bad skills files, it was not designing anything at all and expecting the AI to make coherent structural decisions across 30 sessions.

The rewrite is me sitting down with a blank doc and drawing the boxes before any code exists. Then the CLAUDE.md enforces what I already decided. Whether that actually holds up as the project grows, I genuinely don't know yet.

cpncrunch•46m ago
Are you really saving any time at all using AI at all then? If you have to write the architecture for it, write all the rules you want it to follow, check everything it's written, and then reprompt it because it's not how you want it?
gjvc•50m ago
have another drink and drive yourself home
binyu•42m ago
> I'm rewriting k10s in Rust. Not because Rust is better but, because it's the language I can steer. I've written enough of it to feel when something's wrong before I can articulate why. That instinct is the one thing vibe-coding can't replace. The AI hands you plausible-looking code. You need a nose for when it's garbage.

Isn't Golang relatively easier to read than Rust? I was under the impression that Rust is a more complex language syntactically.

> The other change is simpler: I'm doing the design work myself, by hand, before any code gets written. Not a vague doc. Concrete interfaces, message types, ownership rules. The architecture decisions that the AI kept making wrong are now made in writing before the first prompt.

This post is good to grasp the difference between "vibe-coding" and using the AI to help with design and architectural choices done by a competent programmer (I am not saying you are not one). Lately I feel that Opus 4.7 involves the user a lot more, even when given a prompt to one-shot a particular piece of software.

dropbox_miner•31m ago
Go reads fine whether the architecture is good or bad, and I couldn't tell the difference until I was in trouble. Rust is harder to read but harder to misuse. The borrow checker would have caught that data race at compile time. I've also just written more Rust. That familiarity matters separately.

+1 on Open 4.7 involving the user a lot more. Rn I'm trying to get to a state where I can codify my design + decision preferences as agents personas and push myself out of the dev loop.

binyu•27m ago
Gotcha, that implies you are going to read the code that the AI produces anyways.

> Go reads fine whether the architecture is good or bad

Were you reading the Golang code all along and got fooled or did you review it after it failed? Sorry I admit I didn't read the whole article.

williamstein•10m ago
He was NOT reading the code: "For 7 months I'd been prompting and shipping without ever sitting down and actually reading the code Claude wrote."
binyu•6m ago
Right, thank you. Personally I think reading all the code that the AI produces is impossible and defeats the purpose of using it. The key is to devise a structured way to interact with it (skills and similar) and use extensive testing along the way to verify the work at all steps.
erelong•35m ago
Can't you just ask AI to break up large files into smaller ones and also explain how the code works so you can understand it, instead of start over from scratch?
dropbox_miner•24m ago
That was actually the first thing I tried. It did a good jov at explaining the code base mess and the architecture. Then I ran 3-4 refactor attempts. Each one broke things in ways that were harder to debug than the original mess. The god object had so many implicit dependencies that pulling one thread unraveled something else. And each attempt burned through my daily Claude usage limit before the refactor was stable.

And I'm sure the rewrite is going to teach me a whole different set of lessons...

joshuanapoli•24m ago
Rewrite following a new architecture plan could get finished pretty quickly, treating the original as a prototype.
epec254•33m ago
Not sure if just me, but this post feels AI written?
pipeline_peak•6m ago
Feels a bit too long winded to be AI generated.
mpurbo•31m ago
Strict SDD might help to constrain and harness the process.
AIorNot•30m ago
This doesnt make much sense the article itself is AI written

It would have been easy to run a few ai agents to review the code and find these issues as well and architect it clearly

keithnz•29m ago
AI writes what you ask it to write, you need to talk to it about architecture. You should have an architecture doc so AI can shape the code based on that, you can get the AI to make the architecture doc also. If using claude you can use the software architecture mode for this.
xantronix•22m ago
So you're not actually writing code by hand? I'm very confused by the difference between the title and the conclusion here.
nothinkjustai•13m ago
Writing code by hand is an oxymoron. You don’t write code with AI, AI doesn’t write, it generates.
apt-apt-apt-apt•9m ago
Outright lie clickbait. As he states himself, he's doing the design work by hand, and will likely still use AI to write code.
EMM_386•8m ago
You don't need to go back to coding by hand if you know how to do it already. There is a middle ground.

If you understand good software architecture, architect it. Create a markdown document just as you would if you had a team of engineers working with you and would hand off to them. Be specific.

Let the AI do the implementation of your architecture.

kypro•7m ago
> I learned over these 7 months

7 months ago was early November. Coding assistants were getting very good back then, but they were still significantly poorer at making good architectural decisions in my experience. They tended to just force features into the existing code base without much thought or care.

Today I've noticed assistants tend to spot architectural smells while working and will ask you whether they should try to address it, but even then they're probably never going to suggest a full refactor of the codebase (which probably is generally the correct heuristic).

My guess is that if you built this today with AI that you wouldn't run into so many of these problems. That's not to say you should build blind, but the first thing that stood out to me was that you starting building 7 months ago and coding assistants were only just becoming decent at that time, and undirected would still generally generate total slop.

shahbaby•6m ago
This reads too much like it was LLM generated. I can't say for sure if it was but I have an allergic reaction to the short snappy know-it-all LLM writing style.
plastic041•3m ago
Title says

> back to writing code by hand

But what they are doing is

> doing the __design work__ myself, by hand, before any code gets written.

So... Claude still is generating the code I guess?

And seriously, I can't understand that they thought their vibe coded project works fine and even bought a domain for the project without ever looking at source code it generated, FOR 7 MONTHS??

SzPredict – open seizure prediction benchmark (all 6 baselines fail)

https://github.com/hyperreal-ai/SzPredict
1•hyperreal-ai•1m ago•0 comments

Remove/replace links pointing to GNOME Calendar, and update branding

https://gitlab.com/linuxmint/pins/mint/gnome-calendar/-/work_items/1
1•prathamtharwani•3m ago•0 comments

Singapore Foreign Minister to Keynote AI Engineer Singapore

https://old.reddit.com/r/singapore/comments/1t97tnx/vivian_balakrishnan_vibe_coded_an_ai_second_b...
1•doppp•7m ago•0 comments

Making cross-platform SIMD code pleasant

https://bkaradzic.github.io/posts/typeless-simd/
1•RUI-0517•14m ago•0 comments

Today Is World Password Day

https://itnerd.blog/2026/05/07/today-is-world-password-day-2/
1•mooreds•15m ago•0 comments

BSides Austin Is on Hold

https://bsidesaustin.com/
1•bean-weevil•16m ago•0 comments

Recursive Multi-Agent Systems

https://recursivemas.github.io/
1•jonbaer•19m ago•0 comments

What can singing mice say about human speech?

https://phys.org/news/2026-05-mice-human-speech.html
1•gmays•20m ago•0 comments

Ask HN: How have you spent time outside work for the past couple of weeks?

2•alex77456•21m ago•0 comments

Up in Smoke

https://thebaffler.com/odds-and-ends/the-profession-that-does-not-exist-symposium
1•NaOH•22m ago•0 comments

Apple's privacy invading tech is likely going mainstream

https://quickthoughts.ca/posts/self-owning-ai-tech/
5•quickthoughts•22m ago•1 comments

Robot Dogs Are a Security Nightmare [video]

https://www.youtube.com/watch?v=lA8WuXDXfcI
1•incomplete•28m ago•0 comments

A Job at OpenAI Became the Greatest Lottery Ticket of the AI Boom

https://www.wsj.com/tech/openai-employee-stock-sales-71ed10bd
3•JumpCrisscross•33m ago•0 comments

Brain motion is driven by mechanical coupling with the abdomen

https://www.nature.com/articles/s41593-026-02279-z
1•refibrillator•34m ago•0 comments

Stack of 500: 500 Production-Tested AI Prompts

https://stackkit.gumroad.com/l/lhxxik
1•ghostreg•36m ago•0 comments

A simple way to understand Bayes' Theorem

https://interestingstuff.xyz/explainers/a-simple-way-to-understand-bayes-theorem/
2•interestingstuf•37m ago•0 comments

Johnny Castaway Screensaver 1992 for macOS Tahoe. Runs as a Screensaver

https://github.com/tallPete/JohnnyCastaway
1•castawayjohnny•43m ago•1 comments

Ask HN: What Wintel/AMD (Laptop) Harware are you liking?

2•aagha•48m ago•0 comments

Fulfilling a life-long dream; 72-year old will graduate from medical school

https://www.washingtonpost.com/lifestyle/2026/05/10/grandmother-medical-school-graduate-residency/
2•wallflower•48m ago•0 comments

To learn to speak you have to speak

http://languagemuse.blogspot.com/2025/06/to-learn-to-speak-you-have-to-speak.html
3•andsoitis•57m ago•0 comments

Pitfalls of Try/Finally in Python

https://pythonkoans.substack.com/p/koan-20-the-unreliable-messenger
2•meander_water•1h ago•0 comments

I'm going back to writing code by hand

https://blog.k10s.dev/im-going-back-to-writing-code-by-hand/
65•dropbox_miner•1h ago•24 comments

Honda Patents a Fake Clutch for Electric Motorcycles

https://electrek.co/2026/05/07/honda-patents-fake-clutch-for-electric-motorcycles-and-it-might-ac...
3•m463•1h ago•1 comments

Freenode IRC Mathematics Seminars (2010)

https://freenode-math.fandom.com/wiki/Seminars
1•susam•1h ago•0 comments

"Cannot be explained" – New ultra stainless steel stuns researchers

https://www.sciencedaily.com/releases/2026/05/260510030950.htm
6•HardwareLust•1h ago•0 comments

Stateless settlement-gated HTTP APIs using UTXO replay protection

https://github.com/ruidasilva/merkleworks-x402-spec
1•ruidasilva•1h ago•0 comments

West Bank settlers forced a Palestinian to dig up the body of his father

https://www.bbc.com/news/articles/cjrpnjpl39po
7•khaledh•1h ago•0 comments

Free/OSS agentic API interrogator

https://github.com/dapooleygmailcom/gaiia-mcp-server
1•dapooley•1h ago•1 comments

Make America AI-Ready

https://beta.dol.gov/ai-ready
2•andsoitis•1h ago•0 comments

Transmission Spectroscopy of the Habitable Zone Exoplanet LHS1140B (2024)

https://arxiv.org/abs/2406.15136
1•johnbarron•1h ago•0 comments