It was my first years of being a "software engineer", versus the solo hacker kid who liked making art of over phone lines. So I devoured books which would teach me how to make software with other people and for other people.
Books like the "BeOS Filesystem book" (Practice File System Design) was another classic from the era [1]. It was like today's LLM white papers, learning how a company did something unique, except companies seldom published them because it was a time of IP hoarding.
Unfortunately the books that eventually became the most practical were those by Sutters and Meyers; compendiums on the warts and jewels of C++ that you needed to know to be good at programming in it. Such nitty gritty, much of which was eventually fixed by language design. I really don't miss having to know all that, freeing my mind to consider architecture, design, and delivery.
[1] https://www.nobius.org/dbg/practical-file-system-design.pdf
[1] https://root.cern.ch/TaligentDocs/TaligentOnline/DocumentRoo...