Sticky notes can help optimize reading and handling complexity by allowing you to break down complex information into simple pieces represented by individual notes that you can physically arrange and rearrange to better understand relationships and flow. The notes serve as visual representations that aid comprehension and creative thinking.
Le Mob Programming consiste à regrouper une équipe entière dans une pièce équipée d'un seul poste de travail pour tout le monde.
Cette pratique vous promet entre autres une productivité accrue alors qu'une seule personne à la fois ne peut toucher le clavier !
Promesses tenues ?
This document discusses collaborative exploratory and unit testing. It introduces mob programming where testers work together in real-time. Exploratory testing focuses on exploring a product to uncover unexpected issues while unit testing verifies specific functionality. The document provides an overview of exploratory testing skills and frameworks as well as challenges of testing like non-deterministic behaviors. It emphasizes the power of collaboration between testers with different skills and perspectives.
The document discusses different types of unit testing including approval testing, combinatorial testing, theory testing, executable query testing, testing routes, custom patterns, multithreaded testing, and testing event wiring. Theory testing involves generating test cases, testing a theory against each case, and recording any failures. Executable query testing verifies that queries pass, increases complexity, provides feedback on failures, and compares original and current results.
This document discusses Agile principles and practices for managing changing priorities and improving visibility, productivity, quality, and reducing risk. It emphasizes that most value comes from developing the right mindset and culture, not just practices. Culture provides the greatest leverage for change. Specific techniques mentioned include value stream mapping, innovation games, and strategic play to reveal patterns and encourage partnership, seeing people as valuable, courage, vulnerability, and continuous learning.
Top 10 Agile Gotchas, Problems and Challenges + What you can do about themMichael Sahota
The document discusses common problems teams face when implementing Agile practices, such as long sprint planning meetings, boring daily standups, and unfinished user stories at the end of each sprint. It provides suggestions for how to address these issues, such as splitting large stories into smaller ones, focusing daily standups on planning for the day, and using retrospectives to understand why stories aren't finished and make improvements. The document emphasizes the importance of team culture and fit for successful Agile adoption.
"People over Process" slides that are about coming back to the heart of Agile: People!
Intro - People over Process.
Agile = Culture. Whole Agile.
Focus on People: Vulnerability, Authentic Connection, Safety & Trust (VAST)
People-centric organizations (Laloux Culture Model)
People-centric Change
This document provides information about a workshop on slicing and splitting stories to deliver value each sprint. The main audience is product owners and business analysts who want to help the development team understand requirements. The goals of the workshop are to teach participants how to write excellent user stories and acceptance criteria, apply definitions of ready and done, understand vertical slicing, and know how to split stories. The workshop covers topics like product statements, personas, core activities, storytelling, minimal viable products, product backlog items, user stories, vertical slicing, and splitting stories.
Sticky notes can help optimize reading and handling complexity by allowing you to break down complex information into simple pieces represented by individual notes that you can physically arrange and rearrange to better understand relationships and flow. The notes serve as visual representations that aid comprehension and creative thinking.
Le Mob Programming consiste à regrouper une équipe entière dans une pièce équipée d'un seul poste de travail pour tout le monde.
Cette pratique vous promet entre autres une productivité accrue alors qu'une seule personne à la fois ne peut toucher le clavier !
Promesses tenues ?
This document discusses collaborative exploratory and unit testing. It introduces mob programming where testers work together in real-time. Exploratory testing focuses on exploring a product to uncover unexpected issues while unit testing verifies specific functionality. The document provides an overview of exploratory testing skills and frameworks as well as challenges of testing like non-deterministic behaviors. It emphasizes the power of collaboration between testers with different skills and perspectives.
The document discusses different types of unit testing including approval testing, combinatorial testing, theory testing, executable query testing, testing routes, custom patterns, multithreaded testing, and testing event wiring. Theory testing involves generating test cases, testing a theory against each case, and recording any failures. Executable query testing verifies that queries pass, increases complexity, provides feedback on failures, and compares original and current results.
This document discusses Agile principles and practices for managing changing priorities and improving visibility, productivity, quality, and reducing risk. It emphasizes that most value comes from developing the right mindset and culture, not just practices. Culture provides the greatest leverage for change. Specific techniques mentioned include value stream mapping, innovation games, and strategic play to reveal patterns and encourage partnership, seeing people as valuable, courage, vulnerability, and continuous learning.
Top 10 Agile Gotchas, Problems and Challenges + What you can do about themMichael Sahota
The document discusses common problems teams face when implementing Agile practices, such as long sprint planning meetings, boring daily standups, and unfinished user stories at the end of each sprint. It provides suggestions for how to address these issues, such as splitting large stories into smaller ones, focusing daily standups on planning for the day, and using retrospectives to understand why stories aren't finished and make improvements. The document emphasizes the importance of team culture and fit for successful Agile adoption.
"People over Process" slides that are about coming back to the heart of Agile: People!
Intro - People over Process.
Agile = Culture. Whole Agile.
Focus on People: Vulnerability, Authentic Connection, Safety & Trust (VAST)
People-centric organizations (Laloux Culture Model)
People-centric Change
This document provides information about a workshop on slicing and splitting stories to deliver value each sprint. The main audience is product owners and business analysts who want to help the development team understand requirements. The goals of the workshop are to teach participants how to write excellent user stories and acceptance criteria, apply definitions of ready and done, understand vertical slicing, and know how to split stories. The workshop covers topics like product statements, personas, core activities, storytelling, minimal viable products, product backlog items, user stories, vertical slicing, and splitting stories.
The world is experiencing unprecedented change – and the rate of change is accelerating. For organisations, there is only one chance of survival. Making the ability to adapt to change a competitive advantage. At this session, we talk through some of the major case studies and thinking in recent years and what that means for businesses of the future.
From IIT Academy, Hong Kong - meetup.com/IITAcademyHK
The document discusses patterns for more powerful asserts when doing approval testing. It outlines 7 approaches to asserting values in approval tests, moving from simple number and string assertions to more complex objects, files, automatically generated names, custom verification methods, and using diff tools to compare outputs on failure. The goal is to make approval testing more expressive and tests less cluttered while still using normal test scenarios.
This document discusses strategies for games and strategies. It touches on several topics:
- The importance of games for immersion, fun, and practice for life
- Different strategies like just-in-time rules versus big upfront rules
- The idea that it is in playing the game that we discover what game we must play
- Common strategies like stating the obvious, using your advantages, and changing the game
- The concept of a dominant strategy and examples like the Prisoner's Dilemma
The document outlines the process for Lean Coffee, which involves setting up topics using a ToDo, In Progress, Done framework. Participants then collect and introduce topics in one sentence before dot voting to prioritize what to discuss. Discussions are time boxed and voted on whether to continue discussing the topic or move to the next. This process repeats, creating headings, gathering ideas, introducing topics, prioritizing by vote, discussing, and determining when finished.
The document provides instructions for an activity. It states that a seashore is a better location than a street. The activity requires some skill but is easy to learn, and even children can enjoy it. While complications are minimal when successful, factors like too many participants, rain, or equipment breaking loose can cause problems. Proper space and using a rock as an anchor are advised.
This document discusses ways to increase testability through code seams. It recommends separating code into functional and non-functional pieces, and extracting the functional pieces. This allows the functional code to be tested in isolation without external dependencies. Specific techniques mentioned include peeling away non-functional layers and slicing functional logic from surrounding code. Examples show how to make code more deterministic and remove reliance on global state, dates, and other uncontrollable variables to improve testability.
The document provides instructions for an activity that requires some skill but is easy to learn. It mentions that one may need to try several times to be successful, but complications are minimal once successful. The activity works best with lots of room and can be peaceful without complications, though rain can interfere and having too many people doing the same thing nearby can also cause problems. A rock is recommended as an anchor, but there is no second chance if things break loose from it.
The document discusses how mob programming can be applied to testing to amplify its impact. Mob testing involves having testers, programmers, and test automators work together simultaneously on testing. It provides several benefits like automated testing, exploratory testing, feedback, understanding, and serendipity. The document provides examples of applying mob testing to exploratory testing, automated testing, and production code. It emphasizes benefits like shared learning, insights, handling problems, and producing the best quality work through collaboration.
Exploring User Stories Through Mind mappingKenji Hiranabe
This document discusses how mind mapping can benefit software development and exploring user stories. It provides an overview of mind mapping and how it can be used to capture a big picture view of user needs and wishes in order to identify user stories. The document demonstrates mind mapping for a library system user interview, showing how user stories can be identified from the mind map. It concludes that mind mapping is effective for gathering information, exploring topics freely in user interviews, and providing a high-level view of user needs to identify user stories.
This document discusses getting existing code under tests and the benefits of unit testing. It provides examples of code and questions to test understanding of unit testing and functional vs non-functional testing. Functional tests are described as easier since they isolate code and ensure consistent outputs for given inputs, while non-functional tests involving things like concurrency are more difficult to test.
This document contains code samples in multiple programming languages that implement the "99 Bottles of Beer" song. Code examples are provided in Haskell, Ruby, Java, SmallBasic, and other languages. Each implementation shows a different approach to modeling the song and counting down bottles of beer in a concise yet readable way.
This document summarizes a presentation on strong-style pairing by Llewellyn Falco and Maaret Pyhäjärvi. It introduces the concepts of strong-style pairing versus traditional pairing. Examples are provided of exercises done in strong-style pairing, including navigating, language demos, and coding FizzBuzz. Benefits of strong-style pairing include rapid learning, increased productivity over time, and addressing traditional problems with pairing like disengagement or slowing people down. Homework is assigned to initiate pairing with a new person.
This document discusses user story mapping and provides an example of mapping out a morning routine. It explains that user story mapping helps create a shared understanding by focusing conversations on user experiences. The mapping process involves writing individual tasks or stories, organizing them into a narrative flow, exploring alternatives, distilling the map into a backbone, and slicing tasks to achieve specific outcomes. It then demonstrates this process by mapping out tasks for different goals of getting ready in the morning, either in a rush or with more leisurely time.
This document introduces several innovation games that can be used by agile project managers and organizations. It describes games like the hot air balloon, prune the product tree, and what a volunteer wants that involve participants providing feedback through visual and interactive exercises. The benefits of these games include organizing ideas, understanding customer expectations, identifying priorities, and making strategic decisions. Guidelines are provided for facilitators to run the games effectively and get valuable input from participants.
This document discusses techniques for software project estimation. It recommends providing estimates as ranges rather than specific numbers, and always clarifying what an estimate will be used for. It emphasizes aggregating independent estimates, using past project data to calibrate estimates, and not negotiating estimates or commitments. Key techniques include decomposing work into independently estimable units, using the "law of large numbers" for accuracy, and re-estimating regularly based on actual project velocity. Overall, the document provides guidance for creating estimates that are useful without being overly precise commitments.
Arlen Bankston
Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.
The document provides instructions for connecting with others on LinkedIn in 5 steps: open LinkedIn, select "My Network", select the "Add" button, choose "Find Nearby", and then turn on location services and connect with contacts or message existing connections.
The document appears to be a slide presentation about test driven development (TDD). It includes slides about daily schedules, types of knowledge related to TDD skills, combining different TDD skills, writing test scenarios, the differences between BDD and an "evil programmer" approach, testing functional code, faking code to pass tests first before implementing, resources for learning more about TDD including a blog and video, and thanks and contact information. The presentation provides an overview of key concepts and best practices for TDD.
The world is experiencing unprecedented change – and the rate of change is accelerating. For organisations, there is only one chance of survival. Making the ability to adapt to change a competitive advantage. At this session, we talk through some of the major case studies and thinking in recent years and what that means for businesses of the future.
From IIT Academy, Hong Kong - meetup.com/IITAcademyHK
The document discusses patterns for more powerful asserts when doing approval testing. It outlines 7 approaches to asserting values in approval tests, moving from simple number and string assertions to more complex objects, files, automatically generated names, custom verification methods, and using diff tools to compare outputs on failure. The goal is to make approval testing more expressive and tests less cluttered while still using normal test scenarios.
This document discusses strategies for games and strategies. It touches on several topics:
- The importance of games for immersion, fun, and practice for life
- Different strategies like just-in-time rules versus big upfront rules
- The idea that it is in playing the game that we discover what game we must play
- Common strategies like stating the obvious, using your advantages, and changing the game
- The concept of a dominant strategy and examples like the Prisoner's Dilemma
The document outlines the process for Lean Coffee, which involves setting up topics using a ToDo, In Progress, Done framework. Participants then collect and introduce topics in one sentence before dot voting to prioritize what to discuss. Discussions are time boxed and voted on whether to continue discussing the topic or move to the next. This process repeats, creating headings, gathering ideas, introducing topics, prioritizing by vote, discussing, and determining when finished.
The document provides instructions for an activity. It states that a seashore is a better location than a street. The activity requires some skill but is easy to learn, and even children can enjoy it. While complications are minimal when successful, factors like too many participants, rain, or equipment breaking loose can cause problems. Proper space and using a rock as an anchor are advised.
This document discusses ways to increase testability through code seams. It recommends separating code into functional and non-functional pieces, and extracting the functional pieces. This allows the functional code to be tested in isolation without external dependencies. Specific techniques mentioned include peeling away non-functional layers and slicing functional logic from surrounding code. Examples show how to make code more deterministic and remove reliance on global state, dates, and other uncontrollable variables to improve testability.
The document provides instructions for an activity that requires some skill but is easy to learn. It mentions that one may need to try several times to be successful, but complications are minimal once successful. The activity works best with lots of room and can be peaceful without complications, though rain can interfere and having too many people doing the same thing nearby can also cause problems. A rock is recommended as an anchor, but there is no second chance if things break loose from it.
The document discusses how mob programming can be applied to testing to amplify its impact. Mob testing involves having testers, programmers, and test automators work together simultaneously on testing. It provides several benefits like automated testing, exploratory testing, feedback, understanding, and serendipity. The document provides examples of applying mob testing to exploratory testing, automated testing, and production code. It emphasizes benefits like shared learning, insights, handling problems, and producing the best quality work through collaboration.
Exploring User Stories Through Mind mappingKenji Hiranabe
This document discusses how mind mapping can benefit software development and exploring user stories. It provides an overview of mind mapping and how it can be used to capture a big picture view of user needs and wishes in order to identify user stories. The document demonstrates mind mapping for a library system user interview, showing how user stories can be identified from the mind map. It concludes that mind mapping is effective for gathering information, exploring topics freely in user interviews, and providing a high-level view of user needs to identify user stories.
This document discusses getting existing code under tests and the benefits of unit testing. It provides examples of code and questions to test understanding of unit testing and functional vs non-functional testing. Functional tests are described as easier since they isolate code and ensure consistent outputs for given inputs, while non-functional tests involving things like concurrency are more difficult to test.
This document contains code samples in multiple programming languages that implement the "99 Bottles of Beer" song. Code examples are provided in Haskell, Ruby, Java, SmallBasic, and other languages. Each implementation shows a different approach to modeling the song and counting down bottles of beer in a concise yet readable way.
This document summarizes a presentation on strong-style pairing by Llewellyn Falco and Maaret Pyhäjärvi. It introduces the concepts of strong-style pairing versus traditional pairing. Examples are provided of exercises done in strong-style pairing, including navigating, language demos, and coding FizzBuzz. Benefits of strong-style pairing include rapid learning, increased productivity over time, and addressing traditional problems with pairing like disengagement or slowing people down. Homework is assigned to initiate pairing with a new person.
This document discusses user story mapping and provides an example of mapping out a morning routine. It explains that user story mapping helps create a shared understanding by focusing conversations on user experiences. The mapping process involves writing individual tasks or stories, organizing them into a narrative flow, exploring alternatives, distilling the map into a backbone, and slicing tasks to achieve specific outcomes. It then demonstrates this process by mapping out tasks for different goals of getting ready in the morning, either in a rush or with more leisurely time.
This document introduces several innovation games that can be used by agile project managers and organizations. It describes games like the hot air balloon, prune the product tree, and what a volunteer wants that involve participants providing feedback through visual and interactive exercises. The benefits of these games include organizing ideas, understanding customer expectations, identifying priorities, and making strategic decisions. Guidelines are provided for facilitators to run the games effectively and get valuable input from participants.
This document discusses techniques for software project estimation. It recommends providing estimates as ranges rather than specific numbers, and always clarifying what an estimate will be used for. It emphasizes aggregating independent estimates, using past project data to calibrate estimates, and not negotiating estimates or commitments. Key techniques include decomposing work into independently estimable units, using the "law of large numbers" for accuracy, and re-estimating regularly based on actual project velocity. Overall, the document provides guidance for creating estimates that are useful without being overly precise commitments.
Arlen Bankston
Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.
The document provides instructions for connecting with others on LinkedIn in 5 steps: open LinkedIn, select "My Network", select the "Add" button, choose "Find Nearby", and then turn on location services and connect with contacts or message existing connections.
The document appears to be a slide presentation about test driven development (TDD). It includes slides about daily schedules, types of knowledge related to TDD skills, combining different TDD skills, writing test scenarios, the differences between BDD and an "evil programmer" approach, testing functional code, faking code to pass tests first before implementing, resources for learning more about TDD including a blog and video, and thanks and contact information. The presentation provides an overview of key concepts and best practices for TDD.
The document discusses different data formats for representing a book including XML, JSON, YAML, simple/CSV/tabbed text formats, and a C++ operator overload format. It also provides resources for approval testing and mob programming.
This document discusses the return on investment (ROI) of dedicating time each day to learning and self-improvement. It notes that small gains over time, such as dedicating just one hour per day or improving skills by 1% each month, can lead to exponential growth when compounded over months and years. Various learning techniques and formats are presented such as mob programming, pair programming, and workshops. The importance of cultivating a learning culture at work is emphasized.
This document discusses mob programming, where all team members work together on the same task at the same time. Key aspects include having a designated driver who writes code while others navigate and collaborate. Benefits highlighted are bringing together diverse perspectives and skills to solve problems faster and with higher quality. Mob programming encourages learning, idea sharing, and focusing on work quality over individual credit. It works best when team size allows everyone to actively contribute.
Sparrow Decks apply Machine Learning techniques to your own brain. It's AI for I.
Here we will train your subconscious to recognize:
House vs Song sparrows
Cluttered vs Relevant code
Long vs Short lines
Long vs Short methods
Good vs Bad names
Duplication vs distinct code
Inconsistency vs Duplication
This document discusses strategies for throwing better exceptions in code. It presents examples of poorly thrown exceptions and demonstrates how to improve them by including more context and details. The key rules discussed are to use variable values, wrap bad exceptions, provide context, show runtime details, include tl;dr examples, add extra information, and highlight root causes when throwing exceptions. This aims to give confused coders more guidance in debugging and understanding where errors are occurring.
The document outlines the roles and responsibilities of various participants in a coding exercise. It describes 6 roles: the Announcer who reads observations out loud, the Collector who gathers observations, the Keeper who manages rotation of roles, the Navigator who guides the Driver, the Driver who types code, and the Un-sticker who asks questions to nudge the Navigator. Each role has specific tasks to contribute to a collaborative problem solving process.
Teaching kids programming with the Intentional MethodLlewellyn Falco
This document describes Teaching Kids Programming (TKP), a free and modular programming courseware for teaching programming concepts to kids ages 10 and up. TKP has been tested on over 2,000 kids and takes an agile approach, emphasizing quick setup, collaborative and iterative learning, and rapid feedback. The course is organized into units that each focus on an experience area like "Recipe", "Recap", or "Quiz". These experiences guide students through activities like executing their first program within minutes, exploring mistakes to discover patterns, and taking quizzes where 100% of pairs get 100% right. The goal is for students to experience the joy of programming through experimentation and variations on ideas. Teachers are encouraged to try
Some Helpful Observations for successful Mob ProgrammingLlewellyn Falco
The document provides several observations for successful mob programming:
- Always be actively contributing to the mob in any way possible, such as navigation, proofreading, asking questions, or offering suggestions.
- Respect each other's strengths and weaknesses as individuals and as the group works together to learn.
- Respect the existing code while still looking to improve it, without insulting previous work and thoughtfully navigating changes.
The document discusses various ways that video games can teach skills through techniques like repetition, exploration, immersion, feedback, and hints. It provides examples of games like Settlers of Catan that teach through repetition, Minecraft that encourages exploration, GTA that enables immersion, and Portal that gives feedback. The document also shares resources for teaching kids programming and contact information for the author.
This is a blank code report for you to print and fill in your self. If you are wondering what a completed one looks like, check out: http://www.slideshare.net/llewellynfalco/the-code-report-v1
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
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 .
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
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.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/