Growth
•
0 likes•237 views
What does career growth mean? How does one grow in their career? How do you choose an organisation which allows one to grow? One grows when the environment allows growing. I am not talking about the std. the corporate ladder. One can climb those automatically as the time passes. But all of us agree that it doesn't mean "growth". The key ingredients for the actual growth is the following: * Purpose - the intention to contribute to the well-being of others * Practice - Consistent and deliberate practice * Perseverance - Persistence to try out hard things The talk is about examples and stories about these ingredients and what makes those who have these ingredients and those who don't.
Report
Share
Report
Share
Download to read offline
Recommended
The last mile problem
Have you ever asked a programmer how much longer “this” is going to take? Here goes another typical answer. I am done with most of the tasks, need extra time to finish the last few ones. And the “last few tasks” never ends or takes enormous amounts of time.
On the one hand, we all know that estimates always go wrong. But there is another aspect to this too, i.e. the last mile problem. It can be because of the “fear or shipping” or not applying the guideline “done is better than perfect”.
This talk is about a few tricks I tried not to get into the “perfection” mode; instead, get into the habit of “shipping”. Surprisingly, that helped me to avoid providing estimates :)
Expand Contract Pattern for Continuous Delivery of Databases
This document discusses techniques for continuously delivering database changes, including database refactoring. It describes strategies like splitting tables and columns, adding transition periods, using versioning, automation with testing, and making changes incrementally and reversibly. Database refactoring includes structural, data quality, referential integrity, and transformation changes. Tools, strategies for low risk releases, and patterns like branch by abstraction and strangler are recommended to support evolutionary development and continuous delivery of database changes.
Sprinkle javascript using stimulus js
n this world of Microservices, I am building a Monolith app. In this world of React and Vue, am building a server-side rendered app.
However, I need Javascript. I can’t avoid that. I need some parts of the page updated dynamically. I need to show/hide certain parts of the page depending upon user actions.
I don’t want JQuery for the obvious reasons. Slow.., Heavy and then, of course, it can easily create spaghetti code.
That is when I came across Stimulus JS - a modest Javascript framework. It sprinkles Javascript to add behaviour to your HTML.
It has a controller, action and targets (i.e. the HTML elements). Moreover, it pairs well with Turbolinks. So I don’t need to do the circus of converting JSON to DOM.
I’ve been using Stimulus for over a year and its been quite good. This talk is about my experiences with Stimulus with a few examples. I will share recommendations on where it might be useful and where it is not.
Patterns and practices for evolvability - the key for technical agility
Evolvability refers to the ability to adapt to market needs and the changing environment. Mainly two kinds of evolvability are needed: Product evolving as per the market needs to avoid Building something that nobody wants The architecture and the design of the software evolving to allow the team to make faster changes to the product without breaking things That is why it is crucial to build the right product and build it in the right way.
Expand contract pattern - Continuous Delivery for Databases - DevOpsDays Seattle
Modifying the schema of a production database is *hard*. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Contract pattern is a blueprint for making the database migration. It makes the remodelling both reversible and safe. By *expanding* the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema
- Gain confidence that the migration is safe
We *contract* the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a **continuous delivery way**. Most importantly, without threatening the robustness of your production applications.
Expand contract pattern continuous delivery and databases
Modifying the schema of a production database is hard. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Collapse pattern is a blueprint for making the database migration and makes the remodelling both reversible and safe. By expanding the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema;
- Gain confidence that the migration is safe.
We contract the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a continuous delivery way. Most importantly, without threatening the robustness of your production applications.
Expand contract pattern - Continuous Delivery and Databases
Modifying the schema of a production database is *hard*. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Contract pattern is a blueprint for making the database migration. It makes the remodelling both reversible and safe. By *expanding* the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema
- Gain confidence that the migration is safe
We *contract* the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a **continuous delivery way**. Most importantly, without threatening the robustness of your production applications.
Importance of Showing Up
The talk I gave @ Diversity Meetup [conducted by HasGeek on 7th April, 2018] @ Walmarl Labs.
https://rootconf.in/2018-diversity-meetup-walmart/
Recommended
The last mile problem
Have you ever asked a programmer how much longer “this” is going to take? Here goes another typical answer. I am done with most of the tasks, need extra time to finish the last few ones. And the “last few tasks” never ends or takes enormous amounts of time.
On the one hand, we all know that estimates always go wrong. But there is another aspect to this too, i.e. the last mile problem. It can be because of the “fear or shipping” or not applying the guideline “done is better than perfect”.
This talk is about a few tricks I tried not to get into the “perfection” mode; instead, get into the habit of “shipping”. Surprisingly, that helped me to avoid providing estimates :)
Expand Contract Pattern for Continuous Delivery of Databases
This document discusses techniques for continuously delivering database changes, including database refactoring. It describes strategies like splitting tables and columns, adding transition periods, using versioning, automation with testing, and making changes incrementally and reversibly. Database refactoring includes structural, data quality, referential integrity, and transformation changes. Tools, strategies for low risk releases, and patterns like branch by abstraction and strangler are recommended to support evolutionary development and continuous delivery of database changes.
Sprinkle javascript using stimulus js
n this world of Microservices, I am building a Monolith app. In this world of React and Vue, am building a server-side rendered app.
However, I need Javascript. I can’t avoid that. I need some parts of the page updated dynamically. I need to show/hide certain parts of the page depending upon user actions.
I don’t want JQuery for the obvious reasons. Slow.., Heavy and then, of course, it can easily create spaghetti code.
That is when I came across Stimulus JS - a modest Javascript framework. It sprinkles Javascript to add behaviour to your HTML.
It has a controller, action and targets (i.e. the HTML elements). Moreover, it pairs well with Turbolinks. So I don’t need to do the circus of converting JSON to DOM.
I’ve been using Stimulus for over a year and its been quite good. This talk is about my experiences with Stimulus with a few examples. I will share recommendations on where it might be useful and where it is not.
Patterns and practices for evolvability - the key for technical agility
Evolvability refers to the ability to adapt to market needs and the changing environment. Mainly two kinds of evolvability are needed: Product evolving as per the market needs to avoid Building something that nobody wants The architecture and the design of the software evolving to allow the team to make faster changes to the product without breaking things That is why it is crucial to build the right product and build it in the right way.
Expand contract pattern - Continuous Delivery for Databases - DevOpsDays Seattle
Modifying the schema of a production database is *hard*. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Contract pattern is a blueprint for making the database migration. It makes the remodelling both reversible and safe. By *expanding* the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema
- Gain confidence that the migration is safe
We *contract* the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a **continuous delivery way**. Most importantly, without threatening the robustness of your production applications.
Expand contract pattern continuous delivery and databases
Modifying the schema of a production database is hard. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Collapse pattern is a blueprint for making the database migration and makes the remodelling both reversible and safe. By expanding the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema;
- Gain confidence that the migration is safe.
We contract the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a continuous delivery way. Most importantly, without threatening the robustness of your production applications.
Expand contract pattern - Continuous Delivery and Databases
Modifying the schema of a production database is *hard*. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Contract pattern is a blueprint for making the database migration. It makes the remodelling both reversible and safe. By *expanding* the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema
- Gain confidence that the migration is safe
We *contract* the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a **continuous delivery way**. Most importantly, without threatening the robustness of your production applications.
Importance of Showing Up
The talk I gave @ Diversity Meetup [conducted by HasGeek on 7th April, 2018] @ Walmarl Labs.
https://rootconf.in/2018-diversity-meetup-walmart/
TDD, Refactoring - Workshop
This document discusses test-driven development (TDD) and refactoring using the Gilded Rose kata exercise. It provides rules for TDD, such as only writing production code with a failing test and refactoring code after each test. Simple design principles are outlined, like revealing intention and avoiding duplication. Extreme object-oriented programming rules are also listed, like limiting indentation and properties. The goal is to practice TDD and refactoring skills through the Gilded Rose kata.
Merge hells!! feature toggles to the rescue - Presented @ Agile Toronto
Have you ever wondered how Amazon does deployments in every 11 seconds? Have you ever wondered how frequently Google Chrome updates?
Compare that with an enterprise product you are using or the banking application that you use, it takes weeks or even months for an update. The assumption is that frequent releases are possible for Googles or Amazons or Unicorns. It is not for others.
This talk is about why that assumption is wrong. It can be done anywhere, with enough focus and investment for the Continuous Delivery pipeline to make sure that every commit is releasable or deployable.
And fundamental to Continuous Delivery is Continuous Integration. Continuous Integration guarantees every change committed to the repository is tested and reported about production readiness. And Feature Toggle is for turning features on/off depending upon certain conditions. This opens the opportunity to test certain features quickly with few users for experimentation and learning.
Feature branching has been popular for long, but everyone knows about the “code merge hell”, a common issue because of long-lived branches or infrequent integration. If the team is spending time in fixing the merge hells and checking what part of the code needs to be merged, then it is not the efficient use of human talent.
Merge hells!! Feature toggles to the rescue - DevOpsDays Madison
This document discusses using feature toggles to help manage merge conflicts and allow for continuous delivery of code changes. It notes that building features nobody wants is a waste of resources. Feature toggles allow code to be deployed without being released, avoiding rollback issues. They also enable options like A/B testing and canary releasing. The document recommends managing feature toggles through configuration files and designing systems to be failure-tolerant using circuit breakers. It suggests architectures like branch by abstraction and strangler patterns to help manage feature toggles. Overall, it advocates taking a lean approach by working in small batches to integrate changes continuously.
Technical debt a catch all phrase--
This talk is about bringing in the segregation to identify the debt and the tactics of paying off technical debt in a matured, sustainable manner. Yes, it can be paid off provided enough focus is given to it.
Developing, building, testing and deploying react native apps
React Native is gaining maturity as a cross-platform mobile app development solution. With a strong community around the ecosystem, mobile app development is all set to become simpler and enjoyable.
This talk is about various techniques and tools that are available for building, testing and deploying React Native apps for Android and iOS platforms.
Merge hells!! feature toggles to the rescue
Introducing Continuous Delivery practices to a team in trouble can be daunting. Where do you start ? What do you do first ? Which battle do you pick first ?
I’ll share my experience of guiding a team to achieve a higher degree of delivery maturity. This is a journey from a troublesome, struggling start of chaotic manual deployments, merge hell, regular production roll backs and lost code, to deliver a single commit to trunk automatically and reliably, under an hour, many times a day.
Continuous delivery from the trenches
This document discusses two companies' journeys to continuous delivery of software. The first story describes automating a loan processing platform that now processes close to $4 million in loans with a small team. The second story automated a mobile device management solution for healthcare. The document then outlines the continuous delivery process used, including practices like continuous integration, deployment pipelines and emphasizing delivering business value. Challenges discussed include balancing speed and quality while improving processes through retrospectives.
Continuous delivery for Android
Continuous delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. The idea is to make your software releasable at any moment of time by integrating it continuously and releasing it frequently to get early and frequent feedback.
Because of the approval process that exists in the release process of Android apps, Continuous Delivery is not easy for Android apps as compared to web application deployments. And it's also assumed that not much tools are available to enable Continuous Delivery.
Yes, its still not instant update to the app, but still things are better than how it has been in the past. This talk gives an overview of tools and techniques that can help us to create a pipeline to get fast and frequent feedback through continuous delivery.
Introduction to continuous delivery
Continuous delivery is a software development practice where software can be released to production at any time by building software in a way that enables frequent, automated releases. It involves practices like continuous integration, where code is automatically merged and tested frequently, automated testing and deployment, and using deployment pipelines and tools to streamline the release process. Many large tech companies practice continuous delivery, with some deploying new code in minutes or every 11 seconds to get changes to users quickly.
Merge hells - Feature Toggles to the rescue
The document discusses how feature toggles can help address "merge hells" that can occur with continuous integration. Feature toggles allow incomplete features to be deployed without being released, avoiding the need to rollback deployments. They enable options like A/B testing, canary releasing, and managing experimental and operations toggles. To manage feature toggles, teams should follow mainline development practices, use feature toggle tools, set expiry dates for toggles, and consider toggles as a first step towards continuous delivery.
Deliver with impact
This document discusses impact mapping as a technique for delivering projects with impact. It provides an example of impact mapping for an MDM (mobile device management) product. The key steps of impact mapping include: defining goals and who they impact; identifying desired behaviors and how to enable them; establishing metrics to measure impact; and planning milestones to test assumptions. Impact mapping focuses on creating actual behavioral change rather than just shipping software.
Learnings while building Mobile Device Management [MDM]
The presentation I gave DroidCon India '15 about building device management and our experiences/learnings with the same.
Javascript Testing Tools - Overview
This document discusses different types of testing tools, including unit testing tools like Jasmine and Mocha that allow for quick feedback during test-driven development, end-to-end testing tools like Selenium and Protractor that simulate user interactions, contract testing tools like Pact that test design contracts, and screenshot comparison tools like Wraith and Resemble.js for visual regression testing. It also mentions that unit tests should have high value but low maintenance, end-to-end tests have high effort for maintenance, and that testing strategies should follow the testing pyramid with more unit and integration tests than end-to-end tests.
Continuous delivery using jenkins
This document discusses the importance of continuous delivery using Jenkins. It introduces continuous integration and continuous delivery, explaining that continuous integration provides fast feedback on code changes while continuous delivery provides feedback on production readiness. It outlines how to set up a build pipeline in Jenkins to guarantee production readiness and make releases risk-free and automated. The document emphasizes that continuous delivery satisfies customers through early and frequent delivery of software and encourages teams to take responsibility for releases through continuous improvement.
Culture of Continuous Delivery
This document discusses the culture of continuous delivery. It promotes building quality in from the start, keeping the build always deployable, and continuous improvement. Continuous delivery aspects include automating the build, having a deployable build, continuous integration, build pipelines, configuration management, release management, and using Kanban and feature toggles. Practicing continuous delivery leads to a great culture with values like delighted customers and software craftsmanship. It also discusses concepts from neuroscience like how the brain reacts to stress and rewards that relate to continuous delivery practices.
TDD with AngularJS
This is the slides we used for AngularJS Workshop we did as part of AngularJS Miniconf 2014. https://metarefresh.in/2014/angularjs-miniconf
Droid con 2013 workshop unit testing in android [robolectirc]
This document discusses unit testing Android applications. It introduces Robolectric, an emulation framework that runs unit tests for Android apps on a Java Virtual Machine instead of an emulator or device. This allows tests to run much faster. Robolectric emulates the Android SDK and resources using shadow objects and view/resource loading. It is easy to extend and has good community support. While useful for unit testing, it cannot replace integrated tests that run on actual devices.
Push button deployment using Jenkins
This presentation shows how to create a pipeline in Jenkins CI server for push button deployment. It demonstrates the different tools used for the same and also what are the advantages of having a build pipeline
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
What next after learning python programming basics
What next after learning python programming basics
More Related Content
More from Leena N
TDD, Refactoring - Workshop
This document discusses test-driven development (TDD) and refactoring using the Gilded Rose kata exercise. It provides rules for TDD, such as only writing production code with a failing test and refactoring code after each test. Simple design principles are outlined, like revealing intention and avoiding duplication. Extreme object-oriented programming rules are also listed, like limiting indentation and properties. The goal is to practice TDD and refactoring skills through the Gilded Rose kata.
Merge hells!! feature toggles to the rescue - Presented @ Agile Toronto
Have you ever wondered how Amazon does deployments in every 11 seconds? Have you ever wondered how frequently Google Chrome updates?
Compare that with an enterprise product you are using or the banking application that you use, it takes weeks or even months for an update. The assumption is that frequent releases are possible for Googles or Amazons or Unicorns. It is not for others.
This talk is about why that assumption is wrong. It can be done anywhere, with enough focus and investment for the Continuous Delivery pipeline to make sure that every commit is releasable or deployable.
And fundamental to Continuous Delivery is Continuous Integration. Continuous Integration guarantees every change committed to the repository is tested and reported about production readiness. And Feature Toggle is for turning features on/off depending upon certain conditions. This opens the opportunity to test certain features quickly with few users for experimentation and learning.
Feature branching has been popular for long, but everyone knows about the “code merge hell”, a common issue because of long-lived branches or infrequent integration. If the team is spending time in fixing the merge hells and checking what part of the code needs to be merged, then it is not the efficient use of human talent.
Merge hells!! Feature toggles to the rescue - DevOpsDays Madison
This document discusses using feature toggles to help manage merge conflicts and allow for continuous delivery of code changes. It notes that building features nobody wants is a waste of resources. Feature toggles allow code to be deployed without being released, avoiding rollback issues. They also enable options like A/B testing and canary releasing. The document recommends managing feature toggles through configuration files and designing systems to be failure-tolerant using circuit breakers. It suggests architectures like branch by abstraction and strangler patterns to help manage feature toggles. Overall, it advocates taking a lean approach by working in small batches to integrate changes continuously.
Technical debt a catch all phrase--
This talk is about bringing in the segregation to identify the debt and the tactics of paying off technical debt in a matured, sustainable manner. Yes, it can be paid off provided enough focus is given to it.
Developing, building, testing and deploying react native apps
React Native is gaining maturity as a cross-platform mobile app development solution. With a strong community around the ecosystem, mobile app development is all set to become simpler and enjoyable.
This talk is about various techniques and tools that are available for building, testing and deploying React Native apps for Android and iOS platforms.
Merge hells!! feature toggles to the rescue
Introducing Continuous Delivery practices to a team in trouble can be daunting. Where do you start ? What do you do first ? Which battle do you pick first ?
I’ll share my experience of guiding a team to achieve a higher degree of delivery maturity. This is a journey from a troublesome, struggling start of chaotic manual deployments, merge hell, regular production roll backs and lost code, to deliver a single commit to trunk automatically and reliably, under an hour, many times a day.
Continuous delivery from the trenches
This document discusses two companies' journeys to continuous delivery of software. The first story describes automating a loan processing platform that now processes close to $4 million in loans with a small team. The second story automated a mobile device management solution for healthcare. The document then outlines the continuous delivery process used, including practices like continuous integration, deployment pipelines and emphasizing delivering business value. Challenges discussed include balancing speed and quality while improving processes through retrospectives.
Continuous delivery for Android
Continuous delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. The idea is to make your software releasable at any moment of time by integrating it continuously and releasing it frequently to get early and frequent feedback.
Because of the approval process that exists in the release process of Android apps, Continuous Delivery is not easy for Android apps as compared to web application deployments. And it's also assumed that not much tools are available to enable Continuous Delivery.
Yes, its still not instant update to the app, but still things are better than how it has been in the past. This talk gives an overview of tools and techniques that can help us to create a pipeline to get fast and frequent feedback through continuous delivery.
Introduction to continuous delivery
Continuous delivery is a software development practice where software can be released to production at any time by building software in a way that enables frequent, automated releases. It involves practices like continuous integration, where code is automatically merged and tested frequently, automated testing and deployment, and using deployment pipelines and tools to streamline the release process. Many large tech companies practice continuous delivery, with some deploying new code in minutes or every 11 seconds to get changes to users quickly.
Merge hells - Feature Toggles to the rescue
The document discusses how feature toggles can help address "merge hells" that can occur with continuous integration. Feature toggles allow incomplete features to be deployed without being released, avoiding the need to rollback deployments. They enable options like A/B testing, canary releasing, and managing experimental and operations toggles. To manage feature toggles, teams should follow mainline development practices, use feature toggle tools, set expiry dates for toggles, and consider toggles as a first step towards continuous delivery.
Deliver with impact
This document discusses impact mapping as a technique for delivering projects with impact. It provides an example of impact mapping for an MDM (mobile device management) product. The key steps of impact mapping include: defining goals and who they impact; identifying desired behaviors and how to enable them; establishing metrics to measure impact; and planning milestones to test assumptions. Impact mapping focuses on creating actual behavioral change rather than just shipping software.
Learnings while building Mobile Device Management [MDM]
The presentation I gave DroidCon India '15 about building device management and our experiences/learnings with the same.
Javascript Testing Tools - Overview
This document discusses different types of testing tools, including unit testing tools like Jasmine and Mocha that allow for quick feedback during test-driven development, end-to-end testing tools like Selenium and Protractor that simulate user interactions, contract testing tools like Pact that test design contracts, and screenshot comparison tools like Wraith and Resemble.js for visual regression testing. It also mentions that unit tests should have high value but low maintenance, end-to-end tests have high effort for maintenance, and that testing strategies should follow the testing pyramid with more unit and integration tests than end-to-end tests.
Continuous delivery using jenkins
This document discusses the importance of continuous delivery using Jenkins. It introduces continuous integration and continuous delivery, explaining that continuous integration provides fast feedback on code changes while continuous delivery provides feedback on production readiness. It outlines how to set up a build pipeline in Jenkins to guarantee production readiness and make releases risk-free and automated. The document emphasizes that continuous delivery satisfies customers through early and frequent delivery of software and encourages teams to take responsibility for releases through continuous improvement.
Culture of Continuous Delivery
This document discusses the culture of continuous delivery. It promotes building quality in from the start, keeping the build always deployable, and continuous improvement. Continuous delivery aspects include automating the build, having a deployable build, continuous integration, build pipelines, configuration management, release management, and using Kanban and feature toggles. Practicing continuous delivery leads to a great culture with values like delighted customers and software craftsmanship. It also discusses concepts from neuroscience like how the brain reacts to stress and rewards that relate to continuous delivery practices.
TDD with AngularJS
This is the slides we used for AngularJS Workshop we did as part of AngularJS Miniconf 2014. https://metarefresh.in/2014/angularjs-miniconf
Droid con 2013 workshop unit testing in android [robolectirc]
This document discusses unit testing Android applications. It introduces Robolectric, an emulation framework that runs unit tests for Android apps on a Java Virtual Machine instead of an emulator or device. This allows tests to run much faster. Robolectric emulates the Android SDK and resources using shadow objects and view/resource loading. It is easy to extend and has good community support. While useful for unit testing, it cannot replace integrated tests that run on actual devices.
Push button deployment using Jenkins
This presentation shows how to create a pipeline in Jenkins CI server for push button deployment. It demonstrates the different tools used for the same and also what are the advantages of having a build pipeline
More from Leena N (18)
Merge hells!! feature toggles to the rescue - Presented @ Agile Toronto
Merge hells!! feature toggles to the rescue - Presented @ Agile Toronto
Merge hells!! Feature toggles to the rescue - DevOpsDays Madison
Merge hells!! Feature toggles to the rescue - DevOpsDays Madison
Developing, building, testing and deploying react native apps
Developing, building, testing and deploying react native apps
Learnings while building Mobile Device Management [MDM]
Learnings while building Mobile Device Management [MDM]
Droid con 2013 workshop unit testing in android [robolectirc]
Droid con 2013 workshop unit testing in android [robolectirc]
Recently uploaded
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
What next after learning python programming basics
What next after learning python programming basics
E-commerce Development Services- Hornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdf
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
Requirement Traceability in Xen Functional Safety
Using OpenFastTrace to trace requirements in Xen functional safety
Enums On Steroids - let's look at sealed classes !
These are slides for my session"Enums On Steroids - let's look at sealed classes !" - delivered among others, on Devoxx UK 2024 conference
Mobile app Development Services | Drona Infotech
Drona Infotech is one of the Best Mobile App Development Company In Noida Maintenance and ongoing support. mobile app development Services can help you maintain and support your app after it has been launched. This includes fixing bugs, adding new features, and keeping your app up-to-date with the latest
Visit Us For :
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Unveiling the Advantages of Agile Software Development.pdf
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
Measures in SQL (SIGMOD 2024, Santiago, Chile)
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
UI5con 2024 - Bring Your Own Design System
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
How to write a program in any programming language
How to write a program in any programming language
Odoo ERP Vs. Traditional ERP Systems – A Comparative Analysis
When it is all about ERP solutions, companies typically meet their needs with common ERP solutions like SAP, Oracle, and Microsoft Dynamics. These big players have demonstrated that ERP systems can be either simple or highly comprehensive. This remains true today, but there are new factors to consider, including a promising new contender in the market that’s Odoo. This blog compares Odoo ERP with traditional ERP systems and explains why many companies now see Odoo ERP as the best choice.
What are ERP Systems?
An ERP, or Enterprise Resource Planning, system provides your company with valuable information to help you make better decisions and boost your ROI. You should choose an ERP system based on your company’s specific needs. For instance, if you run a manufacturing or retail business, you will need an ERP system that efficiently manages inventory. A consulting firm, on the other hand, would benefit from an ERP system that enhances daily operations. Similarly, eCommerce stores would select an ERP system tailored to their needs.
Because different businesses have different requirements, ERP system functionalities can vary. Among the various ERP systems available, Odoo ERP is considered one of the best in the ERp market with more than 12 million global users today.
Odoo is an open-source ERP system initially designed for small to medium-sized businesses but now suitable for a wide range of companies. Odoo offers a scalable and configurable point-of-sale management solution and allows you to create customised modules for specific industries. Odoo is gaining more popularity because it is built in a way that allows easy customisation, has a user-friendly interface, and is affordable. Here, you will cover the main differences and get to know why Odoo is gaining attention despite the many other ERP systems available in the market.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
Recently uploaded (20)
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
What next after learning python programming basics
What next after learning python programming basics
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdf
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdf
Enums On Steroids - let's look at sealed classes !
Enums On Steroids - let's look at sealed classes !
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Unveiling the Advantages of Agile Software Development.pdf
Unveiling the Advantages of Agile Software Development.pdf
How to write a program in any programming language
How to write a program in any programming language
Odoo ERP Vs. Traditional ERP Systems – A Comparative Analysis
Odoo ERP Vs. Traditional ERP Systems – A Comparative Analysis
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
Growth
- 1. Growth What does it mean?
- 5. Lessons Learned From the AWS Outage
- 6. Resiliency
- 7. Murphy’s Law
- 8. Resilience Engineering Jesse Robbins Kripa Krishnan John Allspaw
- 10. Homeostasis
- 13. Resilient people
- 14. Ingredients
- 15. The surprising truth about what motivates us
- 21. Contribute to the well-being of others
- 23. Perseverance
- 27. Career Choice
- 34. A little about myself
- 36. Thank you!!! @leenasn / leena@continuousdelivery.in https://medium.com/@leenasn https://medium.com/continuousdelivery