There are no_tests-rmr
•
0 likes•247 views
This document discusses techniques for successfully completing technical projects. It emphasizes doing hard work, setting clear goals, measuring progress, deploying in stages, refactoring for understanding, writing tests, and using bug reports as integration tests. The overall message is that projects require bravery, discipline, expertise, and a willingness to work through failures in order to thrive.
Report
Share
Report
Share
Download to read offline
Recommended
Automated Battle Scars Se Conf 2011
This is my talk for the 2011 Selenium Conference about how to be successful in the test automation world.
8th algebra -may 6
The document outlines tasks for a work day including turning in a review, checking if a test was signed, wishing luck on a final exam, asking about timed tests, and providing work time. An assignment is also listed to turn in a signed Chapter 8 test for potential extra credit.
Seven Bad Habits to Avoid As a QA Engineer
While you might truly care about product quality, all QA engineers tend to fall for these mistakes every now and then. Here are some habits that you should avoid to produce high-quality work.
Exploratory Testing in an Agile Context
The document discusses exploratory testing in an agile context. It describes exploratory testing as simultaneously learning about a system while designing and executing tests, using feedback from the last test to inform the next. It also discusses that agile teams do both checking of requirements through automated tests as well as exploring to discover unintended consequences. Finally, it provides an example charter for exploratory testing of editing user profiles on a system.
Agile Testing
This presentation was given by Me (Anand Ramdeo @testinggeek) and Nathan Bain (@nathanbain) at Skills Matter in London.
Agile Testers: Becoming a key asset for your team
Slides for a presentation titled "Agile Testers: Becoming a Key Asset for your team" given at the Next Generation Testing Executive Briefing on 19 May 2010 in London
5-Ways-to-Revolutionize-Your-Software-Testing
This document provides 5 insights to revolutionize software testing: 1) There are two types of code (experience and infrastructure) that require different testing approaches; 2) Testing should focus on capabilities rather than features; 3) Focus on testing techniques rather than individual test cases; 4) Testing should improve development rather than just find bugs; 5) Testing needs innovation to engage talent and avoid repetitive work. The author advocates shifting testing strategy to higher levels of abstraction and partnering with development to build quality in from the start.
Draper presentation
Draper is a Ruby on Rails gem created by Jeff Casimir that aims to separate view presentation logic from controllers and models through the use of decorators. It encourages moving filtering of data and view helpers to decorators defined at the presentation layer. By using decorators, Draper provides a more object-oriented approach to view helpers and enforces an interface between controllers and view templates through attribute whitelisting or blacklisting. An example Twitter-style Rails app called Dritter demonstrates the use of Draper.
Recommended
Automated Battle Scars Se Conf 2011
This is my talk for the 2011 Selenium Conference about how to be successful in the test automation world.
8th algebra -may 6
The document outlines tasks for a work day including turning in a review, checking if a test was signed, wishing luck on a final exam, asking about timed tests, and providing work time. An assignment is also listed to turn in a signed Chapter 8 test for potential extra credit.
Seven Bad Habits to Avoid As a QA Engineer
While you might truly care about product quality, all QA engineers tend to fall for these mistakes every now and then. Here are some habits that you should avoid to produce high-quality work.
Exploratory Testing in an Agile Context
The document discusses exploratory testing in an agile context. It describes exploratory testing as simultaneously learning about a system while designing and executing tests, using feedback from the last test to inform the next. It also discusses that agile teams do both checking of requirements through automated tests as well as exploring to discover unintended consequences. Finally, it provides an example charter for exploratory testing of editing user profiles on a system.
Agile Testing
This presentation was given by Me (Anand Ramdeo @testinggeek) and Nathan Bain (@nathanbain) at Skills Matter in London.
Agile Testers: Becoming a key asset for your team
Slides for a presentation titled "Agile Testers: Becoming a Key Asset for your team" given at the Next Generation Testing Executive Briefing on 19 May 2010 in London
5-Ways-to-Revolutionize-Your-Software-Testing
This document provides 5 insights to revolutionize software testing: 1) There are two types of code (experience and infrastructure) that require different testing approaches; 2) Testing should focus on capabilities rather than features; 3) Focus on testing techniques rather than individual test cases; 4) Testing should improve development rather than just find bugs; 5) Testing needs innovation to engage talent and avoid repetitive work. The author advocates shifting testing strategy to higher levels of abstraction and partnering with development to build quality in from the start.
Draper presentation
Draper is a Ruby on Rails gem created by Jeff Casimir that aims to separate view presentation logic from controllers and models through the use of decorators. It encourages moving filtering of data and view helpers to decorators defined at the presentation layer. By using decorators, Draper provides a more object-oriented approach to view helpers and enforces an interface between controllers and view templates through attribute whitelisting or blacklisting. An example Twitter-style Rails app called Dritter demonstrates the use of Draper.
Fantastic Tests - The Crimes of Bad Test Design
The document discusses why testing is important and what causes bad tests. Testing provides comfort and confidence by knowing if new code breaks existing functionality. Bad tests have a wide scope so it's unclear what they test, depend on specific orders or system states, are too similar to the product without the same fragility, or are not similar enough to the user experience. The key is for tests to be independent of order or system state and balance similarity to the product with enough differences to reliably fail when bugs are present.
Let's review it: What designers can learn from (code) review
What if designers approached collaboration and critique more like developers? Could it make us better designers, and could it better collaboration between designers and developers? Presented at Yggdrasil 2018 in Sandefjord, Norway
TDD - Ketan Soni
This document discusses Acceptance Test Driven Development (ATDD) and its benefits over a typical development flow. With ATDD, business analysts, developers, and QA work collaboratively to define acceptance criteria and concrete acceptance test scenarios before development begins. Developers then implement the code to pass the defined tests. QA then performs manual testing and consolidates test scenarios. The benefits of ATDD include faster feedback, no automation backlog, more exploratory testing time for QA, fewer functional bugs, and greater team collaboration.
Incident management
Short presentation-on incident management, as per ITIL definition,In today’s article we are going to learn all about the “Incident Tracking and management” Process – How to track and manage incidents in Software Testing with sample templates.
Are you thinking- “STH has published a lot of content on defect/bug tracking, so how is this going to be different”? That is exactly the reason why we have to look at what we mean by incident first.
Automating good coding practices
The document discusses various techniques for automating good coding practices, including unit tests, integration tests, static analysis, and automated monitoring. It emphasizes that unit tests ensure code is functioning as intended, global tests check for errors across codebases, and monitoring verifies code continues working over time. While coverage metrics and formal code reviews have value, the document argues automation is more effective and comments should be replaced with well-written tests.
Improve Testing with a Zone Defense
At one time or another, every tester hears the dreaded question, “Why didn’t you guys catch these bugs?” We all have some standard responses, and they are most likely true). But what can we learn about our testing when we look beyond the easy answers? Pamela Gillaspie proposes that the key to improving your testing is determining the areas where bugs are slipping past your defenses. For her team, the practice is a lot like basketball. If you group the bugs into zones, you can devise a strategy to cover those zones more effectively. Some zones need a different testing approach than you’ve used; others might reveal a need for closer communication. Join Pamela as she shares her experience as defensive coordinator, addressing the developers’ playbook (What kinds of recurring problems do we see?), trick plays (The user is doing what?), and penalties (That wasn’t in the requirements!).
Agile code quality metrics
The document discusses various code quality metrics that can be used to understand software quality, including defects density, unit test density, code and test coverage, cyclomatic complexity, fan-in and fan-out, and WTFs per minute. While metrics can help identify issues, they cannot determine the precise cause. Metrics should be used carefully to avoid incentivizing behaviors like hiding bugs. Maintaining pride in craftsmanship is important for quality.
How to successfully grow a code review culture
As a team grows, code ownership is distributed. Code review becomes increasingly important to support the maintainability of complex codebases. An effective code base is on that can be worked on collaboratively by a team.
In this talk we'll discuss how to introduce a successful code review culture to your development team that will foster the idea of shared ownership. This in turn will result in a happy and healthy code base.
https://webexpo.net/prague2016/talk/how-to-successfully-grow-a-code-review-culture/
Alex Feil Intern Evaluation - QA-QC (1)
The intern evaluation summarizes Alex Feil's performance over a 2-3 week internship assisting with quality control inspections on the Columbus AFB Medical Dental Clinic project. The evaluator rates Alex highly in all areas and comments that Alex displayed eagerness to learn, thoroughness, initiative and professionalism. The evaluator would recommend hiring Alex for a full-time quality control role due to his strong work ethic, attention to detail, and passion for the industry. Areas for growth include gaining additional construction experience.
VodQA3_ATDD_KetanSoni
This was a full length talk presented by Ketan Soni in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
VodQA3_ATDD_KetanSoni
This was a full length talk presented by Ketan Soni in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
Unit testing
Unit testing involves testing individual units or components of code, such as classes or methods, in isolation from the rest of the code base. A unit test asserts certain conditions or tests for specific behaviors and returns a pass/fail result. The purpose of unit testing is to validate that each piece of code works as intended, allowing code to be refactored with confidence and problems to be identified early. Best practices for unit testing include writing tests for new code, designing code for testability, and following an arrange-act-assert structure. Tests should be fast, isolated, and clearly named. Unit testing promotes code quality, documentation, and easier refactoring.
Defining Done
How do we know... I mean, really _know_ when our project is finally _done_...? Particularly in this world of Agile Development practices, where the client can change his mind at any moment and add or remove things from the project, willy-nilly... What a mess! Welcome to (one of) the answers: Acceptance Criteria!
Bridging the communication Gap & Continuous Delivery
This is a case study of a top retailer in UK which was following Agile but not all the Agile practices. We will discuss how collaboration between business and engineering team improved using BDD and how it was used to generate automated acceptance tests. We will also discuss how continuous integration was implemented which laid foundation for continuous delivery.
Ui qa tools
This document discusses tools for automating user interface (UI) quality assurance testing. It begins with introductions and defines UI quality as including code quality, look and feel consistency with designs, functional testing across browsers/devices, and performance testing. It then recommends specific open source tools for automating each type of testing, including Selenium for functional testing, Galen for look and feel testing, Linters for code quality checking, and performance testing services. The presentation aims to help share knowledge about quality assurance and convince attendees that automated testing is important and helps catch errors early. It concludes by thanking attendees and announcing an upcoming conference.
Software Quality Assurance: A mind game between you and devil
Software Quality Assurance (SQA) is essential in assuring the quality of software development. Topics such as SQA core concept, QA & developer relationship, common mistakes made by developers, cost of bugs at different stages of software development, best practices to avoid silly bugs in development stage and thus reducing the probability of getting a bug by the clients - are discussed in the slides.
Software Quality Assurance: A mind game between you and devil
The document discusses software quality assurance and the mindset of developers. It notes that initially developers think testing is not needed and that QA finds many issues in their work. However, over time as developers realize the costs of bugs, their mindset transforms to proactively consider issues like validation, accessibility and security. The document provides examples of common mistakes made by developers and emphasizes the importance of things like proper processes, prioritized bug fixing, and code reviews between development and testing.
Testable requirements
The document discusses using examples and acceptance criteria to define requirements for software development. It recommends collaborating with business analysts, developers and testers to define examples that specify desired system behaviors in a clear and executable way. Automating acceptance tests based on these examples helps communicate requirements, verify functionality and allow for faster development cycles and deployments. Challenges include maintaining the tests and ensuring they don't become brittle. Strategies like minimizing end-to-end tests and focusing on key user journeys can help address these challenges.
Lessons Learned When Automating
I attended the Tabara de Testare testing group on 3rd February 2015 to present "Lessons Learned When Automating. A live stream from UK to Romania.
http://compendiumdev.co.uk/page/tabaradetestare201602
I've been asked some very challenging questions about lessons learned, and how decisions are made during the process of automating and performing technical testing. In this webinar I'm going to answer them based on my experience. We'll discus how we know 'what to automate' which means we have to split our analysis into 'detection' and 'testing'. We'll cover lessons learned from solving problems, and making mistakes, and steps we can take during the problem solving process e.g. for intermittent failures, and possible tool bugs. We'll discuss abstraction levels and the different levels of the technology stack to automate: how to do it, and how we make the decisions. We'll discuss coding primarily the differences, and the overlap, between the needs for coding for testing and coding for production deployment. We'll also cover some WebDriver specific answers to some of these questions. I'm also going to describe books and techniques that have helped me over the years when trying to deal with these questions on production projects.
Browser Automated Testing Frameworks - Nightwatch.js
Browser automation testing frameworks like Nightwatch.js allow developers to automatically test their web applications. Nightwatch.js provides an easy way to write tests using JavaScript. Tests can launch browsers, fill forms, click links, and verify outputs. Nightwatch.js tests can help developers catch errors that might break functionality and ensure compatibility across browsers. The documentation is good and it is actively maintained with over 10,000 downloads per month. Developers can integrate Nightwatch.js tests into their own projects to avoid future issues.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Azure API Management to expose backend services securely
How to use Azure API Management to expose backend service securely
More Related Content
Similar to There are no_tests-rmr
Fantastic Tests - The Crimes of Bad Test Design
The document discusses why testing is important and what causes bad tests. Testing provides comfort and confidence by knowing if new code breaks existing functionality. Bad tests have a wide scope so it's unclear what they test, depend on specific orders or system states, are too similar to the product without the same fragility, or are not similar enough to the user experience. The key is for tests to be independent of order or system state and balance similarity to the product with enough differences to reliably fail when bugs are present.
Let's review it: What designers can learn from (code) review
What if designers approached collaboration and critique more like developers? Could it make us better designers, and could it better collaboration between designers and developers? Presented at Yggdrasil 2018 in Sandefjord, Norway
TDD - Ketan Soni
This document discusses Acceptance Test Driven Development (ATDD) and its benefits over a typical development flow. With ATDD, business analysts, developers, and QA work collaboratively to define acceptance criteria and concrete acceptance test scenarios before development begins. Developers then implement the code to pass the defined tests. QA then performs manual testing and consolidates test scenarios. The benefits of ATDD include faster feedback, no automation backlog, more exploratory testing time for QA, fewer functional bugs, and greater team collaboration.
Incident management
Short presentation-on incident management, as per ITIL definition,In today’s article we are going to learn all about the “Incident Tracking and management” Process – How to track and manage incidents in Software Testing with sample templates.
Are you thinking- “STH has published a lot of content on defect/bug tracking, so how is this going to be different”? That is exactly the reason why we have to look at what we mean by incident first.
Automating good coding practices
The document discusses various techniques for automating good coding practices, including unit tests, integration tests, static analysis, and automated monitoring. It emphasizes that unit tests ensure code is functioning as intended, global tests check for errors across codebases, and monitoring verifies code continues working over time. While coverage metrics and formal code reviews have value, the document argues automation is more effective and comments should be replaced with well-written tests.
Improve Testing with a Zone Defense
At one time or another, every tester hears the dreaded question, “Why didn’t you guys catch these bugs?” We all have some standard responses, and they are most likely true). But what can we learn about our testing when we look beyond the easy answers? Pamela Gillaspie proposes that the key to improving your testing is determining the areas where bugs are slipping past your defenses. For her team, the practice is a lot like basketball. If you group the bugs into zones, you can devise a strategy to cover those zones more effectively. Some zones need a different testing approach than you’ve used; others might reveal a need for closer communication. Join Pamela as she shares her experience as defensive coordinator, addressing the developers’ playbook (What kinds of recurring problems do we see?), trick plays (The user is doing what?), and penalties (That wasn’t in the requirements!).
Agile code quality metrics
The document discusses various code quality metrics that can be used to understand software quality, including defects density, unit test density, code and test coverage, cyclomatic complexity, fan-in and fan-out, and WTFs per minute. While metrics can help identify issues, they cannot determine the precise cause. Metrics should be used carefully to avoid incentivizing behaviors like hiding bugs. Maintaining pride in craftsmanship is important for quality.
How to successfully grow a code review culture
As a team grows, code ownership is distributed. Code review becomes increasingly important to support the maintainability of complex codebases. An effective code base is on that can be worked on collaboratively by a team.
In this talk we'll discuss how to introduce a successful code review culture to your development team that will foster the idea of shared ownership. This in turn will result in a happy and healthy code base.
https://webexpo.net/prague2016/talk/how-to-successfully-grow-a-code-review-culture/
Alex Feil Intern Evaluation - QA-QC (1)
The intern evaluation summarizes Alex Feil's performance over a 2-3 week internship assisting with quality control inspections on the Columbus AFB Medical Dental Clinic project. The evaluator rates Alex highly in all areas and comments that Alex displayed eagerness to learn, thoroughness, initiative and professionalism. The evaluator would recommend hiring Alex for a full-time quality control role due to his strong work ethic, attention to detail, and passion for the industry. Areas for growth include gaining additional construction experience.
VodQA3_ATDD_KetanSoni
This was a full length talk presented by Ketan Soni in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
VodQA3_ATDD_KetanSoni
This was a full length talk presented by Ketan Soni in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
Unit testing
Unit testing involves testing individual units or components of code, such as classes or methods, in isolation from the rest of the code base. A unit test asserts certain conditions or tests for specific behaviors and returns a pass/fail result. The purpose of unit testing is to validate that each piece of code works as intended, allowing code to be refactored with confidence and problems to be identified early. Best practices for unit testing include writing tests for new code, designing code for testability, and following an arrange-act-assert structure. Tests should be fast, isolated, and clearly named. Unit testing promotes code quality, documentation, and easier refactoring.
Defining Done
How do we know... I mean, really _know_ when our project is finally _done_...? Particularly in this world of Agile Development practices, where the client can change his mind at any moment and add or remove things from the project, willy-nilly... What a mess! Welcome to (one of) the answers: Acceptance Criteria!
Bridging the communication Gap & Continuous Delivery
This is a case study of a top retailer in UK which was following Agile but not all the Agile practices. We will discuss how collaboration between business and engineering team improved using BDD and how it was used to generate automated acceptance tests. We will also discuss how continuous integration was implemented which laid foundation for continuous delivery.
Ui qa tools
This document discusses tools for automating user interface (UI) quality assurance testing. It begins with introductions and defines UI quality as including code quality, look and feel consistency with designs, functional testing across browsers/devices, and performance testing. It then recommends specific open source tools for automating each type of testing, including Selenium for functional testing, Galen for look and feel testing, Linters for code quality checking, and performance testing services. The presentation aims to help share knowledge about quality assurance and convince attendees that automated testing is important and helps catch errors early. It concludes by thanking attendees and announcing an upcoming conference.
Software Quality Assurance: A mind game between you and devil
Software Quality Assurance (SQA) is essential in assuring the quality of software development. Topics such as SQA core concept, QA & developer relationship, common mistakes made by developers, cost of bugs at different stages of software development, best practices to avoid silly bugs in development stage and thus reducing the probability of getting a bug by the clients - are discussed in the slides.
Software Quality Assurance: A mind game between you and devil
The document discusses software quality assurance and the mindset of developers. It notes that initially developers think testing is not needed and that QA finds many issues in their work. However, over time as developers realize the costs of bugs, their mindset transforms to proactively consider issues like validation, accessibility and security. The document provides examples of common mistakes made by developers and emphasizes the importance of things like proper processes, prioritized bug fixing, and code reviews between development and testing.
Testable requirements
The document discusses using examples and acceptance criteria to define requirements for software development. It recommends collaborating with business analysts, developers and testers to define examples that specify desired system behaviors in a clear and executable way. Automating acceptance tests based on these examples helps communicate requirements, verify functionality and allow for faster development cycles and deployments. Challenges include maintaining the tests and ensuring they don't become brittle. Strategies like minimizing end-to-end tests and focusing on key user journeys can help address these challenges.
Lessons Learned When Automating
I attended the Tabara de Testare testing group on 3rd February 2015 to present "Lessons Learned When Automating. A live stream from UK to Romania.
http://compendiumdev.co.uk/page/tabaradetestare201602
I've been asked some very challenging questions about lessons learned, and how decisions are made during the process of automating and performing technical testing. In this webinar I'm going to answer them based on my experience. We'll discus how we know 'what to automate' which means we have to split our analysis into 'detection' and 'testing'. We'll cover lessons learned from solving problems, and making mistakes, and steps we can take during the problem solving process e.g. for intermittent failures, and possible tool bugs. We'll discuss abstraction levels and the different levels of the technology stack to automate: how to do it, and how we make the decisions. We'll discuss coding primarily the differences, and the overlap, between the needs for coding for testing and coding for production deployment. We'll also cover some WebDriver specific answers to some of these questions. I'm also going to describe books and techniques that have helped me over the years when trying to deal with these questions on production projects.
Browser Automated Testing Frameworks - Nightwatch.js
Browser automation testing frameworks like Nightwatch.js allow developers to automatically test their web applications. Nightwatch.js provides an easy way to write tests using JavaScript. Tests can launch browsers, fill forms, click links, and verify outputs. Nightwatch.js tests can help developers catch errors that might break functionality and ensure compatibility across browsers. The documentation is good and it is actively maintained with over 10,000 downloads per month. Developers can integrate Nightwatch.js tests into their own projects to avoid future issues.
Similar to There are no_tests-rmr (20)
Let's review it: What designers can learn from (code) review
Let's review it: What designers can learn from (code) review
Bridging the communication Gap & Continuous Delivery
Bridging the communication Gap & Continuous Delivery
Software Quality Assurance: A mind game between you and devil
Software Quality Assurance: A mind game between you and devil
Software Quality Assurance: A mind game between you and devil
Software Quality Assurance: A mind game between you and devil
Browser Automated Testing Frameworks - Nightwatch.js
Browser Automated Testing Frameworks - Nightwatch.js
Recently uploaded
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Azure API Management to expose backend services securely
How to use Azure API Management to expose backend service securely
Digital Marketing Trends in 2024 | Guide for Staying Ahead
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Artificial Intelligence for XMLDevelopment
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.
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
dbms calicut university B. sc Cs 4th sem.pdf
Its a seminar ppt on database management system using sql
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
This case study explores designing a scalable e-commerce platform, covering key requirements, system components, and best practices.
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Recently uploaded (20)
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Azure API Management to expose backend services securely
Azure API Management to expose backend services securely
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
There are no_tests-rmr
- 1. There Are No Tests Jeff Casimir @j3
- 4. “ I’ve rarely seen technical projects go wrong for technical reasons.” Joe O’Brien EdgeCase
- 6. be brave
- 9. Expertise RESCUE passion determination
- 11. define Goals
- 13. Measure PROGRESS
- 14. Coverage faults velocity response Complexity Value
- 16. Break the Cycle
- 18. Process Tools & Kit
- 20. Runtime Monitor Value coverage Complexity
- 22. Doing the Work
- 24. Just No miracles one step
- 27. Find Test Extract Validate Use
- 33. Bug Reports
- 34. As _____________________ < user type > When _____________________ < a series of actions > then _____________________ < expect to see/do something > but _____________________ < instead, the bug! >
- 35. As _____________________ An Unautheticated User When _____________________ I click the login link then _____________________ I expect to see username & pw but _____________________ There’s only a username box
- 38. the Rescue
- 39. be brave Set goals break the cycle Do the work fight fires Jeff Casimir save the day @j3