Raw LLM Responses

(not op). My advice is to develop a complete understanding of whatever you want to work on. Be it game engines, operating system, hardware, AI, etc. - from high level abstraction down to optimizing every CPU cycle. I strongly recommend handwriting projects from scratch, and figuring out the technical challenges yourself, the architecture, the tradeoffs, and so on. Be the kind of person that doesn’t only know that « we can’t just do X instead of Y», know exactly « why » you can’t do X and exactly how doing X is a bad idea, and why Y is a better idea. Be able to explain that to a 5 year old as well as you can explain it to a senior architect. Have first hand experience of how exactly X messes up projects and why Y is better. The thing is that the field is changing in a way that actual coding skills are less valuable, what is valuable is taste, experience, deep expertise, and an intuitive sense for what is good architecture vs what isn’t.