There is a difference between not writing bugs, and checking your invariants.
If you have not read implementation code you are dependent on, you by sefinition have not had the signal that raises that invariant violation into your consciousness.
It would be like a civil engineer building a bridge out of limestone at a thickness that would require a larger thickness of steel and just saying "to hell with it, go figure it out".
The write-only programmer is a threat to themselves and everyone around them. And to be frank, even more dangerous are those members of management who have their expectations around implementation time so skewed by this cavalier attitude toward knowing the dynamics of your stack.
You will make bugs. Crossed invariants are completely preventable though.
If you have not read implementation code you are dependent on, you by sefinition have not had the signal that raises that invariant violation into your consciousness.
It would be like a civil engineer building a bridge out of limestone at a thickness that would require a larger thickness of steel and just saying "to hell with it, go figure it out".
The write-only programmer is a threat to themselves and everyone around them. And to be frank, even more dangerous are those members of management who have their expectations around implementation time so skewed by this cavalier attitude toward knowing the dynamics of your stack.
You will make bugs. Crossed invariants are completely preventable though.