Comment by Oras

> The important part seems to be knowing what to ask, what to check, and what you are actually trying to build.

1. Understanding user requirements/pain points is very important and many get it wrong.

2. Doing the architecture of the system within the org env/cloud/infra is often wrong by LLMs (for now).

3. Debugging when things go wrong. What to log, how to log it, and how to ensure not logging much or logging sensitive data.

4. Guide junior engineers, so they are not just accepting what LLMs are spiting.