I'm guessing people use your learning software during weekdays and working hours (5 days and 8 hours/day). That's 3.4QPS. How many machines are you running on?
Also, I'm really shocked to hear you've not encountered any bugs. How many humans are using your systems? A scale is good enough (100s, 1000s, 10000s?).
Each week the number of individual users was in the thousands; that was usually a rolling window since people tend to not do more than a few e-learning courses per year. I'm certainly not claiming that there are no bugs -- in all likelihood there are -- only that no bugs have yet crashed the system or were obvious and serious enough for users to tell us about.
Who said a "learning action" is equivalent to a query?
>Also, I'm really shocked to hear you've not encountered any bugs.
What's so shocking about it?
You make it sound like there are numerous studies supporting your conclusion, can you link a few of them?
It's a different style of development.
A lot of people have never worked on projects without lots of bugs.
My current F# project for example has almost 100 outstanding issues.
They would be really surprised to know that lots of people have worked on large c projects that are virtually bug free.
Examples of (a) are not always malicious, mind. For a small shop, if your program messes up because during a process the machine it was on got unplugged, it is easy to see why that can be called not a bug in the system. When your shop gets large enough, though, scenarios like that become far too common.