How to Objectively Measure Software Quality?
Software is a system of finite information. This allows us to objectively measure quality, similarly to how we objectively measure chess moves. When Magnus Carlsen wipes his but with Ding Liren, there's no arguing who won or who was the better player. Their moves can be analysed and we can use math to calculate who was the better player. We can even use math to calculate exactly how much better Magnus was compared to Ding.
Software obeys by the same rules due to being a system of finite information, allowing us to objectively measure software quality and compare different systems.
In this video I will measure the quality of Zendesk's most important product and compare it to AINIRO's product. Zendesk has 6,758 employees. Most of their employees went to university according to LinkedIn. 75 went to Berkeley, considered one of the best universities in the world for learning how to become a great software developer. AINIRO had one single employee that implemented its product. This single employee had 9 years of formal education.
According to objective truths, AINIRO's AI chatbot is 80 times better in one of the most important metrics you can measure, and roughly 30 times better on another of the most important metrics. In addition, AINIRO's product obviously have a lot of features that Zendesk does not have.
Extrapolating number of employees multiple by quality, this implies AINIRO's single software developer outperformed the average quality delivered by the average Zendesk employee by roughly 540,640 times. Further considering AINIRO's single employee had 9 years of formal education, while the average Zendesk employee had twice that amount, speaks volumes about how irrelevant it is to have a university degree when it comes to software development, and how counter productive teamwork is when doing creative work delivering innovative products.
Visit https://ainiro.io