I recently had to justify the amount of effort that software development takes. Someone unfamiliar with the process thought that software development is easy, or that it doesnt take much time. They thought, for example, that an advanced reporting app can get pdf export capability if they just said to the development team, "implement pdf export." Literally, they thought that writing a single line of text like that in a specification document would result in the organization gaining that functionality. 

And I just came across a great example of just how hard software development is. Forget the whole slice of functionality, lets focus on one specific field, a piece of text, pertaining to a specific kind of an object, and how it plays along with the translation framework. We don't even want this piece of text to change - in fact, we want it to not change, we want it to not do anything! We just want it to play along - and it still doesn't work. 

And how much time out it take to fix it? Well, according to the timestamps on the subsequent conversation, the ticket was created in March of 2016. 9 years later, the issue is still open. There are 10 related and referenced issues, of which 7 are closed. It has been somewhat fixed - it is fixed on some versions of the application, but is not fixed on some other ones.

I'm referring to a small conversation in the continuous development of the Drupal platform and CMS. I'm referring to this conversation: https://www.drupal.org/project/drupal/issues/2689459

This conversation is also an example of how to submit a bug report. Notice that the bug report includes steps to reproduce, expected outcome, and actual outcome. See also the outline of the format of a bug report that Wasya Co recommends.

With that said, we at Wasya Co still think that Drupal is an excellent choice for a CMS. We don't say it's bad because it's taking their team more than 9 years to fix a small thing. Drupal is much better than, say, Wordpress. Drupal provides a lot of functionality, is enterprise-grade and production-ready, is one of the most popular frameworks out there, and generally works very well. We're just saying, that a lot of work gets put into making sure that systems work properly. And a successful system will have plenty of unresolved, open tasks. A successful system will not work perfectly all the time. Still, a successful system provides good value when used, resolves a pain point for the end user, or provides an important and useful capability, despite existing bugs.