logoalt Hacker News

lilerjee • yesterday at 5:00 PM • 3 replies • view on HN

Writing code (Programming) is a thinking tool too.

When you are writing code manually, actually you are thinking about what you are doing, what you will build actually, what are your or users' real requirements, etc.


Replies

fcoury • yesterday at 5:36 PM

This will sound extremely stupid, but I have a skill that I use after letting an agent write code for a new feature. This skill creates a copy of the base branch and shows me each of the diffs that matter (outside of imports and other non-important boilerplate) and then I type it on an editor.

I don't use it too often because of the time it takes, but for critical work it is really good.

I have tried to come up with other equivalent ideas, like asking questions about a specific aspect of a feature, or showing the diff with some gaps to be filled, and even though they help I am still on the look out of methods to "imprint" the understanding of features into our brain.

Does anyone know any good papers or studies that could be useful in this research?

➕ show 2 replies
tayo42 • yesterday at 5:51 PM

As long as you generate code in small increments and intentionally I don't think its a big deal.

SwtCyber • today at 10:01 AM

[dead]