3 ms·
Not quite related but right now I'm dealing with an infrastructure architect that a) refuses to document things because of some misguided sense that this will b
by newman314 11y ago
Not quite related but right now I'm dealing with an infrastructure architect that a) refuses to document things because of some misguided sense that this will buy him job security and b) constantly chases the latest shiny tech without regard to how it fits into the overall system or ongoing maintenance and support. Frustrating to say the very least.
- swanson 11y agoChange your job, or change your job. You could discuss how the lack of documentation is causing the team issues; maybe even frame it in a way to highlight how documentation will make him more useful (more time to spend on architecture vs answering questions, better chance that his architecture will be implemented as designed). Express your concerns about introducing new technologies -- something that I've had some success with is asking 'which library/framework/dependency will we able to remove if we add this new one?'. Propose that the architect allocate time to training the team or being on pager duty or fixing maintenance bugs if they feel strongly that a new tech is the best decision. If that doesn't work and the situation is unworkable, then consider a move.