I find that LLMs can write poorly structured code if not given a good foundation to do so. The existing code in a repo is what the LLM will see and generally output similar code to.
Given that, I'd recommend the mainstays on good general software design. One of my favorites is "A Philosophy of Software Design" by John Ousterhout. Good general design practices.
Other than that, I think a lot of books generally stay relevant. If it's topic specific, it'll give you a good background on understanding of that topic so you can make sure you or an agent are making sound decisions. Architecture of course is more valuable than ever.
Given that, I'd recommend the mainstays on good general software design. One of my favorites is "A Philosophy of Software Design" by John Ousterhout. Good general design practices.
Other than that, I think a lot of books generally stay relevant. If it's topic specific, it'll give you a good background on understanding of that topic so you can make sure you or an agent are making sound decisions. Architecture of course is more valuable than ever.