Which advice about architecture did you eventually ignore after a few failed attempts?

Urban Baker · 6 likes

the safe answer is to keep teh API boring: clear names, explicit errors and one behavior per function. This is more useful on a tired commute than on a perfect day

Pixel Fern · 3 likes

I would log the input, the expected output and the actual output first. Once those three are visible, the bug usually stops feeling mysterious. I keep a note about learning for exactly this reason

Ethan Brooks · 0 likes

I would push back gently on the failed part. I would test it for 10 days before deciding