Systems and processes are good, but if the individual doesn't want to help make it better that is a different but related problem. Testing locally, checking work...that's the behavioral part of this he _can_ control. You can't force him, but might be able to encourage it, not by calling someone out in a code review/etc but privately discussing some local validation they could do. Also, I'm betting the "typos" aren't for corpus words but config strings like swmn0023094 or server names or whatever. That might be more of a custom dictionary type or DSL solution to check values against valid constant values.
It's a question of what you want to invest your time in. Everyone creates output, whether it's lines of code, a smoke screen to hide your social media time, or a set of ongoing conversations and perceptions than you have a use in the organization.
It also comes that the well-compensated people are probably that because they know how to advocate for their worth, which usually includes a list of things they will tolerate and a list they will not, whereas "market rate" is just happy to be there and more inclined to go along with, ya know, whatever.
Exceeds 1. Politics is the craft of influence. And, debatably, there's a politic even when population size=1, between your subconscious instinctive mind (eat the entire box of donuts) versus your conscious mind (don't spike your blood sugar).
"Seamless" may be irrationally exuberant but it's better than the others _at scale_.
LibreOffice, etc. may see similar from the UI end but if you're scaling across multiple sites/archetypes/employee models/regulatory environments, -and- want access to a wide and deep pool of administrative labor, M365 is seamless by comparison.
reply