I would say that the books about Software Engineering help to at least structure your coding thinking a bit. During my career, I’ve seen lots of Python/JS/C# code which was hardly readable because was written in a pretty obscure way, with too many commentaries between the lines of code, using global state too much, using god objects, or totally ignoring language’s OOP capabilities, etc. So it means that these people who wrote the code were not familiar with even these simple principles which seems to be obvious. Like, you probably can’t study Linear Algebra without understanding how to add numbers.
fastai library is structured pretty well though. It decouples models, learners and training loop from each other. It uses callbacks to decouple the specific functionality from the “core”. It also includes lots of tests and proper documentation where it is required. So it actually follows many of these fancy things like SOLID and DRY. Of course, this knowledge comes with experience. You get this experience after many years of coding, or can simplify your journey a bit reading some books
Sure enough, each book has its limitations and should be treated with a grain of salt. At the end of the day, critical thinking is always a good thing.