Serial podcast creator and .NET Core maniac.
Can often be found talking about everything and nothing on one of the many podcasts that he produces (only one of them is about .NET Core, honest)
Location
Leeds, UK
Education
Computer Science with Games Development - BSc
Work
.NET Development Contractor; Podcast host, producer and editor
I really like the points that you raise, and they've made me stop to think about how different developers could implement them.
Everything that is persistent (recorded talks, articles/wikis). Some of the peers may be missing or not even hired.
We don't tend to record any internal talks that are given, but we do share slide decks and resources discussed.
Post mortems and incident reports I heard are awesome, but takes time to fill them, so the management has to agree on them.
I've only done post mortems in the form of personal blog posts for open source applications. But I like this idea, perhaps they could be included in sprint burndowns/retrospectives, as most of the issues that one solves can easily present for other teams.
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.
I really like the points that you raise, and they've made me stop to think about how different developers could implement them.
We don't tend to record any internal talks that are given, but we do share slide decks and resources discussed.
I've only done post mortems in the form of personal blog posts for open source applications. But I like this idea, perhaps they could be included in sprint burndowns/retrospectives, as most of the issues that one solves can easily present for other teams.