I've worked as a developer for 6 years at this same company.
Today my colleague was going to test a feature X with one of our clients. I built feature X and did a manual(s) test on it before telling him "X works! You can test with the client tomorrow!".
Guess what, the logs looked like it ran the code and succeded when I tested it in Azure, that's why I assumed it worked. But I had forgotten it was missing parts of crucial code.
Here is my "excuse" or "explanation" why this happened. The reason I was clueless about missing code in X, is that I have been jumping between X and features A, B, C , D, E, F several times during the last days and weeks. So I added logs to X just to prepare before adding the final code to it. I was blocked by missing specs from the client, so I paused working on X and switched to the other features, before I could add the final code. Then after some days, I forgot that I still had the final code to add.
Since I had added the logs already to X, the logs looked like the feature worked. Like "X started. -> No exceptions. -> Done!". So it logged things like X worked but did only 70% of the work in the background.
Am I insane of I blame this on task switching? How bad of a mistake is this? WTF should I do to not forget the state/progress of the features I'm switching between!?
I'm so fucking mad I let this happen! I could rip someone's head off! I can't take this fucking bullshit anymore!
Thanks!
submitted by /u/ChonkyKitty0
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/D6vFJLW