It sounds like your assumptions about other developers copy and pasting is lumped in with a bunch of very positive things (asking for help, helping others, being a teammate, being invited to meetings about complex problems). My personal opinion is that software is nuanced and approaching every issue you run into with an assumption that it is important may be a misgiving.
The two second localization change shouldn't be "I have decided to rewrite localization." Similarly for new features, getting an MVP and releasing it internally is often better than writing the best XYZ from the start.
With that being said: there is a time for being very safe and cautious. Sometimes the work you're doing is the core piece of the business -- that deserves respect, lots of extra thought, a full suite of tests, etc.
The two second localization change shouldn't be "I have decided to rewrite localization." Similarly for new features, getting an MVP and releasing it internally is often better than writing the best XYZ from the start.
With that being said: there is a time for being very safe and cautious. Sometimes the work you're doing is the core piece of the business -- that deserves respect, lots of extra thought, a full suite of tests, etc.