DevCon-Shikhar Slides
•
0 likes•153 views
This document discusses strategies for deploying Node applications at scale, including branching strategies, continuous integration, accelerating build times, packaging, deployments, monitoring, and testing. It recommends establishing branching strategies upfront, using feature flags, automating continuous integration tasks, building once and promoting everywhere, using orchestration for deployments, monitoring trends and errors, and functionally and performance testing applications.
Report
Share
Report
Share
Download to read offline
Recommended
Practical Continuous Deployment - Atlassian - London AUG 18 Feb 2014
The document discusses practical approaches to implementing continuous deployment. It describes converting an organization's internal systems to continuous delivery and deployment over six months to address integration issues. Continuous deployment aims to release features, not unfinished work, through automation that makes releasing repeatable. Stakeholders benefit from faster delivery of features to customers and clearer progress signals. The document outlines a development workflow involving tracking requests, branching per feature, automated testing, code reviews, merging to a release branch, and deploying to staging and production. It also addresses challenges of automation and coordination across servers for the "last mile" of deployment.
J hipster
JHipster is a code generator that creates a full-fledged Java web project with a responsive front-end using AngularJS or Angular 2, a documented REST API, tests, security, and database integration. It leverages technologies like Spring Boot, Swagger, Maven, Npm, Gatling, and more. To get started, install JHipster using Yarn or Npm, generate a new project with 'yo jhipster', and make choices like monolithic or microservices, Maven or Gradle, and AngularJS 1 or Angular 2. The generator handles setting up the project with all necessary configurations and components.
Rubyconf presentation
This document discusses challenges and best practices for large-scale Ruby on Rails projects. It covers topics like test-driven development, behavior-driven development with Cucumber, code quality practices like pairing and code reviews, performance optimization tools, and client-side optimizations. The key messages are that automated testing, code quality practices, and performance monitoring are important for large projects to help catch bugs early and reduce development time.
Agile Apps with App Engine
Google App Engine provides advantages like not requiring servers, free usage within quotas, and quick deployment. However, it also has disadvantages like not supporting all dependencies, requiring rewriting of queries and ORMs, and limitations on queries and APIs. Frameworks are recommended for App Engine to enable agile development, team development, maintainability through MVC, and test-driven development. Example frameworks discussed are Django and Kay, noting their quick starts, learning curves, and differences in relationships from traditional servers. Sharding techniques are needed to address query object count limitations.
#ITsubbotnik Spring 2017: Andriy Filatov "Ансамбль солёных поваров: сравнивае...
Моя тема - «Ансамбль солёных поваров: сравниваем Ansible, SaltStack и Chef»
Я буду сравнивать три ведущие, по моему мнению, SCM-системы: Chef, Ansible и SaltStack. Доклад будет приправлен практикой и примерами из жизни, как хорошими так и плохими.
The Key Components of Adopting CI The OpenStack Way
Wajdi Al-Hawari, software developer for Internap, presented at OpenStack Day Canada showcasing how they revamped their Continuous Integration solution the OpenStack way.
Android Continuous Integration and Automation - Enrique Lopez Manas, Sixt
- The document discusses continuous integration and delivery practices using tools like Jenkins and Gradle. It covers branching strategies like using feature branches off of develop/beta branches and hotfix branches off of master. The presenter is a mobile developer and Google Developer Expert.
VodQA_ParallelizingCukes_AmanKing
This was a full length talk presented by Aman King in the vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
Recommended
Practical Continuous Deployment - Atlassian - London AUG 18 Feb 2014
The document discusses practical approaches to implementing continuous deployment. It describes converting an organization's internal systems to continuous delivery and deployment over six months to address integration issues. Continuous deployment aims to release features, not unfinished work, through automation that makes releasing repeatable. Stakeholders benefit from faster delivery of features to customers and clearer progress signals. The document outlines a development workflow involving tracking requests, branching per feature, automated testing, code reviews, merging to a release branch, and deploying to staging and production. It also addresses challenges of automation and coordination across servers for the "last mile" of deployment.
J hipster
JHipster is a code generator that creates a full-fledged Java web project with a responsive front-end using AngularJS or Angular 2, a documented REST API, tests, security, and database integration. It leverages technologies like Spring Boot, Swagger, Maven, Npm, Gatling, and more. To get started, install JHipster using Yarn or Npm, generate a new project with 'yo jhipster', and make choices like monolithic or microservices, Maven or Gradle, and AngularJS 1 or Angular 2. The generator handles setting up the project with all necessary configurations and components.
Rubyconf presentation
This document discusses challenges and best practices for large-scale Ruby on Rails projects. It covers topics like test-driven development, behavior-driven development with Cucumber, code quality practices like pairing and code reviews, performance optimization tools, and client-side optimizations. The key messages are that automated testing, code quality practices, and performance monitoring are important for large projects to help catch bugs early and reduce development time.
Agile Apps with App Engine
Google App Engine provides advantages like not requiring servers, free usage within quotas, and quick deployment. However, it also has disadvantages like not supporting all dependencies, requiring rewriting of queries and ORMs, and limitations on queries and APIs. Frameworks are recommended for App Engine to enable agile development, team development, maintainability through MVC, and test-driven development. Example frameworks discussed are Django and Kay, noting their quick starts, learning curves, and differences in relationships from traditional servers. Sharding techniques are needed to address query object count limitations.
#ITsubbotnik Spring 2017: Andriy Filatov "Ансамбль солёных поваров: сравнивае...
Моя тема - «Ансамбль солёных поваров: сравниваем Ansible, SaltStack и Chef»
Я буду сравнивать три ведущие, по моему мнению, SCM-системы: Chef, Ansible и SaltStack. Доклад будет приправлен практикой и примерами из жизни, как хорошими так и плохими.
The Key Components of Adopting CI The OpenStack Way
Wajdi Al-Hawari, software developer for Internap, presented at OpenStack Day Canada showcasing how they revamped their Continuous Integration solution the OpenStack way.
Android Continuous Integration and Automation - Enrique Lopez Manas, Sixt
- The document discusses continuous integration and delivery practices using tools like Jenkins and Gradle. It covers branching strategies like using feature branches off of develop/beta branches and hotfix branches off of master. The presenter is a mobile developer and Google Developer Expert.
VodQA_ParallelizingCukes_AmanKing
This was a full length talk presented by Aman King in the vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
An almost complete continuous delivery pipeline including configuration manag...
How we have created a build pipeline for continous delivery at Recorded Future. This includes also test of Chef cookbooks and configuration.
Presentation at
Config Management Camp 2014
The Rounds Project: Growing from thousands to millions - Berry Ventura & Yoah...
The document discusses tips for building a great mobile app from the Rounds Android team's experience with their app. It emphasizes supporting many devices and languages, having a robust and crash-free app, using responsive UI design, and surprising and delighting users. Technical strategies discussed include using an executor service for background threads, an IntentService for asynchronous tasks, and events via broadcasts to communicate between components. The goal is to scale the app while keeping it fast, reliable and a great experience for users.
Cypress for Testing
Cypress is an open source, front end testing tool built for modern web applications. It uses JavaScript to write automated end-to-end tests that run directly in the browser engine. Unlike Selenium which runs outside the browser, Cypress operates inside the browser to listen and modify behavior. Cypress makes testing simple through its intuitive API, fast speeds, and ability to work on any frontend framework. The document outlines Cypress' architecture, features, limitations, installation process, project structure, and how to write tests using constructs like describe, it, before, and assertions.
Engineering Tools at Netflix: Enabling Continuous Delivery
An overview of the Netflix build, bake and deploy infrastructure, and the tools used to enable continuous delivery.
Introduction to cypress in Angular (Chinese)
Cypress framework is a JavaScript-based end-to-end testing framework built on top of Mocha – a feature-rich JavaScript test framework running on and in the browser, making asynchronous testing simple and convenient. Cypress is like Protractor for Angular. In this talk, we will talk about how to write cypress test from scratch and some best practice.
Practical continuous quality gates for development process
There are a lot of books and publications about the continuous integration in the world. But in my experience it’s difficult to find information about how to open quality gates between automated tests and to continuous integration practice to in your current project. After reading several articles and even a couple of books you will understand how to work with it. But what next? I will share with you practical tips and tricks on how to lift iron curtain to your automated tests before a continuous quality practice today. It is for this reason why I am pleased to share with you my acquired experience in my presentation.
Continuous delivery with open source tools
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
Continuous integration & deployment
The document discusses options for setting up continuous integration for native iOS applications. It explores unit testing libraries like Sentest and gh-unit, functional testing options like UIAutomation, iCuke, and Frank, and static analysis tools like scan-build. While many existing tools were found lacking or difficult to use in a CI environment, Frank was identified as an actively maintained and easy to run functional testing option. The document also mentions concerns about testing push notifications and API interactions that may break with changes.
Cypress first impressions
The document discusses Cypress, an open source tool for testing web applications. It highlights Cypress' great UI, bundled tools like Sinon and jQuery, features like XHR interception and debugging with time traveling snapshots. It also mentions best practices, using fixtures to load test data, dealing with iframes and OAuth, and known issues.
“Practical DevOps by a small team of devs” by Ilgvars Jēcis from FinoTech at...
Are you in the project which needs ten thousand auto-scaled docker containers on Kubernetes in a multi-regional AWS deployment?
Right.. we also have never done that. Nevertheless, you still might need DevOps 'magic' to deliver those boring everyday IT projects on time and budget.
I will tell our journey with DevOps at a small IT shop and share tools & practices we have tried and which of them were useful and which were total overkill.
Ilgvars is founder & developer at FinoTech. He's been working in IT field for more than 15 years and still kind of enjoys it. Things he likes even more: cooking & eating, few sports activities and finally beer.
Automating Your Way to Greatness by Combining OutSystems CI/CD With the Power...
Having built-in CI/CD capabilities has always been a core tenet of the OutSystems platform. As customer factories have grown and CI/CD pipelines have become more complex, OutSystems has developed an integration with some of the leading CI/CD DevOps tools in the market, Jenkins, and Azure DevOps to tackle some of the challenges of managing enterprise-grade CI/CD pipelines.
Cypress
Cypress is a testing tool that allows for fast, easy, and reliable testing of anything that runs in a browser. It differs from other tools in that it does not use Selenium, focuses on end-to-end testing, works on any front-end framework, uses only JavaScript for tests, and runs much faster than other options. Cypress tests the application as a real user would and allows debugging of test flows. It also supports plugins, common commands and assertions, and has a similar syntax to unit testing frameworks.
IaC? VSTS to the rescue! Abbreviations explained
This document discusses DevOps and infrastructure as code (IaC) using Azure Resource Manager. It begins with an overview of how Agile development processes led to the need for immutable infrastructure and DevOps. Infrastructure is now defined as code using ARM templates to ensure consistency and deployability. The document then outlines how IaC, DevOps tools like VSTS, and a continuous delivery pipeline can be used together for automated deployments in a production environment every sprint. It concludes by advertising an upcoming session on continuous delivery for IT professionals.
Ship It ! with Ruby/ Rails Ecosystem
This document discusses how the Ruby on Rails ecosystem helps development teams by enabling non-blocking development. It outlines tools that allow developers to work independently in sandboxes, manage code through source control, build and deploy automatically, and track issues. This approach prevents blocking, allows continuous integration, and facilitates coordination between developers and operations through notification systems and issue tracking. The document also presents solutions for monitoring servers and jobs that can help reduce the need for a dedicated system administrator.
QA Challenge Accepted 4.0 - Cypress vs. Selenium
This document compares the Cypress and Selenium testing frameworks. It provides an overview of each framework, including supported languages, browsers, and key differences. The document suggests Cypress may signal the end of an era for Selenium as it provides direct browser control, easier debugging of tests, and support for testing desktop applications like Electron. It highlights some unique features of Cypress, such as controlling application state and network traffic. The presentation ends with a Q&A section.
Semi Automatic Code Review
This document summarizes Richard Huang's work developing semi-automatic code review tools and services. It describes his rails_best_practices gem for analyzing Ruby on Rails code and suggesting refactors. It also outlines his railsbp.com online service for automatically reviewing code, collaborating with others, and tracking review histories. The document proposes extending the gem to add new code checking capabilities and making both the gem and service open source.
Continuous delivery - tools and techniques
A talk I gave at the Montgomery County Java User's Group on Continuous Delivery Tools and Techniques.
Introduction To Continuous Integration
This document discusses continuous integration (CI), including why it is important, how it works through its core practices, and how CI evolves over time. CI is meant to catch bugs early, reduce merge conflicts, and make development teams more efficient by implementing automated builds, testing, and code integration. The core practices involve using a single source code repository, automating builds and testing, and publishing the latest version. CI is an evolving practice that changes as tools, languages, and development approaches change over time.
Introduction to Integration Testing With Cypress
A quick overview over Cypress, a front end testing library, going over the motivation to incorporate it for integration tests and some best practices of how to use it.
Learn Key Insights from The State of Web Application Testing Research Report
In a recent study by Dimensional Research of 1,011 development and QA professionals, almost every survey respondent cited that application quality is important, with 84% believing it is very or critically important. Despite this, findings revealed that 94% of teams still face challenges when it comes to conducting adequate QA. View the presentation to learn why organizations must prioritize automated testing and QA practices to deliver high-quality applications and increase customer satisfaction.
The Highlands v2
The author spent nine months in the Scottish Highlands, where she found incredible natural beauty and inspiration as an artist. Some highlights included driving through forests and mountains on the journey there, visiting the Isle of Skye with its stunning beaches, and Glen Affric which she considered the most beautiful place. Though the author had to leave Scotland before her year was up, she was lucky enough to see the Highlands in all four seasons, including a magical experience of heavy snow four days before departing. The natural beauty of the Scottish Highlands left a profound impact and the author hopes to return someday.
PART 1 - Introduction to digital evangelism and discipleship
This document discusses digital evangelism and discipleship. It provides an overview of using digital tools and platforms to share the gospel online and help believers grow in their faith remotely. Examples of digital evangelism mentioned include using websites, apps, email, SMS and social media. The document also lists several online resources and platforms that can be used for digital ministry, evangelism and discipleship. It emphasizes the need for collaborative efforts to utilize digital strategies and fulfill the Great Commission of making disciples of all nations.
More Related Content
What's hot
An almost complete continuous delivery pipeline including configuration manag...
How we have created a build pipeline for continous delivery at Recorded Future. This includes also test of Chef cookbooks and configuration.
Presentation at
Config Management Camp 2014
The Rounds Project: Growing from thousands to millions - Berry Ventura & Yoah...
The document discusses tips for building a great mobile app from the Rounds Android team's experience with their app. It emphasizes supporting many devices and languages, having a robust and crash-free app, using responsive UI design, and surprising and delighting users. Technical strategies discussed include using an executor service for background threads, an IntentService for asynchronous tasks, and events via broadcasts to communicate between components. The goal is to scale the app while keeping it fast, reliable and a great experience for users.
Cypress for Testing
Cypress is an open source, front end testing tool built for modern web applications. It uses JavaScript to write automated end-to-end tests that run directly in the browser engine. Unlike Selenium which runs outside the browser, Cypress operates inside the browser to listen and modify behavior. Cypress makes testing simple through its intuitive API, fast speeds, and ability to work on any frontend framework. The document outlines Cypress' architecture, features, limitations, installation process, project structure, and how to write tests using constructs like describe, it, before, and assertions.
Engineering Tools at Netflix: Enabling Continuous Delivery
An overview of the Netflix build, bake and deploy infrastructure, and the tools used to enable continuous delivery.
Introduction to cypress in Angular (Chinese)
Cypress framework is a JavaScript-based end-to-end testing framework built on top of Mocha – a feature-rich JavaScript test framework running on and in the browser, making asynchronous testing simple and convenient. Cypress is like Protractor for Angular. In this talk, we will talk about how to write cypress test from scratch and some best practice.
Practical continuous quality gates for development process
There are a lot of books and publications about the continuous integration in the world. But in my experience it’s difficult to find information about how to open quality gates between automated tests and to continuous integration practice to in your current project. After reading several articles and even a couple of books you will understand how to work with it. But what next? I will share with you practical tips and tricks on how to lift iron curtain to your automated tests before a continuous quality practice today. It is for this reason why I am pleased to share with you my acquired experience in my presentation.
Continuous delivery with open source tools
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
Continuous integration & deployment
The document discusses options for setting up continuous integration for native iOS applications. It explores unit testing libraries like Sentest and gh-unit, functional testing options like UIAutomation, iCuke, and Frank, and static analysis tools like scan-build. While many existing tools were found lacking or difficult to use in a CI environment, Frank was identified as an actively maintained and easy to run functional testing option. The document also mentions concerns about testing push notifications and API interactions that may break with changes.
Cypress first impressions
The document discusses Cypress, an open source tool for testing web applications. It highlights Cypress' great UI, bundled tools like Sinon and jQuery, features like XHR interception and debugging with time traveling snapshots. It also mentions best practices, using fixtures to load test data, dealing with iframes and OAuth, and known issues.
“Practical DevOps by a small team of devs” by Ilgvars Jēcis from FinoTech at...
Are you in the project which needs ten thousand auto-scaled docker containers on Kubernetes in a multi-regional AWS deployment?
Right.. we also have never done that. Nevertheless, you still might need DevOps 'magic' to deliver those boring everyday IT projects on time and budget.
I will tell our journey with DevOps at a small IT shop and share tools & practices we have tried and which of them were useful and which were total overkill.
Ilgvars is founder & developer at FinoTech. He's been working in IT field for more than 15 years and still kind of enjoys it. Things he likes even more: cooking & eating, few sports activities and finally beer.
Automating Your Way to Greatness by Combining OutSystems CI/CD With the Power...
Having built-in CI/CD capabilities has always been a core tenet of the OutSystems platform. As customer factories have grown and CI/CD pipelines have become more complex, OutSystems has developed an integration with some of the leading CI/CD DevOps tools in the market, Jenkins, and Azure DevOps to tackle some of the challenges of managing enterprise-grade CI/CD pipelines.
Cypress
Cypress is a testing tool that allows for fast, easy, and reliable testing of anything that runs in a browser. It differs from other tools in that it does not use Selenium, focuses on end-to-end testing, works on any front-end framework, uses only JavaScript for tests, and runs much faster than other options. Cypress tests the application as a real user would and allows debugging of test flows. It also supports plugins, common commands and assertions, and has a similar syntax to unit testing frameworks.
IaC? VSTS to the rescue! Abbreviations explained
This document discusses DevOps and infrastructure as code (IaC) using Azure Resource Manager. It begins with an overview of how Agile development processes led to the need for immutable infrastructure and DevOps. Infrastructure is now defined as code using ARM templates to ensure consistency and deployability. The document then outlines how IaC, DevOps tools like VSTS, and a continuous delivery pipeline can be used together for automated deployments in a production environment every sprint. It concludes by advertising an upcoming session on continuous delivery for IT professionals.
Ship It ! with Ruby/ Rails Ecosystem
This document discusses how the Ruby on Rails ecosystem helps development teams by enabling non-blocking development. It outlines tools that allow developers to work independently in sandboxes, manage code through source control, build and deploy automatically, and track issues. This approach prevents blocking, allows continuous integration, and facilitates coordination between developers and operations through notification systems and issue tracking. The document also presents solutions for monitoring servers and jobs that can help reduce the need for a dedicated system administrator.
QA Challenge Accepted 4.0 - Cypress vs. Selenium
This document compares the Cypress and Selenium testing frameworks. It provides an overview of each framework, including supported languages, browsers, and key differences. The document suggests Cypress may signal the end of an era for Selenium as it provides direct browser control, easier debugging of tests, and support for testing desktop applications like Electron. It highlights some unique features of Cypress, such as controlling application state and network traffic. The presentation ends with a Q&A section.
Semi Automatic Code Review
This document summarizes Richard Huang's work developing semi-automatic code review tools and services. It describes his rails_best_practices gem for analyzing Ruby on Rails code and suggesting refactors. It also outlines his railsbp.com online service for automatically reviewing code, collaborating with others, and tracking review histories. The document proposes extending the gem to add new code checking capabilities and making both the gem and service open source.
Continuous delivery - tools and techniques
A talk I gave at the Montgomery County Java User's Group on Continuous Delivery Tools and Techniques.
Introduction To Continuous Integration
This document discusses continuous integration (CI), including why it is important, how it works through its core practices, and how CI evolves over time. CI is meant to catch bugs early, reduce merge conflicts, and make development teams more efficient by implementing automated builds, testing, and code integration. The core practices involve using a single source code repository, automating builds and testing, and publishing the latest version. CI is an evolving practice that changes as tools, languages, and development approaches change over time.
Introduction to Integration Testing With Cypress
A quick overview over Cypress, a front end testing library, going over the motivation to incorporate it for integration tests and some best practices of how to use it.
Learn Key Insights from The State of Web Application Testing Research Report
In a recent study by Dimensional Research of 1,011 development and QA professionals, almost every survey respondent cited that application quality is important, with 84% believing it is very or critically important. Despite this, findings revealed that 94% of teams still face challenges when it comes to conducting adequate QA. View the presentation to learn why organizations must prioritize automated testing and QA practices to deliver high-quality applications and increase customer satisfaction.
What's hot (20)
An almost complete continuous delivery pipeline including configuration manag...
An almost complete continuous delivery pipeline including configuration manag...
The Rounds Project: Growing from thousands to millions - Berry Ventura & Yoah...
The Rounds Project: Growing from thousands to millions - Berry Ventura & Yoah...
Engineering Tools at Netflix: Enabling Continuous Delivery
Engineering Tools at Netflix: Enabling Continuous Delivery
Practical continuous quality gates for development process
Practical continuous quality gates for development process
“Practical DevOps by a small team of devs” by Ilgvars Jēcis from FinoTech at...
“Practical DevOps by a small team of devs” by Ilgvars Jēcis from FinoTech at...
Automating Your Way to Greatness by Combining OutSystems CI/CD With the Power...
Automating Your Way to Greatness by Combining OutSystems CI/CD With the Power...
Learn Key Insights from The State of Web Application Testing Research Report
Learn Key Insights from The State of Web Application Testing Research Report
Viewers also liked
The Highlands v2
The author spent nine months in the Scottish Highlands, where she found incredible natural beauty and inspiration as an artist. Some highlights included driving through forests and mountains on the journey there, visiting the Isle of Skye with its stunning beaches, and Glen Affric which she considered the most beautiful place. Though the author had to leave Scotland before her year was up, she was lucky enough to see the Highlands in all four seasons, including a magical experience of heavy snow four days before departing. The natural beauty of the Scottish Highlands left a profound impact and the author hopes to return someday.
PART 1 - Introduction to digital evangelism and discipleship
This document discusses digital evangelism and discipleship. It provides an overview of using digital tools and platforms to share the gospel online and help believers grow in their faith remotely. Examples of digital evangelism mentioned include using websites, apps, email, SMS and social media. The document also lists several online resources and platforms that can be used for digital ministry, evangelism and discipleship. It emphasizes the need for collaborative efforts to utilize digital strategies and fulfill the Great Commission of making disciples of all nations.
мастер класс изготовление из бумаги снегурочки и деда мороза
мастер класс изготовление из бумаги снегурочки и деда мороза
Sin título 1
Los derechos del niño son normas jurídicas que protegen a personas menores de edad de forma inalienable e irrenunciable. Varios documentos internacionales como la Declaración de los Derechos del Niño y la Convención sobre los Derechos del Niño consagran los derechos del niño. Los principios clave incluyen la no discriminación, el interés superior del niño, el derecho a la vida y al desarrollo, y la participación de los niños en asuntos que les afectan.
Face & Body Painting (Evgeny Freeone)
Face and body painting is a service offered by Evgeny Freeone. He has over 10 years of experience creating unique and artistic designs on people's faces, arms, legs and other parts of the body. Customers can book appointments on his website to have their faces and bodies painted for events, photoshoots, festivals or just for fun.
Gre Quant - Demo ppt
The document provides a strategy guide for the GRE exam. It outlines the structure and format of the GRE, including the analytical writing, verbal reasoning, and quantitative reasoning sections. It also describes the different types of questions that may appear on the quantitative reasoning section, such as problems with a single correct answer, problems with multiple correct answers, quantitative comparison questions, and numerical entry questions. Examples of questions are provided for each type to illustrate the formats. The guide concludes by thanking the reader and providing contact information for additional GRE preparation resources.
La leyenda del beso/The Legend of the kiss.
El documento narra la historia de Mario, un noble español que regresa de cazar y se encuentra con una tribu gitana que pide permiso para acampar. Mario queda impresionado por la belleza de una joven gitana llamada Amapola. Más tarde, Amapola resulta herida y es llevada al castillo de Mario, donde él se enamora de ella. Sin embargo, la hechicera gitana Ulita advierte a Mario que si besa a Amapola encontrará la muerte, debido a una antigua maldición sobre la madre de Amapola.
Managing climate risks through resilient crop interventions and climate-smart...
Managing climate risks through resilient crop interventions and climate-smart...CCAFS | CGIAR Research Program on Climate Change, Agriculture and Food Security
This is a presentation for CCAFS East Africa by Maren Radeny at the Symposium on Climate Change Adaptation in Africa 2016 "Fostering African Resilience and Capacity to Adapt" in Addis Ababa, Ethiopia, on 21st-23rd February 2016 e learning
Este documento presenta información sobre el uso del e-learning en la enseñanza superior. En menos de 3 oraciones, resume lo siguiente: El documento discute las ventajas y desventajas del e-learning, incluyendo la flexibilidad y acceso ilimitado a la información que ofrece, pero también los desafíos de la falta de estructura y motivación para algunos estudiantes. Además, presenta diferentes formas de entrega de contenido a través del e-learning como aprendizaje sincrónico, asincrónico y basado en la web.
Diffy : Automatic Testing of Microservices @ Twitter
Agile development has become a norm nowadays. Though it fosters faster product development cycles, it often results in a higher number of functional and/or performance regressions. In an SOA setting such as Twitter, such regressions may cascade from one service to one or more services. Detecting such regressions manually is not practically feasible in light of the hundreds of services and tens of thousands of metrics each service collects. To this end, we developed a novel tool called Diffy to automatically detect such regressions.
The key highlights of the talk are the following:
A simple yet effective approach for detecting functional regressions. False positives are minimized via statistical analysis of metrics obtained from a tuple <primary,> of nodes, where the same traffic is sent to each node.
An ensemble approach to performance regression. The need for an ensemble of classifiers stemmed from the multifaceted characteristics of the performance data. In order to minimize the impact of variability of hardware performance across nodes, we used two clusters – instead of a tuple of nodes – corresponding to the release candidate and production code. The approach is robust against the presence of anomalies in the performance data.
The proposed techniques work well with minute data. Diffy has been in use in production by multiple services at Twitter, and has been baked into the continuous build process so as to actively detect functional and/or performance regressions.
We shall take the audience through how the techniques are being used at Twitter with REAL data.
MOOC: tendencia de inspiración
MOOC: tendencia de inspiración.
2° parte curso: MOOC en el escenario educativo.
Universidad Nacional del Nordeste. Resistencia, Chaco.
MOOC en el escenario educativo
Este documento describe la evolución de la educación a distancia a través de cinco generaciones, desde el uso inicial de la radio y la televisión hasta el aprendizaje en línea actual mediante plataformas como Coursera y edX. También analiza diferentes tipos de MOOC (cMOOC centrados en la interacción y xMOOC centrados en el contenido) y presenta ejemplos de plataformas populares de MOOC.
Infrastructure as code might be literally impossible part 2
The document discusses various issues with infrastructure as code including complexities that arise from software licenses, bugs, and inconsistencies across tools and platforms. Specific examples covered include problems with SSL and APT package management on Debian/Ubuntu, Linux networking configuration difficulties, and inconsistencies in Python packaging related to naming conventions for packages containing hyphens, underscores, or periods. Potential causes discussed include legacy code, lack of time for thorough testing and bug fixing, and economic pressures against developing fully working software systems.
PMI-ACP Lesson 12 Knowledge and Skills Nugget 2
This document provides an overview of key concepts for the PMI-ACP certification, including:
- Agile emphasizes face-to-face communication and provides tools like daily stand-ups and retrospectives to avoid mismatched expectations.
- Feedback techniques in Agile include prototypes, simulations, demonstrations, and evaluations.
- Incremental delivery allows for partial products to be deployed after iterations for early feedback and ROI.
- Agile promotes knowledge sharing through practices like daily stand-ups, pair programming, and retrospectives.
- Problems in Agile are examined at the process, quality, and team dynamics levels using techniques such as establishing a devil's advocate and probing questions.
- An Agile leader communicates
PMI-ACP Lesson 08 Nugget 1 Agile & Scrum Value-based Prioritization
This document discusses financial analysis techniques for project prioritization. It covers concepts like net present value (NPV), internal rate of return (IRR), return on investment (ROI), payback period, and time value of money. Formulas are provided for calculating future value, present value, NPV, and IRR. Examples are included to demonstrate how to use these techniques to evaluate and select between projects. The key message is that projects with higher NPV, IRR and ROI but lower payback period should be prioritized.
Viewers also liked (20)
PART 1 - Introduction to digital evangelism and discipleship
PART 1 - Introduction to digital evangelism and discipleship
мастер класс изготовление из бумаги снегурочки и деда мороза
мастер класс изготовление из бумаги снегурочки и деда мороза
Managing climate risks through resilient crop interventions and climate-smart...
Managing climate risks through resilient crop interventions and climate-smart...
Diffy : Automatic Testing of Microservices @ Twitter
Diffy : Automatic Testing of Microservices @ Twitter
Infrastructure as code might be literally impossible part 2
Infrastructure as code might be literally impossible part 2
PMI-ACP Lesson 08 Nugget 1 Agile & Scrum Value-based Prioritization
PMI-ACP Lesson 08 Nugget 1 Agile & Scrum Value-based Prioritization
Similar to DevCon-Shikhar Slides
Angular 2 overview
Angular 2 is a new version of AngularJS that is currently in alpha. It embraces modern web standards like Shadow DOM and Web Workers. Angular 2 components replace directives and use classes instead of controllers. Templates are now called views. Two-way binding and ng-repeat are changed. The API is still changing but you can try it now on angular.io.
Dealing With Legacy: The Real-World Experience
This document summarizes the experience of a team dealing with legacy code in a critical ordering application. Some of the challenges they faced included a mix of junior and senior developers, preparing for an upgrade, and planning a major design overhaul of legacy code with little documentation. Things that worked well included Scrum processes, bi-weekly releases, automation, and opportunistic refactoring. Areas for improvement included larger design refactors, more testing, and test-driven development. In the future, the author would have liked living documentation, monitoring, and more efficient UI testing. The presentation warns against creating legacy code and encourages design refactoring and better practices.
Project management frameworks for software developing
This document discusses various project management frameworks that can help organize projects and deliver features on time. It outlines some common problems like failing to meet deadlines and difficulties estimating timelines. It then describes frameworks like the Waterfall model, Lean software development, Extreme Programming (XP), Scrum, Kanban, and DevOps. It notes limitations of the traditional Waterfall approach and proposes iterative models like cyclical Waterfall/Lean and XP to allow for refinement over multiple sprints. Scrum and Kanban are presented as lightweight frameworks suitable for smaller projects, emphasizing concepts like continuous integration, automation, and incremental improvements.
Tips For Maintaining OSS Projects
Automate release processes, think of project maintenance as learning opportunities, and build what you actually need. Tips include using plugins like sbt-sonatype to enable one-command releases to Maven Central, learning new technologies through small contributions to open source projects, and focusing on libraries that solve daily tasks and application development needs. Examples include libraries for packaging, release, logging, configuration, and serialization created for Scala projects.
TDD and Related Techniques for Non Developers (2012)
A presentation I gave last year about TDD special for non technical people like project managers and managers.
Customized Scrum
This document discusses customizing the Scrum process for a startup company. It describes the author's experience being assigned the Product Owner and Scrum Master roles without previous Scrum experience. The author learned Scrum and implemented it in their own way for their company. The document then provides an overview of key Scrum concepts like sprints, product backlogs, daily standups, sprint reviews, and retrospectives. It also discusses tools that can be used to support the Scrum process.
Using BladeRunnerJS to Build Front-End Apps that Scale - Fluent 2014
Developing large apps is difficult. Ensuring that code is consistent, well structured, tested and has an architecture that encourages enhancement and maintainability is essential. When it comes to building large server-focused apps the solutions to this problem have been tried and tested. But, how do you achieve this when building HTML5 single page apps?
BladeRunnerJS is an open source developer toolkit and lightweight front-end framework that has helped Caplin Systems ensure that a 200k LoC JavaScript codebase hasn’t become a tangled mess of unstable spaghetti code. This codebase is packaged and delivered to customers as an SDK. Additionally customers receive a getting started application of around 50k LoC for them to build upon, and they’re expected not to turn that into a tangled … you get the idea.
In this talk you’ll learn the main concepts to apply when building a front-end app that scales and how BladeRunnerJS can support the development process.
Microservices: The Best Practices
Presentation about best practices when implementing microservice architecture, which was given during EastCode sessions.
What is this agile thing anyway
The document discusses various concepts and practices related to agile software development, including:
- The agile manifesto which emphasizes individuals, working software, customer collaboration, and responding to change.
- Core agile concepts like short iterations, planning one iteration at a time, frequent code releases and customer feedback.
- Specific agile frameworks like eXtreme Programming (XP), Scrum, and Kanban/Lean.
- Testing approaches like unit tests, integration/acceptance tests, test-driven development (TDD), and behavior-driven development (BDD).
- Other practices like continuous integration, domain-driven design (DDD), and DevOps which emphasize collaboration between developers and operations
Agile
This document provides an overview of agile methodology and several agile frameworks. It begins with a brief history of the traditional waterfall model and its limitations. It then introduces the agile manifesto and some core agile principles. Several agile frameworks are described at a high level, including scrum, kanban, extreme programming, and others. Key practices of scrum and extreme programming like iterations, user stories, stand-up meetings, and test-driven development are defined. The document aims to give the reader a broad understanding of agile concepts and some of the most commonly used agile frameworks and practices.
Build software like a bag of marbles, not a castle of LEGO®
If you have ever played with LEGO®, you will know that adding, removing or changing features of a completed castle isn’t as easy as it seems. You will have to deconstruct large parts to get to where you want to be, to build it all up again afterwards. Unfortunately, our software is often built the same way. Wouldn’t it be better if our software behaved like a bag of marbles? So you can just add, remove or replace them at will?
Most of us have taken different approaches to building software: a big monolith, a collection of services, a bus architecture, etc. But whatever your large scale architecture is, at the granular level (a single service or host), you will probably still end up with tightly couple code. Adding functionality means making changes to every layer, service or component involved. It gets even harder if you want to enable or disable features for certain deployments: you’ll need to wrap code in feature flags, write custom DB migration scripts, etc. There has to be a better way!
So what if you think of functionality as loose feature assemblies? We can construct our code in such a way that adding a feature is as simple as adding the assembly to your deployment, and removing it is done by just deleting the file. We would open the door for so many scenarios!
In this talk, I will explain how to tackle the following parts of your application to achieve this goal: WebAPI, Entity Framework, Onion Architecture, IoC and database migrations. And most of all, when you would want to do this. Because… ‘it depends’.
Angular 2
Angular is a platform for building mobile and desktop web applications. It is no longer just a framework. Angular 2 offers improvements such as faster performance, modularity, support for modern browsers, and reactive programming using RxJS. Key parts of Angular include templates, directives, data binding, components, services, modules, and dependency injection. Features like Ahead-of-Time compilation and services improve app performance and reusability. TypeScript adds benefits like static typing and class-based programming.
Building front-end apps that Scale - FOSDEM 2014
This document discusses how to build large-scale front-end apps that can scale effectively. It defines large-scale apps as having significant codebases and complexity. Some signs that an app needs scaling solutions are long development setup times, apps not loading properly, difficulty finding code, and long test runs. The document recommends streamlining the developer workflow, building features in isolation, using a loosely coupled architecture with services, and extensive testing to improve maintainability for large teams.
Project Sherpa: How RightScale Went All in on Docker
We just finished a 7 week project at RightScale to migrate 48 services and 650+ cloud instances to Docker. As a result we’ve been able to accelerate our development processes and cut our cloud costs (a lot). Here we share lessons learned about our experience migrating to Docker and introduce our new Container Manager we added to the RightScale platform to help manage containerized environments.
All about that reactive ui
Slides from my last presentation at the Cape Town Meteor meetup, on optimising the UI, specifically for Hybrid apps and for Meteor JS hybrid apps.
The main thrust is really more about design patterns, and carefully controlling data management in your mobile app, with great examples of these patterns out in the real world.
see the mobile patterns video here : https://www.youtube.com/watch?v=e6WWX4TF3UI
Make It Cooler: Using Decentralized Version Control
A commonly used version control system in the ColdFusion community is Subversion -- a centralized system that relies on being connected to a central server. The next generation version control systems are “decentralized”, in that version control tasks do not rely on a central server.
Decentralized version control systems are more efficient and offer a more practical way of software development.
In this session, Indy takes you through the considerations in moving from Subversion to Git, a decentralized version control system. You also get to understand the pros and cons of each and hear of the practical experience of migrating projects to decentralized version control.
Version control is often used in conjunction with a testing framework and continuous integration. To complete the picture, Indy walks you through how to integrate Git with a testing framework, MXUnit, and a continuous integration server, Hudson.
Angular + JHipster - JHipster Conf
Want to know more about the JHipster's webpack configuration and how to improve your application performance using Lazy loading? Let's discover this together!
Continuous Delivery Using Jenkins
Using Jenkins for continuous delivery allows for easy installation, upgrades, configuration, distributed builds, and plugin support. Jenkins supports continuous integration through features like compiling, packaging, testing, and deploying code. It facilitates shorter release cycles through goals like developing on production-like environments, performing early performance testing, and minimizing the time from idea to delivery. Continuous delivery with Jenkins enables frequent releases, rapid feedback, and deploying any code change simply with a single button press.
Microfrontends Monoreops & Trunkbased based
Slides from my talk at the Coimbatore frontend Meetup on how Microfrontends MonoRepos and Trunk based Development go hand in hand with each other
Requirements the Last Bottleneck
Software developers love tools for coding, debugging, testing, and configuration management. The more these tools improve the How of coding, the more we see that we're behind the curve on improving the What, Why, and When. If you've been on a project that seemed vague, adrift, and endless, this talk can help. Make your projects run SMART.
Similar to DevCon-Shikhar Slides (20)
Project management frameworks for software developing
Project management frameworks for software developing
TDD and Related Techniques for Non Developers (2012)
TDD and Related Techniques for Non Developers (2012)
Using BladeRunnerJS to Build Front-End Apps that Scale - Fluent 2014
Using BladeRunnerJS to Build Front-End Apps that Scale - Fluent 2014
Build software like a bag of marbles, not a castle of LEGO®
Build software like a bag of marbles, not a castle of LEGO®
Project Sherpa: How RightScale Went All in on Docker
Project Sherpa: How RightScale Went All in on Docker
Make It Cooler: Using Decentralized Version Control
Make It Cooler: Using Decentralized Version Control
DevCon-Shikhar Slides
- 1. Deploying Node applications at scale Shikhar Kapoor (@kapoorshikhar) UI Engineer @ Flipkart
- 2. A modern front-end engineers job Webpack React Redux Gulp NodeAngular Express GraphQL NPM MongoDB Grunt Jest Mocha
- 3. • Branching Strategies • Continuous Integration • Accelerating build times • Packaging • Deployments • Monitoring • Testing
- 4. Branching strategies • Decide upfront and enforce them. • Master is sacred! • Feature flags are your friends.
- 6. Shorter but fixed release cycles Mainline/Master Release - week 1 Fix Feature Fix Release - week 2 Feature Feature Fix
- 7. Short cycles/ Daily deployments Mainline/Master Fix Feature 1 * Fix Feature1 * Feature 2 * Feature 2 * * Features get pushed to master daily, with feature flags
- 8. Continuous Integration • Tools • Automate mundane tasks like linting, unit test .. • Build on merge • Store artifacts
- 10. Accelerate build times • Build once, promote everywhere • BUT be careful of the gotchas • Freeze dependencies (Yarn, Shrinkwrap) • Offload mundane tasks to orchestrators
- 11. Get playbook Get hosts Start Run tasks EndA typical orchestration workflow
- 12. Packaging • How do you package and send your code to the server? • Git clone • Archive and copy • Debian (FPM, Post Install, Versioning, easy reverts)
- 13. Deployment • Manage your environments, keep them as similar to production as possible. • Blue-Green? Rolling? • Keep your deployment scripts close and your rollback scripts closer!
- 14. Production Cluster Blue green deployment strategy Stage Cluster Load Balancer Production Cluster Load Balancer
- 15. Rolling deployment strategy Load balancer
- 16. Monitoring • What should you monitor? • Trends • Stack traces/ deep dives • How do you monitor? • OpenTSDB based tools like Grafana for trends • Sentry/ NewRelic for deep dives and stack traces
- 18. Testing • What to test? • Functional - Automate critical flows. • Unit tests • Non-functional • Capacity testing and API Fanout • Performance • RUM / Synthetic - SpeedCurve, Dareboost
- 19. Key takeaways