Flurry provides an analytics library to app makers that gets compiled into their applications and then reports back. Flurry compiles data from all users and apps and gets a global portrait.
The title is misleading. This is an article about steel, not heavy metal as most people here expect. The subtitle is more informative: "The creation of stainless steel took equal parts metallurgy and perseverance". The father of modern metal is Iommi U+1F918
Strangely I can't find it in the latest dev release of chrome or chromium, it's still in stable. At least on linux, it also shows firefox's total memory usage, maybe they are doing lots of comparisons.
for 1) you generally don't want to advertise that you are looking for work while still employed. Showing-up in results is the equivalent of painting a target on your back.
We used Papertrail for about 1 year. It works for fairly well for basic reporting, but it gets pretty expensive once you have enough volume. We moved to Logstash, Elasticsearch and Kibana. The power to aggregate, digest, and search the logs from various apps is quite awesome.
The answer can depend on some of the architectural choices you made when you prototyped your product. If the original use-case has changed significantly, and you find yourself fighting the codebase to get it to do what you want today, the technical debt is something to worry about. The same thing applies if you cannot scale to serve clients requiring a lot more volume than what you anticipated originally. It's possible that some clients have modified the original use-case they wanted when they signed-up with you, so your product must evolve to keep serving them. This may require refactoring, whether p/m fit was achieved or not.
