2 ms·
I tried using these multiple times (I even know a contributor to this endeavour) but I always struggled with what the scope should be. For a little bit of cont
by dijit 6y ago
I tried using these multiple times (I even know a contributor to this endeavour) but I always struggled with what the scope should be.
For a little bit of context, I work with server architecture in a role that used to be defined as sysadmin, then devops and now SRE.
But there’s many decisions a day and there is a huge trade off in having many records (which become essentially write-only as nobody will trawl through) or too few (which leave some gaps or become very large).
Has anyone found a good threshold for what should be a new ADR from an ops perspective.
- GSGBen 6y ago"Based on my experience in this area and with this business, will I likely be asked about this later and will I confidently and easily be able to answer? Is the expected value of recording higher than the expected value of not (factoring in time, noise, mental load later etc)?" is something like what I ask myself to help decide. Also if you make it filterable and searchable (table instead of document format) you can minimise the issues of having a lot of them. You can add your own scale/importance tags as well to give a list of overview ones to read through too.