I've always appreciated the approach taken by https://www.aosabook.org/en/index.html which has different depths of analysis and scope and gives the user the option of diving into different types of programs. I usually recommend it to friends /colleagues as a foundation when they've had to write networking or other tight performance applications. Evaluating design decisions and process of app evolution is just as important as where a modern piece of software is because it can help provide similar context around getting the product out there now, rather than perfect later.

Also the world is constantly changing so trying to make a perfect product is partially an evaluation of how long your solution will even be relevant or how isolated it is from external change.