The document discusses challenges and ideas for learning the agile way based on the author's experience with waterfall, Scrum, and Kanban workflows. It addresses challenges with location, communication, awareness, and collaboration in agile projects as well as challenges for agile testing around self-organization, independence, planning, automation, and lack of direct responsibility. The document provides ideas for addressing these challenges such as letting people know you, sharing ideas, having courage, improving the work environment, viewing testers as developers' best friends, earning respect through communication, and relaxing during demos.
The document discusses how testers can add value to their company, projects, and colleagues. It suggests testers can add value to companies by improving testing and the software development lifecycle, maximizing testing return on investment and minimizing waste. For projects, testing can inform decision making by assessing quality during development and identifying schedule slippage. Testers can add value to colleagues by helping fellow testers and contributing to all project roles. The document advocates testers improving themselves by adopting a service mindset, striving for excellence, and becoming better people overall.
Robotium framework & Jenkins CI tools - TdT@Cluj #19Tabăra de Testare
Meetup #19 @Cluj = Automated tests on Android - Robotium framework & Jenkins CI tools
Presentation of how you can:
• automate your tests for mobile platforms (O.S. Android) by using Robotium
• run your tests by using Jenkins
Knowledge level for the presentation: Beginner
The document discusses best practices and challenges for mobile application testing. It covers differences between mobile and traditional web testing such as integration, interruption, and gesture testing. Challenges include the variety of devices, simulating real life scenarios, usability, automation, and performance testing. Guidelines provided include determining a test matrix based on factors like market share and risk, setting up a mobile lab with different devices, and choosing automated or manual testing methods.
Test analysis & design good practices@TDT Iasi 17Oct2013Tabăra de Testare
The document discusses test analysis and design best practices. It covers defining test objectives, analyzing test items to identify conditions, designing test cases using various techniques, and ensuring traceability between requirements and test cases. Good practices for writing effective test cases are also presented, such as using a standardized naming convention and writing steps that verify a single testing idea. The importance of analysis and design in translating requirements into testable items prior to execution is emphasized.
The document discusses the Thucydides testing framework which provides advanced reporting capabilities when used with the WebDriver browser automation API. Some key points:
- Thucydides allows running WebDriver tests across multiple browsers and supports data-driven testing through CSV files.
- It has native integration with Continuous Integration tools like Jenkins and issue tracking systems like JIRA.
- Tests are organized into pages, steps, and test classes while reports are generated in JUnit and aggregate HTML formats.
- The document provides instructions on setting up a sample project to search Google, including creating page objects, steps classes, and a test class with the @Test method.
The document discusses challenges and ideas for learning the agile way based on the author's experience with waterfall, Scrum, and Kanban workflows. It addresses challenges with location, communication, awareness, and collaboration in agile projects as well as challenges for agile testing around self-organization, independence, planning, automation, and lack of direct responsibility. The document provides ideas for addressing these challenges such as letting people know you, sharing ideas, having courage, improving the work environment, viewing testers as developers' best friends, earning respect through communication, and relaxing during demos.
The document discusses how testers can add value to their company, projects, and colleagues. It suggests testers can add value to companies by improving testing and the software development lifecycle, maximizing testing return on investment and minimizing waste. For projects, testing can inform decision making by assessing quality during development and identifying schedule slippage. Testers can add value to colleagues by helping fellow testers and contributing to all project roles. The document advocates testers improving themselves by adopting a service mindset, striving for excellence, and becoming better people overall.
Robotium framework & Jenkins CI tools - TdT@Cluj #19Tabăra de Testare
Meetup #19 @Cluj = Automated tests on Android - Robotium framework & Jenkins CI tools
Presentation of how you can:
• automate your tests for mobile platforms (O.S. Android) by using Robotium
• run your tests by using Jenkins
Knowledge level for the presentation: Beginner
The document discusses best practices and challenges for mobile application testing. It covers differences between mobile and traditional web testing such as integration, interruption, and gesture testing. Challenges include the variety of devices, simulating real life scenarios, usability, automation, and performance testing. Guidelines provided include determining a test matrix based on factors like market share and risk, setting up a mobile lab with different devices, and choosing automated or manual testing methods.
Test analysis & design good practices@TDT Iasi 17Oct2013Tabăra de Testare
The document discusses test analysis and design best practices. It covers defining test objectives, analyzing test items to identify conditions, designing test cases using various techniques, and ensuring traceability between requirements and test cases. Good practices for writing effective test cases are also presented, such as using a standardized naming convention and writing steps that verify a single testing idea. The importance of analysis and design in translating requirements into testable items prior to execution is emphasized.
The document discusses the Thucydides testing framework which provides advanced reporting capabilities when used with the WebDriver browser automation API. Some key points:
- Thucydides allows running WebDriver tests across multiple browsers and supports data-driven testing through CSV files.
- It has native integration with Continuous Integration tools like Jenkins and issue tracking systems like JIRA.
- Tests are organized into pages, steps, and test classes while reports are generated in JUnit and aggregate HTML formats.
- The document provides instructions on setting up a sample project to search Google, including creating page objects, steps classes, and a test class with the @Test method.
The document discusses mobile web UX and usability testing. It provides instructions for testing the usability of mobile web applications by completing tasks on a chosen app website and surveys. It then discusses what user experience and usability testing are, and gives tips for general testers to get involved in usability testing, such as starting with their own applications, learning UX terms, reading articles, attending conferences, and focusing surveys on clear hypotheses rather than numbers of respondents.
This document discusses Behavior Driven Development (BDD) using the Ruby programming language. It provides an overview of test-driven development (TDD), then defines BDD as building upon TDD by formalizing good TDD habits like working outside-in from business goals. Gherkin is introduced as the language used for writing Cucumber features, using examples to clarify requirements. Cucumber is a tool for running automated acceptance tests written in a BDD style using Gherkin. It also discusses using Capybara to access and interact with web pages in tests.
The document provides test scenarios for testing a mobile contacts application. It outlines ways to open and close the application, core functions like adding, calling, messaging contacts, and secondary functions like settings, importing contacts. It also describes testing the application's usability, stress testing by adding/deleting many contacts, low memory testing, load testing by importing large numbers of contacts. Finally, it lists test scenarios for an additional application called Marty, covering installation, uninstallation, functionality, interactions with the operating system, and updating the application.
Security Testing involves testing applications and systems to ensure security and proper functionality. It includes testing input validation, internal processing, output validation, and more. Common types of security testing are security auditing, vulnerability scanning, risk assessment, ethical hacking, and penetration testing. The OWASP Top 10 includes SQL injection, cross-site scripting, and broken authentication and session management as common vulnerabilities.
This document summarizes Meetup #12 that took place on April 3, 2013. There were presentations on tools for testers, test coverage, exploratory testing, testing a wine glass, risk-based testing, and test automation. Workshops were held on test automation with WebDriver and Python. A testing clinic involved debating ISTQB and BBST courses. Feedback was provided which highlighted the practical exercises, shared experiences, and debates. Areas for improvement mentioned were motivation and thinking more long-term when testing.
The document provides guidance on how to evaluate yourself and other testers. It recommends that you first evaluate your own skills and abilities to determine what you should be doing, if you are doing it, and how you can improve. When evaluating other testers, it suggests comparing yourself to those slightly better in targeted areas and adapting skills you observe. The document then lists possible criteria to consider, including soft skills like communication and business orientation, and technical skills like bug reporting and tool usage. It concludes by reminding the reader not to fool themselves and to find realistic models to aim for continuous improvement.
This document discusses strategies for improving testing skills and effectiveness as a testing team. It recommends discovering testing through experienced colleagues, individual study, and courses. It also suggests gaining knowledge in areas like test design, automation tools, and necessary testing skills. Additionally, it provides tips for making work easier, avoiding monotony, and keys to a successful team like identifying skills, improving them, and specializing roles.
Test Automation Techniques for Windows ApplicationsTabăra de Testare
Unit testing, UI automation, and API testing are essential for validating software builds and reducing integration risks. Automation helps deal with geographically divided teams and enables continuous testing through continuous integration tools and triggers. While automation tests help detect problems early, UI changes remain a major threat and require tests to be updated, which highlights the need for abstraction layers, models, and data-driven testing to minimize maintenance costs from such changes.
This document discusses problems that occur when developers and testers do not work as a team and offers solutions to transform an adversarial "they" relationship into a collaborative "we" relationship. It identifies issues like developers not reporting all bugs, forgetting to inform testers of changes, and dismissing tester-filed bugs as trivial. The document recommends rewarding developers for bug reports, helping set up a testing environment, and emphasizing the customer perspective to improve collaboration.
This document discusses how to bring more creativity and critical thinking to software testing. It notes that typical problems with testing like being boring, repetitive, or thoughtless can be addressed by automating routine tasks, differentiating infrastructure from user experience testing, focusing on testing strategy, and innovating new testing approaches like games. The document encourages testing teams to teach others, think critically about their work, and find ways to make testing more engaging and thoughtful.
This document discusses exploring new approaches to testing by doing things differently than traditional methods. It encourages learning from examples but also exploring your own ideas, taking on multiple roles in the testing process, and looking towards the future of testing with new technologies to find innovative test cases that add value for customers. The overall message is that testing methods should evolve by thinking outside the box and wearing different hats rather than just following established practices.
The document discusses coaching new testers in learning exploratory testing. It outlines several methods used to support learning, including providing initial training on testing concepts, responding to questions, and having testers work on demo and real projects with coaching. Some key aspects of learning discussed are thinking not memorizing, direct communication and questions, learning by exploring, and imitation. The downsides of only using test cases for learning are also mentioned.
The document discusses the history and present state of software testing careers. It provides examples of software testing roles at companies like Google, Adobe, and Microsoft. The document also offers tips on how to build a career in software testing, such as learning programming, earning respect from peers, understanding software development, enjoying breaking software, and being innovative.
Hiring any candidate as a tester and viewing the role as entry-level demotivates testers by not recognizing testing as a skilled profession. It also discourages establishing a collaborative working environment between testers and developers, and relies solely on quantitative metrics rather than coaching to evaluate tester performance, which fails to value quality work.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
The document discusses mobile web UX and usability testing. It provides instructions for testing the usability of mobile web applications by completing tasks on a chosen app website and surveys. It then discusses what user experience and usability testing are, and gives tips for general testers to get involved in usability testing, such as starting with their own applications, learning UX terms, reading articles, attending conferences, and focusing surveys on clear hypotheses rather than numbers of respondents.
This document discusses Behavior Driven Development (BDD) using the Ruby programming language. It provides an overview of test-driven development (TDD), then defines BDD as building upon TDD by formalizing good TDD habits like working outside-in from business goals. Gherkin is introduced as the language used for writing Cucumber features, using examples to clarify requirements. Cucumber is a tool for running automated acceptance tests written in a BDD style using Gherkin. It also discusses using Capybara to access and interact with web pages in tests.
The document provides test scenarios for testing a mobile contacts application. It outlines ways to open and close the application, core functions like adding, calling, messaging contacts, and secondary functions like settings, importing contacts. It also describes testing the application's usability, stress testing by adding/deleting many contacts, low memory testing, load testing by importing large numbers of contacts. Finally, it lists test scenarios for an additional application called Marty, covering installation, uninstallation, functionality, interactions with the operating system, and updating the application.
Security Testing involves testing applications and systems to ensure security and proper functionality. It includes testing input validation, internal processing, output validation, and more. Common types of security testing are security auditing, vulnerability scanning, risk assessment, ethical hacking, and penetration testing. The OWASP Top 10 includes SQL injection, cross-site scripting, and broken authentication and session management as common vulnerabilities.
This document summarizes Meetup #12 that took place on April 3, 2013. There were presentations on tools for testers, test coverage, exploratory testing, testing a wine glass, risk-based testing, and test automation. Workshops were held on test automation with WebDriver and Python. A testing clinic involved debating ISTQB and BBST courses. Feedback was provided which highlighted the practical exercises, shared experiences, and debates. Areas for improvement mentioned were motivation and thinking more long-term when testing.
The document provides guidance on how to evaluate yourself and other testers. It recommends that you first evaluate your own skills and abilities to determine what you should be doing, if you are doing it, and how you can improve. When evaluating other testers, it suggests comparing yourself to those slightly better in targeted areas and adapting skills you observe. The document then lists possible criteria to consider, including soft skills like communication and business orientation, and technical skills like bug reporting and tool usage. It concludes by reminding the reader not to fool themselves and to find realistic models to aim for continuous improvement.
This document discusses strategies for improving testing skills and effectiveness as a testing team. It recommends discovering testing through experienced colleagues, individual study, and courses. It also suggests gaining knowledge in areas like test design, automation tools, and necessary testing skills. Additionally, it provides tips for making work easier, avoiding monotony, and keys to a successful team like identifying skills, improving them, and specializing roles.
Test Automation Techniques for Windows ApplicationsTabăra de Testare
Unit testing, UI automation, and API testing are essential for validating software builds and reducing integration risks. Automation helps deal with geographically divided teams and enables continuous testing through continuous integration tools and triggers. While automation tests help detect problems early, UI changes remain a major threat and require tests to be updated, which highlights the need for abstraction layers, models, and data-driven testing to minimize maintenance costs from such changes.
This document discusses problems that occur when developers and testers do not work as a team and offers solutions to transform an adversarial "they" relationship into a collaborative "we" relationship. It identifies issues like developers not reporting all bugs, forgetting to inform testers of changes, and dismissing tester-filed bugs as trivial. The document recommends rewarding developers for bug reports, helping set up a testing environment, and emphasizing the customer perspective to improve collaboration.
This document discusses how to bring more creativity and critical thinking to software testing. It notes that typical problems with testing like being boring, repetitive, or thoughtless can be addressed by automating routine tasks, differentiating infrastructure from user experience testing, focusing on testing strategy, and innovating new testing approaches like games. The document encourages testing teams to teach others, think critically about their work, and find ways to make testing more engaging and thoughtful.
This document discusses exploring new approaches to testing by doing things differently than traditional methods. It encourages learning from examples but also exploring your own ideas, taking on multiple roles in the testing process, and looking towards the future of testing with new technologies to find innovative test cases that add value for customers. The overall message is that testing methods should evolve by thinking outside the box and wearing different hats rather than just following established practices.
The document discusses coaching new testers in learning exploratory testing. It outlines several methods used to support learning, including providing initial training on testing concepts, responding to questions, and having testers work on demo and real projects with coaching. Some key aspects of learning discussed are thinking not memorizing, direct communication and questions, learning by exploring, and imitation. The downsides of only using test cases for learning are also mentioned.
The document discusses the history and present state of software testing careers. It provides examples of software testing roles at companies like Google, Adobe, and Microsoft. The document also offers tips on how to build a career in software testing, such as learning programming, earning respect from peers, understanding software development, enjoying breaking software, and being innovative.
Hiring any candidate as a tester and viewing the role as entry-level demotivates testers by not recognizing testing as a skilled profession. It also discourages establishing a collaborative working environment between testers and developers, and relies solely on quantitative metrics rather than coaching to evaluate tester performance, which fails to value quality work.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...Zilliz
Join us to introduce Milvus Lite, a vector database that can run on notebooks and laptops, share the same API with Milvus, and integrate with every popular GenAI framework. This webinar is perfect for developers seeking easy-to-use, well-integrated vector databases for their GenAI apps.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.