When looking at new tools or new technology, one has to take into consideration whether the benefit of the "new thing" warrants the minimum 100 hours to be even basically proficient in the new tech, and 1000 hours to become an expert in it.

Jr. Developers are always chasing the new cool tech and tools, and never becoming usefully proficient in any of it.

As for the, "Feel comfortable breaking things" - this is also a Jr. developer mindset. In an "ideal coding world" just making the change is great. But in the real world, your business can't always afford to take the time to code, test, refactor, test, refactor, test, implement.

Breaking the code is costly in both time and money. This is something a senior developer has to take into consideration...keeping production profitably running.