To blog Previous post | Next post
hello, (again) world!
“Quality is a customer determination … based on the customer’s actual experience with the product or service…”
-A. V. Feigenbaum, “Total Quality Control”, McGraw-Hill, 1983.
Plumbr has evolved. From being a tool that could only detect memory leaks, it has now transformed into one that can report failures, and performance bottlenecks – ultimately improving software quality. What hasn’t changed, is our commitment to the developer community. The core of our product continues to help engineers get feedback about the code they’ve written. And, as a company operated by engineers, developer experience shall continue to remain the nucleus of our product development.
Allow me to introduce myself. I am Ramanujan Iyengar, and I’ve joined Plumbr to focus on marketing efforts. As a product, Plumbr has made remarkable strides forward. As for meeting the market and monetization goes, we have a long way to go. My background is in helping companies where they intersect with people/markets. I’m lucky to have found a wonderful crew at Plumbr, who share my vision – improving software quality. It is an exciting time to be joining the company. Over the next few months, we’re going to be bringing more specialists on board to help our refreshed product meet the market. We’re investing heavily into product development too, which has been our forte all along.
As one of my first steps towards a meaningful marketing strategy, I’m restarting our blogs which lay dormant for a while. We’re dusting off this space, and clearing out the cobwebs. The Plumbr team has an excellent track record of identifying problems that developers encounter. They also have provided very contextual solutions to these. My aim is to continue in the same vein, and expand our horizons, by exploring many more varied themes. Truth be told, the bar is set quite high.
Today, we’re operating with renewed vigour towards helping our customers provide a faster, and more reliable digital user experience. This means less errors for users. This also means less time wasted because of dealing with slow and under-performing software.
We’re quantifying our mission into the following capsules –
- Avoid 100 million failures per year for users
- Save 100 million hours per year for users
- Achieve this by year 2022
Every Plumbr customer will help us progress towards this goal. In effect, helping us only comes around to helping our customers.
Applications may break anywhere. This causes problems to the user experience. This breakage may originate from any part of the tech stack. Rest assured, Plumbr will capture this information as it happens. This is the core promise of “Real-User Monitoring” that we deliver on. With a low performance-overhead on applications, we are able to deliver enormous merit to developers by providing feedback about performance resulting from actual usage of the product.
Engineers, Engineering managers, and other business stakeholders will find a major benefit in making Plumbr part of their workflow. In general, those who share the responsibility for top-notch application performance and focus on software quality will find a use for Plumbr. Our mission is to be identified as a part of the DevOps toolchain that every organization has.
In the coming weeks, I intend to cover a lot more about what we’re doing, and about which direction we intend to steer in. Share our news across different channels, and help more people discover what we have to offer.