‹ BackHN Continuity

Thread

The problem is not AI code, but not knowing about system architecture or intent

388 points · 240 comments · zazuke

  1. hollowonepl · · focus · HN ↗
    AI is not for programmers, they will always complain and given time and resources can of course produce better atomic code. AI is for a combination of a business analyst, architect and product manager in one person who has capacity in coding but decided this is limited role in the whole software engineering lifecycle. With the right attitude and of course certain level of micro management over AI (which they had to do with human programmers as well) they can achieve the same or similar results with much less communication friction, less people to maintain that teamwork and get closer to solving issues they find rather than discussing philosophy of programming and other manifestos of the craft that stopped being prestigious or unique and that’s the key point of complaint when AI is given wrong people to use.
    1. mkleczek · · focus · HN ↗
      That's my recent experience as well. You have to know the domain and have technical knowledge so that you understand (not in every detail) what AI is actually doing and why. You also have to understand what you want and why you want it.

      But once you do, working with AI is like having a very capable team of programmers knowing all programming languages you might need and understanding your goals.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.