Aug 18, 2022Liked by Jelena Cupac

"Poor quality is like an avalanche"

I'm totally stealing that line!

Expand full comment
Aug 18, 2022Liked by Jelena Cupac

I didn't know about ISO-25010. Thanks! You made my day :)

About quality, my biggest challenge has been the same for several years now. How to make the management understand that internal software quality is important. How to use the numbers and data we have at our disposal to get slack time to work on refactoring, decoupling and code organization. It's hard, imo, to make the product and the management understand that X% of the time should be invested in quality. They prefer devs to fix bugs and release new features.

Expand full comment

Thanks for the detailed article!

ISO-25010 was also a discovery for me.

Regarding your closing questions, I believe the quality issues I have encountered were mainly: Maintainability and Performance.

It was easy to spot Performance issues because the QA Engineers would stress the Product, but solving it was another ball game.

Of course, Maintainability was also a factor in poor performance because sometimes you have legacy code that no one dares to touch, which might be the source of your performance issue.

Now that I think about it, Maintainability was also an issue because the Architecture was neither clear nor Modular enough to be flexible for some changes.

With those qualities in mind, I can now look at my work differently.


Expand full comment