| Some thoughts based on my limited perspective on things, but just wanting to share. The business cares, first and foremost, in terms of their perspective of your role, on delivery. You have been identified as a gatekeeper, and they depend on you to shepherd this work to the realization of management targets and higher-level goals. Questioning hires is a no-go, mostly because I lack personnel experience and sometimes folks come as a group package. Then you're questioning B2B practices and thus high-level folks as an IC... As for the team, the maverick has a sharp mind for identifying inconsistencies and "holes for ideas." Fill that space with guardrails with your internal framework [1]. Praise the change, yet ask to defer, certain code changes in lieu of more conservative ones. Promise in tiny drips, and point to future stories where you show a roadmap for shiny spikes. The copy-pasters are self-motivated seekers. This is good! They can identify potential solutions quickly. Guardrails with GitHub Actions automation (linting, etc) help here. Teach them what you know. Share ideas and concepts. Try recording some training videos. Schedule a daily group session where you look at everyone's PRs and discuss them. Review comments are softened by a live reading. [1] And refactor later to something less internal. |