I think you can have a huge impact by institutionalizing knowledge in your organization. Basically, what makes the difference between a junior developer and yo

I think you can have a huge impact by institutionalizing knowledge in your organization. Basically, what makes the difference between a junior developer and yourself ? The gap is huge, and you can help reduce it and compress the time it takes someone joining your organization to become really effective. This will have a huge impact on hiring and retention. You will be able to hire junior developers and turn them into highly productive members. They'll get good faster and will be more likely to be appreciated by the team and feel better because they truly are contributing, etc. A sort of handbook and knowledge base that leveraged what you know. If you were to start a greenfield project, what are the things you'll set up right away based on what you know (monitoring, CI/CD, analytics, etc). A sort of stack for success, but not necessarily tied to technology stack. It can contain rationale: Here's how to test ideas, how to prioritize work, etc. What would I learn working with you for a year? What would you consider to be important lessons and insights ? What are the scars. If you were to disappear, what would you like the person who takes over to know.