Director of Developer Relations
YOW! Conferences and Workshops
Member since 6 months
Member since 6 months
With software playing a key role in industrial products and hardware manufacturers preferring to scale number of cores , complexity of present software systems are increasing. It is required for efficient and cost effective development of complex software system.
When building robust real time complex systems which are scalable, it is required to prototype activity and a key component would be capturing behavior using State machines. Modelling the behavior and properties of the system can close the productivity gap in development of complex systems and helps software reuse.
This presentation demonstrates how such a model based abstraction is used for identification of gaps in the requirements, code generation of real time systems and how such a system can be integrated seamlessly into existing systems and can be used for programming protocol, workflow system, simulation …etc.
Hike is an user-centric, mobile-first product, where user experience is the top priority. Hike started as an instant messaging app but during the course of the last four years, it has evolved into a messaging platform that offers a bouquet of features and services on top of messaging.
As a part of quality team, it becomes our primary goal to make sure that app is doing well in terms of performance for a 100+ million user base with an average smartphone cost of $120. We as a product want to achieve and solve lot of user problems but with a constraint of app running with limited device resources.
So the question arise, how do we achieve this goal?
Now, every night, every Sprint (2 weeks) and every public release (monthly), we run our automated perf tests. We measure our app's performance using several app specific use-cases on 4 key areas:
We also benchmark the following scenarios for app latency:
Embracing the fail-fast, fail-early principle, we now provide the necessary feedback to the developers as quickly as possible to avoid downstream delays.
As India's first (and perhaps only) home-grown messaging platform, Hike messenger has been at the forefront of delivering user delight and technological innovation. In achieving our goals, our foray down the Devops route has been an enriching and empowering experience for us as an organisation. In this conversation, we would like to offer an insight into our journey, the challenges we addressed (and are probably still trying to); all the while ensuring the quality of our user experience and product deliverables is not compromised.
Join this session to understand the typical challenges in building a DevOps culture in a startup mould with high product churn. Plus the interesting tweaks we came up with to setup CI pipeline for Mobile Apps, which has various client builds which need to be in sync with server builds.
Aap Ki Adalat is the longest running talk show in the history of Indian television. In this show, the anchor, Mr. Rajat Sharma has grilled over 500 personalities on various sensitive and personal issues. We would like to put the key members of the jQuery Foundation through a similar session, where participants will ask them hard questions around various technical and non-technical choices made by the Foundation and the future direction of the foundation.
At the BEGINNING Of the project: Yay!! Lets automate and cover all test scenarios!! Lets work towards increasing the test coverage !!
After 1 year: Regression suite is too bulky!! I can't maintain it anymore!! Its too flaky!!
Does this conversation ring a bell? Well, this is a common scenario in projects. The UI test automation starts as a saftey net and then becomes a trap net!
Heavy Functional tests layer → Long execution time → Low confidence → Problem of Maintainence
This talk will address these problems in an Agile project. Some solutions that worked in our team. How working as a Team would help prevent these problem?
This talk is intented to demonstrate, Agile adoption is not just process change. We will elaborate the need of engineering practices adoption as well. This will help organization to re-look at their transformation or adoption strategy.
This talk will touch upon the basics of Continous Delivery adoption and practicess like
We will stich together these various practices and procesess together to showcase how a balance of process and engineering practices can help Agility.
The successes of agile software development lies in delivering the workable unit of application with quality as per accepted sprint timelines and receives feedback on the shipped deliverable and incorporate the changes in the current sprint to ensure greater customer satisfaction and trust. Believing in the fact that catch early and fix issues leads to a greater predictability in software deliverable, it becomes imperative to enable developers with set of tools and accelerators which can be leveraged during development. A well-defined continuous integration and delivery process plays a vital role in enabling project teams to leverage all the tools and accelerators during development and automating the testing processes.
However, configuring and managing a CI system at an organization level for each project is a cumbersome task. Also, writing build scripts to automate build actions requires considerable scripting expertise and time. A centralized CI platform that can abstract the complexities of configuring, managing a CI workflow along with the build scripts can ensure greater predictability of software delivery at a far lesser time. Such a platform enables automated build definition creation, to execute build application at regular interval with list of validation embedded along with the compile and build operation. The platform intended to deskill the build definition creation, ensure compliance to continuous integration process. The list of validations that could be part of the continuous integration are automated code analysis, unit testing, code coverage, deployment to multiple environments, functional, performance, security testing, etc. and organization specific validations.
What does it mean to transform core IT systems and deliver new business capabilities through IT during the transformation.
Transformation programmes have multiple goals and many stakeholders - and as the journey starts, all stakeholders need to aware of the goals and agree on the priority in which they need to be met. This drives the perception of value that is delivered by projects.
We would like to share our experience and learnings based on the framework that we evolved in helping stakeholders identify goal priorities and perceived value of projects from two core systems transformation programmes.
We will also be talking about challenges in bringing together stakeholders; agreeing on approaches, relative quantification of project value, selecting the next most valuable project from a pipeline and their impact on the overall transformation.