rtyler
/
brokenco.de
1
0
Fork 0
Code Pull Requests Releases Activity

Update 2023-01-19-eng-leadership-info-management.md

This commit is contained in:
R Tyler Croy 2023-01-20 17:21:55 -08:00 committed by GitHub
parent d22d1cb1a0
commit e926909454
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_posts/2023-01-19-eng-leadership-info-management.md
View File

@ -15,7 +15,7 @@ and leadership positions, I have noticed a number of successful patterns, and
unsuccessful patterns. In this post I want to focus on one of the more
successful patterns: good information management.
Engineering managers are expected to have loads of information ready in their
Engineering managers are expected to have loads of information ready
at all times. The architecture of the systems their team is responsible for,
current project priorities, cross-team points of dependence or collaboration,
and a myriad of other snippets of information. It's a _lot_, but I don't think