Hoyoverse employees share their experience in a university talk:
Q: Do we (uni students) still need to code traditionally when AI can help us to code?
A: Remember, AI learned it, not you.
If a foodie who has never cooked a day in their life has AI whip up two dishes and then calls themselves a 5* chef, could you accept that?
(Everyone in the audience shook their heads)
Any shortcut you take will come back to bite you with interest sooner or later, especially to "shortcuts" like relying solely on dragging and dropping AI blueprints, or having AI generate all your code.
I also wanna share Cai's quote:
If you don't experience pain while making a game, the end result will most likely be painful.
Q: Then when can we use AI?
A: When you find that writing linked lists and binary trees has become a purely mechanical task—congratulations. The essence of AI is to take over mechanical and repetitive work for you, on the condition that you've mastered it first.