For those wondering, "How to Design Programs"
It's more up to the point instead of going into dogmatic diatribe
It's more evidence based (giving examples, etc)
Go for this one and Bob's your uncle! (or maybe it stops being your uncle, I guess)
What a great book. I second this and add my own "The Pragmatic Programmer: 20th anniversary edition"
That, and "Team Geek", in term of relationship with codes and teammates.
edit: oh, and also it's hard to avoid people checking in and/or editing the generated code
https://www.destroyallsoftware.com/screencasts/catalog/funct...
https://www.destroyallsoftware.com/talks/boundaries
It seems unrelated in the surface, but I feel like they explain the "why" of a software architecture in a much simpler way and without the prescriptive and hand-wavy "trust me" nature of most software architecture books.
I also think some of this... attitude? learning? is what go is trying to activate/take advantage of. Everywhere I've worked has had some monstrously experienced senior dev who could easily crack out a solution to a problem of any difficulty but who refuses to use any abstraction more sophisticated than a for loop.
Go says you don't need anything more sophisticated than a for loop, in fact you can't have anything more sophisticated than a for loop. I guess I'm not there yet but it definitely seems suspicious that the people I know who are most into go are very early in their careers or deeply experienced.
For a junior the answer is more "I'll just use bootstrap and customize as much as needed".
While for a senior it's more in line with "I'll just use bootstrap, but you bet I will be on the designer's ass if they ask to customize stuff where it's not necessary."
There is a reason the mid-level developer wanted to write custom CSS. And the reason is that they didn't have the political capital to make bootstrap alone work in a way that is good for the company.
I don't recommend it to juniors anymore because it hasn't aged well and is for my taste hyperbolic in its promises.
IMHO clean code also is more focused on code implementing "business logic" than "systems programming" for example (probably a bit tricky to actually define what the difference is between these too).