This is a challenge I face as a CTO, given that I strongly believe in Maker's schedule and manager's schedule. So this is what we have implemented at where I am now. Not perfect, but I'm sharing what is working for us.
We have "Wednesday Wisdom" session. This is scheduled every week on Wednesday (as you guessed it), at the same time 4.30 - 5.30. Because it is at the same time, same day, every week, developers can arrange their schedules around this session.
Our discussions mostly revolves around topics that improves our engineering competence (12-factor apps, CI/CD process...) and topics that are trending (bots, ML, microservices ...).
We structure our discussions into two parts: theory + discussions around how that particular topic is relevant for us. Second part is primarily anchored by me or senior folks.
We have an internal knowledge management portal built around liferay. Here we share what we have learned from our projects. This is more like practical knowledge rather than sharing links from internet. We have gamified this a little so that everyone shares.
4.1: This KM portal is the lifeline of ongoing learning for us. There are blogs, discussion forums, document management system, and wiki.
4.2: Standards docs, governance docs are shared via DMS. This gives transparency to entire team about the standards we need to follow and the audit mechanism.
4.3: blogs are more for ephemeral content. content from multiple posts are combined into wiki. Ex: devs from individual teams (mobile, php, python ..) will share their knowledge on security. Then a wiki page is created from these posts to create a consolidated / edited page on security.
4.4: as you can guess, discussion forums are for day to day help requests. "Have you done this ...", "I am stuck on ..." kind of requests.
We continue to review each of these aspects and tweak to experiment. So far this has helped us to be a learning organization.
Amazing, I am a junior dev at my company. I know all the developers have vast amount of knowledge in different domains. We are however a new team, figuring out a lot about the product we are building. I want to help make knowledge sharing a painless and effective process. These points are really helpful in making my plan. Thank you.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a challenge I face as a CTO, given that I strongly believe in Maker's schedule and manager's schedule. So this is what we have implemented at where I am now. Not perfect, but I'm sharing what is working for us.
We continue to review each of these aspects and tweak to experiment. So far this has helped us to be a learning organization.
Amazing, I am a junior dev at my company. I know all the developers have vast amount of knowledge in different domains. We are however a new team, figuring out a lot about the product we are building. I want to help make knowledge sharing a painless and effective process. These points are really helpful in making my plan. Thank you.