Spent 8 hours in debugging a defect, just to know that code has been completely refactored, that defect is resolved, another critical defect to be fixed at high priority 😭😭😭😭😭😭 in the same code .. refactored by someone else 🥺🥺

And people call .. life of software engineers is so easy and cozy 🤔😰😢🥱

That's why you write a test for the defect case to check whether it's even reproducible.

co·​or·​di·​na·​tion | \ (ˌ)kō-ˌȯr-də-ˈnā-shən\

Definition of coordination

1 : the process of organizing people or groups so that they work together properly and well
2 : the harmonious functioning of parts for effective results The game requires excellent hand-eye coordination.

https://merriam-webster.com/diction...

@electrineer thanks for the efforts to share this piece, btw there is no effective coordination in wfh - the real culprit

@hellomohit you can coordinate effectively in WFH. I'm able to coordinate with my colleagues just using slack and text messages... it's really simple...

"hey, I found a bug, did you know about this?" - "Ah yeah, I'm just fixing it"

"hey, I just made some refactoring changes and pushed them upstream, pull it so you have the latest version"

"hmm, see this message from the QA team? *link*, what do we do about this? do we A or B?" - "I think we should B" - "Great, I can get right on that since I'm done with my tasks" - ":thumbsup:"

It's really not rocket science, open communication is key. Whenever you're not sure you are working on a separate piece of code from your colleagues, you need to sync to make sure you aren't working on something duplicate or that your changes wont cause conflicts and that you're all up to date. It's a good practice to pull often, but it's even better if you guys keep each other in the loop whenever necessary.