A culture which prioritizes writing things down will allow for this type of pattern.
For example, engineers who solve problems should tell stories in their commit messages, providing context, they should output ideas in Slack, and when they have questions, they should provide context and link to references they have explored (tickets, external resources)
It sounds like a lot of work, but in my opinion it's not. That deliberate slow down by one person allows others to grow at a more healthy pace, ultimately progressing the entire team/org (sizing dependent etc.)
I'm not saying Slack should be a knowledge share but it does become a great portal to more information, and ultimately the git log is one of the more important areas in a business to provide learning opportunities for other engineers.
That type of culture will naturally be better at writing documentation and taking care of it because they are practising well formed communication on a regular.
I like to write a personal log of discoveries and my day. It seems to help my team catch up on stuff I am working on.
I got this idea from dask dev notes [1]
Its amazing how every day/week history of project can help new comers.
It also helps getting your team members reach out to you.
When I used to work in office a lot of people used to reach out with problems and I loved solving them. There was a freshness to these problems
But in remote scenario when I joined a new team, no body knew my strengths and I missed those times. But I think a log of this kind can help people know your abilities and give you more opportunities to solve problems outside your routine context.
Comments
A culture which prioritizes writing things down will allow for this type of pattern.
For example, engineers who solve problems should tell stories in their commit messages, providing context, they should output ideas in Slack, and when they have questions, they should provide context and link to references they have explored (tickets, external resources)
It sounds like a lot of work, but in my opinion it's not. That deliberate slow down by one person allows others to grow at a more healthy pace, ultimately progressing the entire team/org (sizing dependent etc.)
I'm not saying Slack should be a knowledge share but it does become a great portal to more information, and ultimately the git log is one of the more important areas in a business to provide learning opportunities for other engineers.
That type of culture will naturally be better at writing documentation and taking care of it because they are practising well formed communication on a regular.
I like to write a personal log of discoveries and my day. It seems to help my team catch up on stuff I am working on.
I got this idea from dask dev notes [1]
Its amazing how every day/week history of project can help new comers.
It also helps getting your team members reach out to you. When I used to work in office a lot of people used to reach out with problems and I loved solving them. There was a freshness to these problems
But in remote scenario when I joined a new team, no body knew my strengths and I missed those times. But I think a log of this kind can help people know your abilities and give you more opportunities to solve problems outside your routine context.
https://blog.dask.org/