So a few days ago our company held a bugbash. The system is developed since 6 years. And the bugbash lasted 15 minutes or so. The server could not handle 30 users load.
What I found interesting is the aftermatch of this event - a bug was created. There was a lot of hate in it. Devs be disappointed about their work being hindered by a lumbering framework we use. And then there are replies from our internal framework dev team. Jolly good ones. Just imagine the star contrast betweed a comment from a dev stating that it is outrageous that an application cannot handle 30 users load, followed by a reply stating that, well, yes, it could not handle it, but thanks to the new networking (some IT technology) stack the server survived a few watch dog (a thing that stops other things if they take too long) interruptions. Or the fact that the bug issued for this problem is only in scope of analyzing it's cause, not actually fixing it. Yup... the bug is a blocker, and fixing may take a lot of time. Using this leeway one can close the bug early.
To me it looks like the framework team expected this much of an outcome. I am fascinated with the size of the skeleton discovered in their closed. I am enamoured by the way they found a silver lining in our application being useless. I am curious how I will be surprised next time.
Edit: the next week we held another bugbash. Long story short: the application has shown a huge improvement lasting about 15 minutes.
Brak komentarzy:
Prześlij komentarz