PC repair involves restoring damaged or broken computers to working order. Effective troubleshooting requires being in the right mental state to identify problems quickly. General techniques include understanding the root cause, eliminating potential causes methodically, and using diagnostic tools. Specific components that may need repair include the motherboard, processor, memory, storage drives, ports, and operating system. Experience is important for effective PC repair and troubleshooting.
B. Durrett The Challenges of Continuous Deployment Social Developer SummitMediabistro
The document discusses continuous deployment, where code is deployed to production within 20 minutes of being committed. The author details how IMVU, a social media company, successfully uses this approach, deploying code up to 50 times per day. Some benefits are regressions are easy to find and fix, and releases have zero overhead. Challenges include outages, new testing needs, and increased coordination as the engineering team grows. Overall, the author argues that continuous deployment scales well and is a key part of a good development process.
Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below!
This document discusses Avance Software, a company that creates software-based business-critical computing solutions using virtualization to provide high-availability for small and medium businesses. Their mission is to build upon virtualization technologies used since 2006 to provide simple and affordable fault tolerance and disaster recovery across multiple sites. The document outlines Avance's organizational structure which prioritizes collaboration between engineering, support, customers and partners to improve product requirements and feedback. It also discusses their focus on automated testing to eliminate issues and accelerate QA testing as well as their agile development process of 2-week sprints to deliver frequent releases.
This document discusses different approaches to accelerated life testing (ALT). It introduces the thought process for selecting an ALT approach, discusses trade-off decisions, and enables selecting the right approach for a given situation. The key approaches discussed are: real-time testing with no constraints; time compression testing using increased usage cycles; applying an acceleration model relating stress to life; step stress testing; degradation testing; and Weibull success testing. Guiding principles are to respect constraints, use real usage conditions, minimize assumptions, and focus on failure mechanisms.
Automated testing san francisco oct 2013Solano Labs
Opening presentation from Solano Labs Co-Founder Jay Moorthi for Automated Testing San Francisco. This is an overview of Continuous Integration and Deployment best practices. Please let us know what you think!
Software quality improvement expert Jan Princen and XBOSoft CEO Philip Lew discuss the use of Predictive Analytics to prevent software defects in this XBOSoft webinar on Defect Prevention.
PC repair involves restoring damaged or broken computers to working order. Effective troubleshooting requires being in the right mental state to identify problems quickly. General techniques include understanding the root cause, eliminating potential causes methodically, and using diagnostic tools. Specific components that may need repair include the motherboard, processor, memory, storage drives, ports, and operating system. Experience is important for effective PC repair and troubleshooting.
B. Durrett The Challenges of Continuous Deployment Social Developer SummitMediabistro
The document discusses continuous deployment, where code is deployed to production within 20 minutes of being committed. The author details how IMVU, a social media company, successfully uses this approach, deploying code up to 50 times per day. Some benefits are regressions are easy to find and fix, and releases have zero overhead. Challenges include outages, new testing needs, and increased coordination as the engineering team grows. Overall, the author argues that continuous deployment scales well and is a key part of a good development process.
Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below!
This document discusses Avance Software, a company that creates software-based business-critical computing solutions using virtualization to provide high-availability for small and medium businesses. Their mission is to build upon virtualization technologies used since 2006 to provide simple and affordable fault tolerance and disaster recovery across multiple sites. The document outlines Avance's organizational structure which prioritizes collaboration between engineering, support, customers and partners to improve product requirements and feedback. It also discusses their focus on automated testing to eliminate issues and accelerate QA testing as well as their agile development process of 2-week sprints to deliver frequent releases.
This document discusses different approaches to accelerated life testing (ALT). It introduces the thought process for selecting an ALT approach, discusses trade-off decisions, and enables selecting the right approach for a given situation. The key approaches discussed are: real-time testing with no constraints; time compression testing using increased usage cycles; applying an acceleration model relating stress to life; step stress testing; degradation testing; and Weibull success testing. Guiding principles are to respect constraints, use real usage conditions, minimize assumptions, and focus on failure mechanisms.
Automated testing san francisco oct 2013Solano Labs
Opening presentation from Solano Labs Co-Founder Jay Moorthi for Automated Testing San Francisco. This is an overview of Continuous Integration and Deployment best practices. Please let us know what you think!
Software quality improvement expert Jan Princen and XBOSoft CEO Philip Lew discuss the use of Predictive Analytics to prevent software defects in this XBOSoft webinar on Defect Prevention.
What to Expect When You're Expecting (to Own Production)Michael Diamant
The intended presentation audience is developers unfamiliar with owning a production environment. I aim to share lessons I’ve learned while supporting production environments and to paint a path for how ownership can be built.
By no means is this intended to be a comprehensive guide to production ownership. Instead, it should be treated as an introduction or one of the first few steps into the topic.
This presentation was motivated by a former colleague seeking to help frame his team's mindset toward production ownership. He joined a team that was not accustomed to production deploys, on-call, etc and thought it would be valuable to share insight from our experience together in an environment where developers co-owned production.
The Fallacy of Fast - Ines Sombra at Fastly Altitude 2015Fastly
Fastly Altitude - June 25, 2015. Ines Sombra, a Systems Engineer at Fastly, talks about lessons learned in rapid systems development.
Video of the talk: http://fastly.us/Altitude2015_Fallacy-of-Fast
Ines' bio: Ines Sombra is a Systems Engineer at Fastly, where she spends her time helping the Web go faster. Ines holds an M.S. in Computer Science and an M.S. in Information Management from Washington University in Saint Louis. Being a true Argentine, she has a fondness for steak, fernet, and a pug named Gordo.
This document provides an introduction to context driven testing. It discusses establishing the proper mindset of testing for business value by understanding who uses the software, how it is used, and why it exists. Key aspects of context driven testing are exploring where bugs that matter can be found through experimentation and learning, using system and domain knowledge to facilitate analysis that considers the business needs, project risks, product risks, and available resources defined by the context. The document emphasizes the importance of curiosity and complementary principles of agility and context driven development like responding to change, valuing individuals and interactions, and ensuring the product solves the problem.
The document discusses optimizing Java performance. It covers the history of Java performance tuning, how performance testing and optimization is experimental in nature, different aspects of performance to measure, how the Java HotSpot JIT compiler works to optimize code at runtime, best practices for performance testing, and common performance antipatterns to avoid.
A presentation tries to move the discussion on performance testing from a simple, "will it support x users" to a focus on application optimisation.
A short presentation to my internal peer group on some of the potential shortcomings of current penetration testing practices and what might be done about it.
Architectural Testability Workshop for Test Academy BarcelonaAsh Winter
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model.
This document discusses negative testing techniques. Negative testing aims to show where software fails rather than works. It involves testing invalid inputs and edge cases to evaluate error handling and robustness. The document covers managing negative testing, techniques like boundary value analysis and error path testing, selecting impactful tests, executing them while observing failures, and addressing common criticisms of the approach. The conclusion is that negative testing finds significant failures and provides strategic information about risk, though it requires an opportunistic approach to plan and manage.
This document discusses using a genetic algorithm to develop a machine learning model for predicting fault-prone software classes. It begins by introducing software reliability and fault prediction. It then explains that a genetic algorithm is a search technique that evaluates potential solutions, keeps the best ones, and generates new solutions iteratively. The algorithm uses software metrics like coupling, cohesion, inheritance, and size as inputs to classify classes as faulty or fault-free with 80.14% accuracy, helping to identify areas for improvement.
The document discusses regression testing, including its definition, benefits, when it should be applied, types, techniques, challenges and best practices. Regression testing involves re-running all tests to ensure new code changes have not introduced new bugs or caused existing bugs to reappear. It helps find bugs early, increases chances of detecting bugs, ensures correctness and that fixed issues do not occur again.
Test-driven development (TDD) is a software development process that relies on the repetition of a short development cycle of requirements, design, and coding. It promotes writing tests before writing code (test-first design) and helps improve code quality by reducing defects. The TDD cycle involves writing an automated test, running the test and seeing it fail, writing the minimum amount of code to pass the test, and refactoring the code as needed. TDD brings benefits like clarifying requirements, adding executable documentation, and detecting errors early. Acceptance TDD involves automating acceptance tests to define and validate requirements. It helps establish a definition of done and improves team collaboration.
The document summarizes key points from the book "Lessons learned in software testing" by Cem Kaner, James Bach, and Bret Pettichord. It discusses the role of testers in finding important bugs fast through prioritizing test areas and managing risk. It also covers working with developers as part of a team, documenting tests, and designing automated tests differently than manual ones. The role of testers is to deliver information on product quality by asking questions and exploring through varied testing approaches.
The 7 software testing principles briefly explained. Everyone who works in software development company should know these principles.
It happens frequently that testers or qa people are not taken into account as part of the process in the software development lifecycle and this happens expecially when the principles are not known.
Technical specialist Tom Miseur conducted a webinar discussing the basics of getting started with performance and load testing. Learn how to create a PTP (performance test plan), define requirements and objectives, define test scope and approach, and then finally how to create, execute, and analyze test results.
The document contains a session plan for a software testing principles and techniques course. The session objectives are to define various software testing terms and concepts, differentiate between different types of testing, and learn about the testing process. The session would include slides, demonstrations of testing software, and discussions. Test cases for an example ATM system are also provided to demonstrate initial functional testing.
The document outlines 7 testing principles: 1) Testing finds defects but finding none does not mean none exist, 2) Exhaustive testing is impossible so smarter testing is needed, 3) Early testing saves time and money and makes customers happy, 4) Defects tend to cluster together, 5) Test cases must be updated periodically to avoid outdated "pesticide" tests, 6) Testing methods vary depending on the software context, and 7) Software should be stable before testing to avoid false negatives from instability.
This document summarizes the rules and values of the Extreme Programming (XP) software development methodology. It outlines the core practices of XP which include planning with user stories, managing through daily stand-up meetings, designing for simplicity, coding with pair programming and unit testing, and testing all code through automated unit tests and acceptance tests. The values that XP is based on are also summarized as simplicity, communication, feedback, respect, and courage.
The document discusses web APIs and related concepts. It defines a web API as being based on core web protocols like HTTP, URIs, and media types. It explains that HTTP is an application-level protocol for distributed information systems, and describes some common uses of HTTP like data transportation and CRUD operations. It also defines URIs and APIs, and discusses the data-oriented and control-oriented approaches to web APIs, including examples of each.
What to Expect When You're Expecting (to Own Production)Michael Diamant
The intended presentation audience is developers unfamiliar with owning a production environment. I aim to share lessons I’ve learned while supporting production environments and to paint a path for how ownership can be built.
By no means is this intended to be a comprehensive guide to production ownership. Instead, it should be treated as an introduction or one of the first few steps into the topic.
This presentation was motivated by a former colleague seeking to help frame his team's mindset toward production ownership. He joined a team that was not accustomed to production deploys, on-call, etc and thought it would be valuable to share insight from our experience together in an environment where developers co-owned production.
The Fallacy of Fast - Ines Sombra at Fastly Altitude 2015Fastly
Fastly Altitude - June 25, 2015. Ines Sombra, a Systems Engineer at Fastly, talks about lessons learned in rapid systems development.
Video of the talk: http://fastly.us/Altitude2015_Fallacy-of-Fast
Ines' bio: Ines Sombra is a Systems Engineer at Fastly, where she spends her time helping the Web go faster. Ines holds an M.S. in Computer Science and an M.S. in Information Management from Washington University in Saint Louis. Being a true Argentine, she has a fondness for steak, fernet, and a pug named Gordo.
This document provides an introduction to context driven testing. It discusses establishing the proper mindset of testing for business value by understanding who uses the software, how it is used, and why it exists. Key aspects of context driven testing are exploring where bugs that matter can be found through experimentation and learning, using system and domain knowledge to facilitate analysis that considers the business needs, project risks, product risks, and available resources defined by the context. The document emphasizes the importance of curiosity and complementary principles of agility and context driven development like responding to change, valuing individuals and interactions, and ensuring the product solves the problem.
The document discusses optimizing Java performance. It covers the history of Java performance tuning, how performance testing and optimization is experimental in nature, different aspects of performance to measure, how the Java HotSpot JIT compiler works to optimize code at runtime, best practices for performance testing, and common performance antipatterns to avoid.
A presentation tries to move the discussion on performance testing from a simple, "will it support x users" to a focus on application optimisation.
A short presentation to my internal peer group on some of the potential shortcomings of current penetration testing practices and what might be done about it.
Architectural Testability Workshop for Test Academy BarcelonaAsh Winter
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model.
This document discusses negative testing techniques. Negative testing aims to show where software fails rather than works. It involves testing invalid inputs and edge cases to evaluate error handling and robustness. The document covers managing negative testing, techniques like boundary value analysis and error path testing, selecting impactful tests, executing them while observing failures, and addressing common criticisms of the approach. The conclusion is that negative testing finds significant failures and provides strategic information about risk, though it requires an opportunistic approach to plan and manage.
This document discusses using a genetic algorithm to develop a machine learning model for predicting fault-prone software classes. It begins by introducing software reliability and fault prediction. It then explains that a genetic algorithm is a search technique that evaluates potential solutions, keeps the best ones, and generates new solutions iteratively. The algorithm uses software metrics like coupling, cohesion, inheritance, and size as inputs to classify classes as faulty or fault-free with 80.14% accuracy, helping to identify areas for improvement.
The document discusses regression testing, including its definition, benefits, when it should be applied, types, techniques, challenges and best practices. Regression testing involves re-running all tests to ensure new code changes have not introduced new bugs or caused existing bugs to reappear. It helps find bugs early, increases chances of detecting bugs, ensures correctness and that fixed issues do not occur again.
Test-driven development (TDD) is a software development process that relies on the repetition of a short development cycle of requirements, design, and coding. It promotes writing tests before writing code (test-first design) and helps improve code quality by reducing defects. The TDD cycle involves writing an automated test, running the test and seeing it fail, writing the minimum amount of code to pass the test, and refactoring the code as needed. TDD brings benefits like clarifying requirements, adding executable documentation, and detecting errors early. Acceptance TDD involves automating acceptance tests to define and validate requirements. It helps establish a definition of done and improves team collaboration.
The document summarizes key points from the book "Lessons learned in software testing" by Cem Kaner, James Bach, and Bret Pettichord. It discusses the role of testers in finding important bugs fast through prioritizing test areas and managing risk. It also covers working with developers as part of a team, documenting tests, and designing automated tests differently than manual ones. The role of testers is to deliver information on product quality by asking questions and exploring through varied testing approaches.
The 7 software testing principles briefly explained. Everyone who works in software development company should know these principles.
It happens frequently that testers or qa people are not taken into account as part of the process in the software development lifecycle and this happens expecially when the principles are not known.
Technical specialist Tom Miseur conducted a webinar discussing the basics of getting started with performance and load testing. Learn how to create a PTP (performance test plan), define requirements and objectives, define test scope and approach, and then finally how to create, execute, and analyze test results.
The document contains a session plan for a software testing principles and techniques course. The session objectives are to define various software testing terms and concepts, differentiate between different types of testing, and learn about the testing process. The session would include slides, demonstrations of testing software, and discussions. Test cases for an example ATM system are also provided to demonstrate initial functional testing.
The document outlines 7 testing principles: 1) Testing finds defects but finding none does not mean none exist, 2) Exhaustive testing is impossible so smarter testing is needed, 3) Early testing saves time and money and makes customers happy, 4) Defects tend to cluster together, 5) Test cases must be updated periodically to avoid outdated "pesticide" tests, 6) Testing methods vary depending on the software context, and 7) Software should be stable before testing to avoid false negatives from instability.
This document summarizes the rules and values of the Extreme Programming (XP) software development methodology. It outlines the core practices of XP which include planning with user stories, managing through daily stand-up meetings, designing for simplicity, coding with pair programming and unit testing, and testing all code through automated unit tests and acceptance tests. The values that XP is based on are also summarized as simplicity, communication, feedback, respect, and courage.
The document discusses web APIs and related concepts. It defines a web API as being based on core web protocols like HTTP, URIs, and media types. It explains that HTTP is an application-level protocol for distributed information systems, and describes some common uses of HTTP like data transportation and CRUD operations. It also defines URIs and APIs, and discusses the data-oriented and control-oriented approaches to web APIs, including examples of each.
Artificial intelligence (AI) is everywhere, promising self-driving cars, medical breakthroughs, and new ways of working. But how do you separate hype from reality? How can your company apply AI to solve real business problems?
Here’s what AI learnings your business should keep in mind for 2017.
Rahul Verma and Pradeep Soundararajan as young kids in testing in 2010 got together in Cuppa, JP Nagar, Bangalore and decided they would spend time together to help themselves and other testers. This is one of the outputs they produced. 2010 it is. Some ideas could be outdated or wrong even for 2010. Use it as a trigger to your own thought process and not as someone gave you something useful. Shared in 2019 when Rahul and Pradeep went back in memory over a beer talking about how did we get to this point of having a beer together after so many years.
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
This talk was geared around the concept of showing developers what goes into getting enterprise products out the door. Unit testing, release process, continuous integration, security, social engineering, bug bashes.
5 Steps to Jump Start Your Test AutomationSauce Labs
With the acceleration of software creation and delivery, test activities must align to the new tempo. Developers need immediate feedback to be efficient and correct defects as those are introduced. The path to achieving this vision is to build a reliable and scalable continuous test solution.
All beginnings are hard. Having a well-defined plan outlining the approach for your organization to create test automation is key to ensure long term success. Join Diego Molina, Senior Software Engineer at Sauce Labs as he discusses:
The importance of setting up the team correctly from the start
Choosing the right Testing Framework for your organization
Identifying the right scenarios and workflows to test
Learning to avoid common pitfalls at the beginning of the transformation journey
Resilience and Compliance at Speed and ScaleJason Chan
The document discusses Netflix's approach to resilience and compliance at scale through automation. It describes common traditional controls like change approval boards and centralized deployments that don't work for Netflix given its culture of freedom and responsibility and need for rapid innovation. Netflix uses automated "Simian Army" monkeys like Chaos Monkey that cause random failures to test resilience. It also uses tools giving visibility into who made changes and their testing/approval to achieve compliance objectives in a decentralized way without slowing innovation.
The document outlines best practices and tips for application performance testing. It discusses defining test plans that include load testing, stress testing, and other types of performance testing. Key best practices include testing early and often using an iterative approach, taking a DevOps approach where development and operations work as a team, considering the user experience, understanding different types of performance tests, building a complete performance model, and including performance testing in unit tests. The document also provides tips to avoid such as not allowing enough time and using a QA system that differs from production.
The document discusses various software development processes including traditional/waterfall methods, prototyping, rapid application development, evolutionary/incremental/spiral development, agile methods like extreme programming, formal methods, and fourth generation techniques. It provides details on the characteristics, advantages, and disadvantages of each approach.
Continuous Delivery and Continuous Agile by Andy Singleton - Agile Maine Day...agilemaine
Both people and technology are important. The best approach is usually to focus first on understanding user needs and business goals, then determine how technology can help meet those needs in a way that empowers and supports people. Major changes should not be technology-driven alone, but aim to use technology to make people more effective and their work more meaningful.
The document provides an overview of the Rational Unified Process (RUP) and Extreme Programming (XP). RUP is a configurable software development process that uses iterative development, UML modeling, and documentation of artifacts. It consists of four main phases - inception, elaboration, construction, and transition. XP is an agile methodology based on values of communication, simplicity, feedback, and courage, and practices like planning games, test-driven development, pair programming, and frequent integration.
The document outlines the steps of the Problem Solving Methodology (PSM), which includes analysis, design, development, testing, documentation, and evaluation. It provides details about each step, such as analyzing the problem to determine if it is worth solving, designing the solution requirements, developing the system, testing it, and finally evaluating if the system meets its objectives.
This document discusses several anti-patterns related to manual software deployments including extensive documentation, reliance on manual testing, unpredictable releases, and lack of collaboration between development and operations teams. It advocates for automating deployments to make them repeatable and frequent in order to reduce risk and provide quick feedback. Continuous delivery of software through practices like blue-green deployments and canary releases is recommended to satisfy customers.
Essential practices and thinking tools for Agile AdoptionSteven Mak
Steven Mak presented tools and practices for adopting Agile, including:
- Thinking tools like systems thinking and lean thinking can help with adoption.
- Organizational practices like self-managing cross-functional teams and continuous improvement are important.
- Engineering practices like test-driven development, refactoring, and continuous integration can reduce technical debt.
- Adoption requires changing mindsets and habits through training, coaching, and leading by example.
Best practice adoption (and lack there of)John Pape
This is a short presentation I created some time ago that details some of the developmental, procedural, and infrastructure best practices that I discovered while working with various customers.
Incorporating Performance Testing in Agile Development ProcessMichael Vax
This presentations explains different aspects of software performance testing and give actionable recommendations on how to integrate it into the Agile Software development process
in this presentation i demonstrated all of the testings that can be done to improve the continuous delivery system in the development process of software in the end i have demonstrated what TDD is and what are it's benefits after the slides i demonstrated the TDD methodology by building a small project(a simple stack) with three rules of TDD.
The document discusses the stages an organization goes through in adopting DevOps practices and culture. It outlines four stages - reactive, repeatable, reliable, and aspirational. For each stage, it describes the typical issues, processes, tools, and other aspects around scheduling work, managing requirements, ensuring quality, and how development and operations teams collaborate. The overall goal is for organizations to progress from an initial reactive state to the aspirational ideal of true transparency and collaboration between teams.
Making software development processes to work for youAmbientia
Mikko Paukkila discusses optimizing software development processes to balance bureaucracy and flexibility. He advocates for continuous integration to find errors early and speed up feedback loops. Tools like Git, Jenkins, Gerrit enable CI by automating builds, testing and code reviews. Process optimizations include reducing time from change to product, automating more tests, and ensuring developers have easy environments and fast feedback. The goal is enabling smooth development flows from needs to requirements to changes to high quality products.
This document discusses reliability engineering and how it fits within the system engineering lifecycle. It provides an overview of reliability engineering processes and tools used to optimize risk for projects. Some key points made include:
- Reliability engineering exists to help design out failure modes and reduce operational risk through a partnership with system engineering teams.
- Reliability processes are applied throughout the project lifecycle from requirements development through operations and disposal. Tools include FMEA, FTA, simulation, testing and data analysis.
- The goal is for engineers to think about both success space (how things work) and failure space (how things can fail) to design out failures and ensure mission success.
Effective Testing Practices in an Agile EnvironmentRaj Indugula
This is a practitioner’s view of testing and testing practices within an iterative development environment. We will explore the challenges of testing within such an environment and ways to better integrate the QA professional into what is inherently a developer-centric methodology. If quality is paramount, then we ought to move testing to the front of the line and test early and often. Automation lies at the heart of agility and we will look at how test automation techniques and test-first design philosophy might be applied at multiple-levels to drive quality.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
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).
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.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
“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.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
5. Quality of Life
Release 1.0 is the beginning of your
software’s life, not the end of the
project.
Your quality of life after Release 1.0
depends on choices you make long before
that vital milestone.
6. Quality of life degraded, what now?
Get fired!
Gain experience, learn lessons!
8. • Frequent server restarts
• Professional users
• Favorite browser
• No concurrent load on server
• Emulated integration points
• No financial risk in case of
malfunction
• Server is up for months
• All kind of users
• Different browsers (at least that you
have promised to support)
• Real load
• Real integration with external
services
• Negative financial impact
• No assumptions that something
won’t happen, if there is a tiny
chance it will definitely happen
Environment differences
9. Design Production-Ready System
Choosing an appropriate technology
Performance and capacity analysis
Development team culture
Architectural decisions
Effective stress tests
Deployment checklist
Monitoring and effective incident investigation
10. Choosing an appropriate technology
Investigate
Evaluate
Use cases
Documentation
Community
Stability
Tooling
Storage
Experience of your team, learning curve
Use force
Your early decisions make the biggest impact on the
eventual shape of your system.
The earliest decisions you make can be the hardest
ones to reverse later.
11. Performance and capacity analysis
Define capacity against system specificity
Capacity can be maximum concurrent active sessions,
in case of public web site, until allowable response
time is not exceeded.
Or it can be maximum transactions throughput in case
of financial transactions processing system.
Any other thing or combination
Memory usage analyses
Horizontal scalability
Hardware topology
Maybe use some cloud vendor, that offers elastic
capacity service
Server responsibilities
12. Development team culture
Team members must understand and respect methodology
of project management, whether it’s agile, extreme or
whatever
Note every detail
Respect coding quality standard
Unit tests are mandatory
Integration test are desired for critical modules
Don’t resolve an issue hoping that someone will test it for
you
Worst and most annoying is returning back to issue that you
declared as resolved
Make code reviews of each others code
Refactor as many times as it is needed for your own
satisfaction looking at your own code.
Log effectively
Ask for advice, if you are not sure that you make it right
13. Architectural decisions
Gather use cases and constraints before thinking
solution
There are no straightforward rules or patterns
for success. All of this templates together with
experience just help to make correct decisions
Do not confuse architecture with tools and
frameworks
Design domain model from the performance and
reporting requirements point of view
Rethink and refactor before it’s too late
Avoid radical decisions when the milestone is
nearing
Think pragmatic
14. Effective stress tests
Try to build realistic environment
Compose scenario of real world usage
Simulate exceptional situations
Analyze chains of failure
Analyze increased memory usage impacts
Analyze overall performance impacts
Simulate integration points malfunctioning
15. Deployment checklist
Make sure production parameters are set
correctly
Check memory usage configuration
Check database connection pool size
Check thread pools configuration
Check timeouts configuration
Check logging configuration
Check security configurations
Other server configurations
16. Monitoring and effective incident investigation
Use monitoring tools and permanently analyze logs.
If you noted some suspected behavior, don’t
hesitate to react, before it will burst the overall
system.
After incident happened don’t immediately destroy
facts that would help you to investigate the issue.
If something happened once it will definitely
repeat.