If you’re a sysadmin and/or consultant you should read this and you will probably identify with what the writer is talking about.
Ill admit I know exactly how he feels. I think it applies to consulting as well. Its all too easy in a consultant role to make basic assumptions about an environment only to find out during implementation that that small assumption you made is very wrong and the whole migration is now bollocksed.
If you’re consulting and you’re making assumptions, call them out and call them out early. Its kinda a design document 101 type rule, they always contain an “Assumptions” section but its there for this reason. Oh and don’t be tempted to copy/paste the assumptions from the last engagement. Its important, do it properly.