Tags
.NET (42), Meetups (37), dotnetoxford (33), Git (12), Productivity (12), Career (10), LINQPad (8), PublicSpeaking (7), YearInReview (6), Docker (6), CLI (5), Testing (5), Software (4), Workflowy (4), Azure (4), BestPractices (4), Blog (4), Cake (3), Kubernetes (3), Vi (3), Snippets (3), Resharper (2), Podcasts (2), Zoom (2), Xamarin (2), Learning (2), NGINX (2), Evernote (2), Health (2), Debugging (2), DesignPatterns (2), Conference (2), CosmosDB (1), C# (1), Books (1), C# (1), AzureDevOps (1), AzureOxford (1), Aphantasia (1), IoC (1), Hackathon (1), Fonts (1), Documentation (1), dotfiles (1), OGN (1), Microsoft (1), Mocking (1), MVP (1), Neo4j (1), Wyam (1), TimeTracking (1), Powershell (1), RemoteWork (1), Security (1), Serilog (1)07 Apr 2018
Internal Developer Documentation
A very common problem I see in most companies I work with, is both a lack of internal developer documentation, and also a lack of appreciation for how important this really is. There seems to be this assumption that the developer who has all that undocumented knowledge in their head (yes, you know the person) will always be around. They'll never leave for another job, they'll never get run over by a bus, they will always be available. Okay, hopefully the bus thing will never happen, but you get the point! Even when the developer goes on holiday - their knowledge is not available until they get back.
Page 1 of 1