The What, Why and How of (Web, ...) AnalyticsAnand Bagmar
schedule 6 months agoSold Out!
Analytics is changing the way products and services are being created and consumed.
In this session, we will learn
- What is Analytics?
- Why is it important to use Analytics in your product?
- The impact of Analytics not working as expected
We will also see some techniques to test Analytics manually and also automate that validation. But just knowing about Analytics is not sufficient for business now.
There are new kids in town - IoT and Big Data - two of the most used and heard-off buzz words in the Software Industry!
With IoT, with a creative mindset looking for opportunities and ways to add value, the possibilities are infinite. With each such opportunity, there is a huge volume of data being generated - which if analyzed and used correctly, can feed into creating more opportunities and increased value propositions.
There are 2 types of analysis that one needs to think about.
1. How is the end-user interacting with the product? This will give some level of understanding into how to re-position and focus on the true value add features for the product.
2. With the huge volume of data being generated by the end-user interactions, and the data being captured by all devices in the food-chain of the offering, it is important to identify patterns from what has happened, and find out new product / value opportunities based on usage patterns.
Shortening the feedback loop with in-memory integration testingVincent Fuchs
schedule 3 months agoSold Out!
Too often, teams believe that whenever their systems interact with other applications or some infrastructure like a message queue or an email server, there's no other way to test than deploying on a full-fledged environment to get relevant feedback. The main issue with that approach is that feedback loop is not optimum, taking sometimes days or weeks to confirm that a single line of code is working as expected.
Since it's even difficult to perform efficient integration testing manually, most teams don't even try to automate this key stage of the software development lifecycle.
However nowadays, pretty much any external dependency can be replaced by an in-memory equivalent : we're not talking about mocking frameworks here, but about in-memory full implementation of standards, like SQL of course, but also messaging or emailing, which can give developers a very good level of confidence that their code is valid, before they even commit the code.