Thread

1. glouwbug · 1790613143 · focus · HN ↗

   When you write something you constantly remodel your understanding through refactors and rewrites until you internalize it. By internalizing it you gain the capacity to reason about it (during critical downtime) and communicate it. An entire team that can communicate can solve problems together, from one guy's vision to products white boarding to engineering's infrastructure to UX and UI's artistry.

   It boggles me we completely forgot that the world operated like this just 4 years ago

   1. enraged_camel · 1790614282 · focus · HN ↗

      The way I think about it is that understanding is formed in a top-down fashion now, instead of bottom-up. You can look at a feature developed by AI from the outside, and keep peeling the layers and examining them (or having AI explain them to you) until you learn how it works. It's like reading a textbook. It is different than writing the code yourself, or practicing the topic of the textbook yourself. But if you invest the time, it can be just as effective.

      The issue of course is that if you do invest the time, then you're no longer saving time by using AI. You're just spending it reading and trying to understand something you didn't write. And that can be unpleasant in its own way.

      My hot take is that for parts of a system that can be considered its core, forming a deep understanding is almost always important, and so is knowing how the different business domains integrate and where the connection points are. For many others, a high level understanding is sufficient. The difference is that now, with AI, you can make that choice. Before, you had to write everything yourself, and for any sufficiently complex and long-lived system it became impossible to hold all of it in your head.

      1. wholinator2 · 1790615263 · focus · HN ↗

         I disagree that reading a textbook is just as effective as solving problems yourself (this is what i read your statement to mean). It seems fairly obvious from university experience that doing the homework yourself gets you better test grades in the end. You can of course have the AI write the homework but you can't then just watch the AI solve it lest it be drastically muted in effect. Trying things that fail, working hard towards a problem, banging your head against something impossible, these are all worthwhile endeavors. Of course reading the textbook is useful too, very useful! But the textbook does not teach you experience.

         1. shagie · 1790617264 · focus · HN ↗

            > Trying things that fail, working hard towards a problem, banging your head against something impossible, these are all worthwhile endeavors.

            I believe that this is the most important thing... and something that people are afraid of. I've got dozens of personal projects and more than a few branches in my employers repo of things that didn't work... things that I tried, figured out it wasn't going anywhere and went to try some other approach.

            I suspect that there's a bit of sunk cost fallacy going on elsewhere. "If I don't know how to do it, I'm not even going to try" and "I got this far, I'll keep doing it despite it being wrong."

            As a programmer, I am often disappointed at the lack of curiosity in the language and how things could be done. My example would be people writing Java code as if it was still Java 7 - no streams, no Optionals... The fear of having to go back and do it again if using something new doesn't work they'll be in a worse position than if they did it the old way and not realizing that learning what doesn't work or seeing how things that didn't work in this situation may be the right thing for some other future problem.

Unofficial Hacker News client; not affiliated with Y Combinator.