Small bugs aren’t always about coding

I’ve noticed something interesting while working on bugs. Most of the time, the issue isn’t that the code is complex. It’s that the requirements were never clear in the first place. The logic exists in our head, but not in the code or documentation. A simple habit that helps Before jumping into coding, try spending 10 minutes writing things down. Just basic points: What exactly are we building? What are the non-goals? What does success look like? What edge cases might break this? How will this be rolled out? Why this works This small step forces clarity early. It helps: catch gaps in understanding reduce back-and-forth during reviews avoid unnecessary debugging later Curious to know Do you usually write things down before coding, or do you prefer figuring things out while building?