Peter is the former President of the New Zealand Open Source Society. He is currently working on Business Workflow Automation, and is the core maintainer for Gravity Workflow a GPL workflow engine.
One aspect I have seen in good developers is testing assumptions. When you assume you make an ass out of you and me. The main issue is even being aware you are making one. In debugging and diagnostics you will often find that issues are caused when assumptions are incorrect. A personal example with me was the assumption of thread isolation. A record key was stored and later reused in a thread, only it was assumed the thread would keep the key safe. Turns out not to be the case, and the thread was reused, resulting in corruption of data. An assumption caused a major data corruption because a developer made an assumption and failed to test it. I had asked for the assumption of thread isolation to be tested, but it wasn't.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One aspect I have seen in good developers is testing assumptions. When you assume you make an ass out of you and me. The main issue is even being aware you are making one. In debugging and diagnostics you will often find that issues are caused when assumptions are incorrect. A personal example with me was the assumption of thread isolation. A record key was stored and later reused in a thread, only it was assumed the thread would keep the key safe. Turns out not to be the case, and the thread was reused, resulting in corruption of data. An assumption caused a major data corruption because a developer made an assumption and failed to test it. I had asked for the assumption of thread isolation to be tested, but it wasn't.