I have had the same problem myself. How frequent do people think it is, that we can't see our own mistake even if it is instantly obvious to somebody else? Does that phenomenon come up in the book?Tim Holloway wrote:. . . Any beginner can spot [the mistake]. I can't because I "know" what's there and thus can't see it's not there. . . .
Tim Driven Development | Test until the fear goes away
Tim Cooke wrote:There is a slightly different flavour of "mistake" that you might categorise as a deliberate mistake
I occasionally introduce deliberate mistakes into posts here, or leave accidental mistakes for tthe punters to find themselves.Tim Cooke wrote:. . . a deliberate mistake. . . .
That is why the documentation should be readily available and regularly updated. The updates should (I think) be identifiable as updates as opposed to part of the original document. It isn't like a thesis (Frank, take notice), where you may decide things haven't gone as expected and have to change dozens of pages and overwrite the old text. Or even delete dozens of pages. In that case you would of course record the changes with Git or similar.Without understanding the motivators behind the original decision you just don't know, until you do, later.
Tim Driven Development | Test until the fear goes away
Sounds like an RFCTim Cooke wrote:Yes, once accepted ADR's are immutable. If you change your mind on a decision later you document that decision in a new ADR and state that it supersedes an existing ADR.
Often the most important part of the news is what they didn't tell.
Tim Driven Development | Test until the fear goes away
Often the most important part of the news is what they didn't tell.