I think we often conflate principles and tools.
Sometimes, we attribute the success of something to the tool we are using instead of the underlying principle that is enabled by the tool.

For example, I use YNAB an expense tracking tool. I could attribute the fact that I have been saving more money due to using YNAB. It would not be a lie but the real truth is that I have been saving more money because I have been able to have a clear overview of all the expenses I have and as a result spend money better. The fact is, good design is invisible, and great tools remove the friction in applying principles to a point where these principles become unnoticeable.

A tool can be an application, a programming framework or a design process. Are we writing more maintainable code due to microservices or because of using a more modular design? Are we delivering faster due to Scrum or due to iterative development?

On the flipside when something does not work as assumed we tend to blame the tool for shortcomings in principles it was not built to address. Is Rails to blame for the lack of thorough design in our application? Should the Web be compared to native platforms?