• annoying_cyclist@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    20 hours ago

    A couple observations on reading this (as someone who heavily uses agentic coding at work and is mostly OK with it):

    • Maybe I’m weird, but I don’t find “we always plan the implementation and make decisions first, and only then do we write the code” to describe my work style that well. If I don’t know how I want something to look, I will frequently just start writing whatever code comes to mind about that something. Most of the code will suck, and I’ll probably throw much of it away, but I find that it’s often a much more efficient way to get to a design that I like than sitting and debating tradeoffs in the abstract. Me writing the code might be slower than an agent writing the code, but that misses the point of the exercise: me writing the code is a way for me to build my own understanding of the problem.
    • The text translation analogy at the beginning is illustrative, I think. A piece of writing has information, but also elements of the author’s wit, humor, tone, their assumptions about us as readers, and the cultural frame they write within. Good writing combines all of those things in an appealing way. At some basic level translation is about translating words correctly, but “correctly” there does a lot of work. It can be very hard to translate a work from one language to another without losing those less obvious characteristics (wit, tone, etc) that make it appealing, especially if you’re translating (e.g.) idioms or slang that don’t have a clear counterpart in your destination language. This is probably familiar to folks who read authors who’ve been translated outside of their native language: the right (or wrong) translator can have a huge impact on what you experience while reading. That’s not a bar we hold for all text (we’ve all seen very poorly translated manuals for cheap consumer electronics that are nonetheless fine because we can figure out what they’re trying to say), and similarly isn’t a bar that holds for all code, but there is some code where the nuances that automatic translation misses are actually important, and where a human touch is useful.