[kube-system]

Again, by communicating. If someone doesn't know what they are building, who they are building it for, and why -- then they do not have a solid grasp of the requirements.

[lolive]

Never saw a subcontracting requirement document, stating "the solution is for a bozo-project. so don't spend ages making it robust for the future"

[kube-system]

Effectively communicating as an engineer is not “reading a requirements document”.

If you’re just blindly implementing someone else tech spec, you’re not doing any engineering, you’re just programming.