I went back for a PhD after a few years in industry. As a PhD student, my code and habits do not meet the standard of industry. This is because I'm constantly

I went back for a PhD after a few years in industry. As a PhD student, my code and habits do not meet the standard of industry. This is because I'm constantly changing the whole architecture to try new ideas, so I I optimize for small and simple code at the expense of testability, modularization, robustness, etc. It's important to recognize this. You will need to change your style. I can't recommend any one book. I feel like I mostly learned these lessons through random articles, lecture videos, conversations, and personal experience. IMO, some of the most important principles: * Implement as much as possible with pure functions (but don't contort the code to achieve this). * Make your commits as small as possible. Well structured version control history is valuable. * Spend lots of time time thinking about how data flows through your program, more than how the code is organized. * Strongly prefer DAG dependency structure. Write a set of libraries and then a top level program that uses them.