From The Elements of Programming Style by Brian W. Kernighan and P.J. Plauger Good programming cannot be taught by preaching generalities. The way to learn to program well is by seeing, over and over, how real programs can be improved by the application of a few principles of good practice and a little common sense. Practice in critical reading leads to skill in rewriting, which in turn leads to better writing.

The engineering culture of a company is hugely influential in the kind and quantity of innovation it produces, along with other factors such as quality of code, speed of idea to production, feedback loop, etc. Here are some great videos of Spotify's engineering culture and their current journey. https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/ https://labs.spotify.com/2014/09/20/spotify-engineering-culture-part-2/ Also, check out the first answer to "What makes a good engineering culture?" on quora. Edmond Lau gives deep and comprehensive answer.

Simplicity The design must be simple, both in implementation and interface. It is more important for the implementation to be simple than the interface. Simplicity is the most important consideration in a design. Correctness The design must be correct in all observable aspects. It is slightly better to be simple than correct. Consistency The design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either complexity or inconsistency in the implementation.