The document discusses extending continuous integration practices to include more thorough automated system testing. It proposes automating the installation, integration, simulation, and verification processes to continuously test the full system after every code change. This helps find defects earlier but cannot replace traditional testing. The approach aims to pay more for testing now through practices like automated staging to avoid larger costs later from bugs. The ultimate goal is to enable releasing new code every iteration through these extensive testing practices.
The document discusses using agile principles and contracts for large government IT projects. It proposes that "time and material" contracts create the most satisfaction, as they allow for collaboration over negotiation. However, large tax-funded projects require more structure. The document examines how the Norwegian PS2000 standard combines agile practices with target pricing models. It provides examples of projects that successfully blended agile and contracts, as well as areas that caused issues. Finally, it envisions an alternative approach using competitive bidding on small, independent teams with unit pricing for user stories. This could encourage collaboration over lengthy negotiations and change orders.
PĆ„stand: Ć rsaken til at dagens kontraktregime trekker i retning fossefallsprosjekter uten rom for lƦring er at kontraktene forutsetter at prisen for prosjektet er lĆ„st ved oppstart. For Ć„ angi pris, mĆ„ det beskrives hva prisen gjelder.
Forslag til lĆøsning: Kontrakten kan regulerer prisen per feature pĆ„ produktkĆøen. Kunden har da muligheten til Ć„ endre produktkĆøen etter behov uten at dette blir en kontraktsmessig endring.
Jeg kaller dette Stykkpriskontrakt.
For Ć„ fastsette initiell stykkpris og for Ć„ understĆøtte konkurranse mellom leverandĆører foreslĆ„r jeg videre at et utvalg av leverandĆører inviteres til Ć„ levere funksjonalitet i en konkurransefase. Den beste fĆ„r kontrakten og erfaringsdata fra konkurransefasen brukes som input til Ć„ bestemme initiell stykkpris.
Jeg kaller dette prestasjonsbasert konkurranse.
Dette er lĆøse ideer og har aldri vƦrt prĆøvd.
1) The document discusses principles of agile programming such as pair programming, test-driven development, and refactoring.
2) It describes a demonstration of test-driven development using a minesweeper game, highlighting how tests are written first and then code is produced to pass those tests.
3) The document emphasizes that practicing these agile techniques through deliberate practice of coding katas can help programmers improve their skills and "think better" above just the code level. Regular practice is encouraged at meetups like the Prague Coding Dojo.
The document discusses using stories and scenarios to help understand user requirements for software systems. It provides examples of stories describing a user purchasing items from a website and a power grid operator restoring balance in the electricity system. The document advocates planning software development in sprints and releases based on breaking down scenarios into individual features or variations to help guide development in an iterative manner.
The document discusses agile architecture and the role of a solution architect. It defines a solution architect as someone who understands the customer's problem, including constraints and domain knowledge, and uncovers and communicates a feasible solution. It emphasizes that discovering the solution is a team effort. The architect's responsibilities include understanding the problem, describing the problem context and domain model, describing the proposed solution, and simplifying and delivering the architecture and software.
These are my slides from the Bare-Bones Software Architecture course at XP Days Ukraine 2012. The workshop outlines a quick workshop-oriented process for initiating software projects
The document discusses extending continuous integration practices to include more thorough automated system testing. It proposes automating the installation, integration, simulation, and verification processes to continuously test the full system after every code change. This helps find defects earlier but cannot replace traditional testing. The approach aims to pay more for testing now through practices like automated staging to avoid larger costs later from bugs. The ultimate goal is to enable releasing new code every iteration through these extensive testing practices.
The document discusses using agile principles and contracts for large government IT projects. It proposes that "time and material" contracts create the most satisfaction, as they allow for collaboration over negotiation. However, large tax-funded projects require more structure. The document examines how the Norwegian PS2000 standard combines agile practices with target pricing models. It provides examples of projects that successfully blended agile and contracts, as well as areas that caused issues. Finally, it envisions an alternative approach using competitive bidding on small, independent teams with unit pricing for user stories. This could encourage collaboration over lengthy negotiations and change orders.
PĆ„stand: Ć rsaken til at dagens kontraktregime trekker i retning fossefallsprosjekter uten rom for lƦring er at kontraktene forutsetter at prisen for prosjektet er lĆ„st ved oppstart. For Ć„ angi pris, mĆ„ det beskrives hva prisen gjelder.
Forslag til lĆøsning: Kontrakten kan regulerer prisen per feature pĆ„ produktkĆøen. Kunden har da muligheten til Ć„ endre produktkĆøen etter behov uten at dette blir en kontraktsmessig endring.
Jeg kaller dette Stykkpriskontrakt.
For Ć„ fastsette initiell stykkpris og for Ć„ understĆøtte konkurranse mellom leverandĆører foreslĆ„r jeg videre at et utvalg av leverandĆører inviteres til Ć„ levere funksjonalitet i en konkurransefase. Den beste fĆ„r kontrakten og erfaringsdata fra konkurransefasen brukes som input til Ć„ bestemme initiell stykkpris.
Jeg kaller dette prestasjonsbasert konkurranse.
Dette er lĆøse ideer og har aldri vƦrt prĆøvd.
1) The document discusses principles of agile programming such as pair programming, test-driven development, and refactoring.
2) It describes a demonstration of test-driven development using a minesweeper game, highlighting how tests are written first and then code is produced to pass those tests.
3) The document emphasizes that practicing these agile techniques through deliberate practice of coding katas can help programmers improve their skills and "think better" above just the code level. Regular practice is encouraged at meetups like the Prague Coding Dojo.
The document discusses using stories and scenarios to help understand user requirements for software systems. It provides examples of stories describing a user purchasing items from a website and a power grid operator restoring balance in the electricity system. The document advocates planning software development in sprints and releases based on breaking down scenarios into individual features or variations to help guide development in an iterative manner.
The document discusses agile architecture and the role of a solution architect. It defines a solution architect as someone who understands the customer's problem, including constraints and domain knowledge, and uncovers and communicates a feasible solution. It emphasizes that discovering the solution is a team effort. The architect's responsibilities include understanding the problem, describing the problem context and domain model, describing the proposed solution, and simplifying and delivering the architecture and software.
These are my slides from the Bare-Bones Software Architecture course at XP Days Ukraine 2012. The workshop outlines a quick workshop-oriented process for initiating software projects
This document summarizes an Agile programming experience day in Ukraine. The goal is for attendees to have fun programming now and to think better by practicing their skills. The agenda includes a description of a minesweeper coding kata demonstration featuring pair programming. Attendees are encouraged to observe how the pair interacts, designs the code, and progresses through testing. The benefits of practices like test-driven development, pairing, and refactoring are discussed. The conclusion encourages practicing programming skills at work, with coding dojos, and by freeing the mind.
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk introduces concepts like test-driven development (TDD), pair programming, and refactoring. A demonstration of pair programming on a coding kata is shown. The key points emphasized are that practicing TDD in small iterative steps, pairing with others, and continuously refactoring code can help programmers improve quality and think in a more deliberate, mindful way about their work. The overall message is that becoming a better programmer requires freeing one's mind and practicing programming as an art.
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk demonstrates test-driven development and pair programming. It discusses the benefits of these practices, such as producing higher quality code through simplicity, communication, and feedback. It encourages programmers to practice deliberately, both at work and at home, in order to continuously improve. The conclusion emphasizes freeing the mind and practicing programming as an art.
Coding Dojo: Fun with Tic-Tac-Toe (2014)Peter Kofler
Ā
This document summarizes a coding dojo event focused on tic-tac-toe. The event introduces pair programming and test-driven development techniques. Attendees work in pairs to implement tic-tac-toe under constraints, such as writing the worst code possible initially and then refactoring without talking. The goal is to learn through challenges and reflection on how to write better code.
This document provides an overview of a presentation on test-driven development (TDD) and JavaScript. It discusses concepts like refactoring, unit testing, pair programming, and practicing TDD in small exercises called code katas. The presentation covers JavaScript topics like variable scoping and introduces the basic steps of TDD: writing a failing test first, then just enough code to make it pass before refactoring. It emphasizes that TDD helps produce a simple design and provides quick feedback.
Coding Dojo with focus on naming. Rules of the dojo are Pair Programming & TDD. Constraints are challenges during the dojo. Moving to the extreme is a way of learning. We are coding the game of Tic-Tac-Toe and everything - but the names of test methods - is named using random dices. Specifically using these random dices with enterprise-y useless names.
Test Driven Development - For Girl Geeks Night SydneyJo Cranford
Ā
This document discusses Test Driven Development (TDD). TDD involves writing a failing test, writing the code to make it pass, then writing another failing test. This leads to an application design that is leaner and simpler, with interfaces better designed from the user's perspective. Some key points:
- TDD breaks complexity into small, simple steps and thinks from the outside in from the user's point of view.
- TDD results in tests that act as documentation and bugs being identified and fixed sooner.
- Challenges of TDD include it being hard work and some things not lending themselves to automated tests.
This document outlines Peter Kofler's coding dojo on tic-tac-toe. The dojo focuses on collaborative coding through a ping-pong process where one developer writes a test and the other writes code to pass the test. The dojo structure includes introductions, coding sessions, breaks, and retrospectives. The exercise is to collaboratively code a tic-tac-toe game through the ping-pong process while focusing on quality over speed.
This document discusses brutal coding constraints that can be used during coding dojos or retreats to improve coding skills. It proposes constraints like removing conditionals, loops, and mutable data to solve problems like implementing tic-tac-toe. Participants are asked to implement a two-player and AI version of tic-tac-toe under these constraints. The goal is to learn through challenges and collaboratively reflect on the experience.
The document provides an overview of a coding lesson plan that includes:
1) Reviewing what is already known about computers and coding through examples.
2) Learning about coding and programming concepts such as programming languages.
3) Hands-on coding activities using a block-based visual programming language on code.org to write code for games like Angry Birds.
Pair programming involves two programmers working together at one workstation to write code. The benefits include improved code quality through peer review, knowledge sharing between partners, and mentoring of junior developers. One person acts as the driver, writing code, while the other is the navigator and oversees the work. Regular switching of roles and partners is recommended to keep sessions productive. Communication and respect between partners is important for effective pairing.
Serendipity by Design - IxD S. America 13Dave Malouf
Ā
I opened up the talks section of this great conference in Recife, BR in 2013.
The talk was talking about how design can use the powerful tools of art and it's close association to non-linear creativity and associative thinking by building the space and culture of the studio environment.
The Shitposting AI With Thomas Endres & Jonas Mayer | Current 2022HostedbyConfluent
Ā
Using modern AI approaches such as GPT-2, Tacotron and Conformers, we created fully autonomous robot heads that engage in heated social media discussions, completely taking the human out of the loop. The TNG Innovation Hacking Team created a prototype of an end-to-end natural language understanding system, employing techniques such as Speech-to-Text (STT), Conditional Text Generation and Text-To-Speech (TTS).
Social media comments have become the predominant medium for public discussion. However, discussions on Facebook, Twitter and Reddit are notorious for their poor debate culture and missing conclusiveness. The obvious solution to this tremendous waste of time is automation of such fruitless discussions using a bot.
In this talk, we will give an introduction to NLP, focussing on the concepts of STT, Text Generation and TTS. Using live demos, we will guide you through the process of scraping social media comments, training a text generation model, synthesizing millions of voices and building IoT robot heads.
This document summarizes a talk on getting comfortable with behavior driven development (BDD). It begins by defining BDD and explaining that it builds on test driven development (TDD) by describing application behavior from an outside-in perspective with customer involvement. It then discusses that TDD focuses on writing tests first before code, using a red-green-refactor workflow. BDD further crystallizes requirements and ensures programmer priorities are aligned by implementing tests in business language rather than code. The document emphasizes thinking through requirements before writing code or tests to ensure the correct behavior is described and tested.
Peter Kofler presented on pair programming. Some key benefits of pair programming include improved code quality, knowledge sharing between partners, and mentoring junior developers. Effective pair programming involves two programmers working together at one workstation, with one acting as the driver writing code while the other navigates, reviewing the work. It is most useful for production code, programming tasks requiring problem solving, and mentoring novices. Managing the human dynamics between partners and practicing techniques like ping-pong pairing are important for success.
Peter Kofler discusses deliberate practice techniques for software developers to improve their skills. He describes code katas, which are short programming exercises done daily for practice and memorization. Coding dojos are regular meetups where developers work on katas together for learning and fun away from work pressures. Code retreats are full-day intensive sessions focusing on fundamentals through pair programming and switching partners frequently. The goal is to learn through practice and experimentation rather than production work.
The document summarizes a Python coding dojo event that covered test-driven development and pair programming techniques. Attendees learned about TDD processes like writing tests first, red-green-refactor cycles, and practiced pair programming and switching roles frequently. They worked on a "word wrap" coding kata exercise in pairs using TDD and discussed reflections on the design of their code solutions and lessons learned at the end.
The document discusses an approach to test-driven development called "baby steps" where developers write one test and the minimum code to pass that test within a 2 minute timer. They then refactor within the next timer period before repeating the process. It recommends practicing this approach to build TDD skills when developing a tic-tac-toe game.
The London Python Code Dojo - An Education in Developer EducationNicholas Tollervey
Ā
The London Python Code Dojo is a monthly community meeting where Python developers practice coding together. Attendees can learn through hands-on practice, teaching each other, and exploring different solutions. The dojo aims to be fun and safe for learning from mistakes. Organizers focus on setting a positive goal and providing feedback to help learning. The dojo format has been adapted from its origins to better suit the community through show-and-tell, team projects, and informal socializing over food and drinks.
Five favorite features of native apps that you might not realize you can do on a web application.
Supporting slides for my presentation at JavaBin June 11, 2015.
This document summarizes an Agile programming experience day in Ukraine. The goal is for attendees to have fun programming now and to think better by practicing their skills. The agenda includes a description of a minesweeper coding kata demonstration featuring pair programming. Attendees are encouraged to observe how the pair interacts, designs the code, and progresses through testing. The benefits of practices like test-driven development, pairing, and refactoring are discussed. The conclusion encourages practicing programming skills at work, with coding dojos, and by freeing the mind.
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk introduces concepts like test-driven development (TDD), pair programming, and refactoring. A demonstration of pair programming on a coding kata is shown. The key points emphasized are that practicing TDD in small iterative steps, pairing with others, and continuously refactoring code can help programmers improve quality and think in a more deliberate, mindful way about their work. The overall message is that becoming a better programmer requires freeing one's mind and practicing programming as an art.
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk demonstrates test-driven development and pair programming. It discusses the benefits of these practices, such as producing higher quality code through simplicity, communication, and feedback. It encourages programmers to practice deliberately, both at work and at home, in order to continuously improve. The conclusion emphasizes freeing the mind and practicing programming as an art.
Coding Dojo: Fun with Tic-Tac-Toe (2014)Peter Kofler
Ā
This document summarizes a coding dojo event focused on tic-tac-toe. The event introduces pair programming and test-driven development techniques. Attendees work in pairs to implement tic-tac-toe under constraints, such as writing the worst code possible initially and then refactoring without talking. The goal is to learn through challenges and reflection on how to write better code.
This document provides an overview of a presentation on test-driven development (TDD) and JavaScript. It discusses concepts like refactoring, unit testing, pair programming, and practicing TDD in small exercises called code katas. The presentation covers JavaScript topics like variable scoping and introduces the basic steps of TDD: writing a failing test first, then just enough code to make it pass before refactoring. It emphasizes that TDD helps produce a simple design and provides quick feedback.
Coding Dojo with focus on naming. Rules of the dojo are Pair Programming & TDD. Constraints are challenges during the dojo. Moving to the extreme is a way of learning. We are coding the game of Tic-Tac-Toe and everything - but the names of test methods - is named using random dices. Specifically using these random dices with enterprise-y useless names.
Test Driven Development - For Girl Geeks Night SydneyJo Cranford
Ā
This document discusses Test Driven Development (TDD). TDD involves writing a failing test, writing the code to make it pass, then writing another failing test. This leads to an application design that is leaner and simpler, with interfaces better designed from the user's perspective. Some key points:
- TDD breaks complexity into small, simple steps and thinks from the outside in from the user's point of view.
- TDD results in tests that act as documentation and bugs being identified and fixed sooner.
- Challenges of TDD include it being hard work and some things not lending themselves to automated tests.
This document outlines Peter Kofler's coding dojo on tic-tac-toe. The dojo focuses on collaborative coding through a ping-pong process where one developer writes a test and the other writes code to pass the test. The dojo structure includes introductions, coding sessions, breaks, and retrospectives. The exercise is to collaboratively code a tic-tac-toe game through the ping-pong process while focusing on quality over speed.
This document discusses brutal coding constraints that can be used during coding dojos or retreats to improve coding skills. It proposes constraints like removing conditionals, loops, and mutable data to solve problems like implementing tic-tac-toe. Participants are asked to implement a two-player and AI version of tic-tac-toe under these constraints. The goal is to learn through challenges and collaboratively reflect on the experience.
The document provides an overview of a coding lesson plan that includes:
1) Reviewing what is already known about computers and coding through examples.
2) Learning about coding and programming concepts such as programming languages.
3) Hands-on coding activities using a block-based visual programming language on code.org to write code for games like Angry Birds.
Pair programming involves two programmers working together at one workstation to write code. The benefits include improved code quality through peer review, knowledge sharing between partners, and mentoring of junior developers. One person acts as the driver, writing code, while the other is the navigator and oversees the work. Regular switching of roles and partners is recommended to keep sessions productive. Communication and respect between partners is important for effective pairing.
Serendipity by Design - IxD S. America 13Dave Malouf
Ā
I opened up the talks section of this great conference in Recife, BR in 2013.
The talk was talking about how design can use the powerful tools of art and it's close association to non-linear creativity and associative thinking by building the space and culture of the studio environment.
The Shitposting AI With Thomas Endres & Jonas Mayer | Current 2022HostedbyConfluent
Ā
Using modern AI approaches such as GPT-2, Tacotron and Conformers, we created fully autonomous robot heads that engage in heated social media discussions, completely taking the human out of the loop. The TNG Innovation Hacking Team created a prototype of an end-to-end natural language understanding system, employing techniques such as Speech-to-Text (STT), Conditional Text Generation and Text-To-Speech (TTS).
Social media comments have become the predominant medium for public discussion. However, discussions on Facebook, Twitter and Reddit are notorious for their poor debate culture and missing conclusiveness. The obvious solution to this tremendous waste of time is automation of such fruitless discussions using a bot.
In this talk, we will give an introduction to NLP, focussing on the concepts of STT, Text Generation and TTS. Using live demos, we will guide you through the process of scraping social media comments, training a text generation model, synthesizing millions of voices and building IoT robot heads.
This document summarizes a talk on getting comfortable with behavior driven development (BDD). It begins by defining BDD and explaining that it builds on test driven development (TDD) by describing application behavior from an outside-in perspective with customer involvement. It then discusses that TDD focuses on writing tests first before code, using a red-green-refactor workflow. BDD further crystallizes requirements and ensures programmer priorities are aligned by implementing tests in business language rather than code. The document emphasizes thinking through requirements before writing code or tests to ensure the correct behavior is described and tested.
Peter Kofler presented on pair programming. Some key benefits of pair programming include improved code quality, knowledge sharing between partners, and mentoring junior developers. Effective pair programming involves two programmers working together at one workstation, with one acting as the driver writing code while the other navigates, reviewing the work. It is most useful for production code, programming tasks requiring problem solving, and mentoring novices. Managing the human dynamics between partners and practicing techniques like ping-pong pairing are important for success.
Peter Kofler discusses deliberate practice techniques for software developers to improve their skills. He describes code katas, which are short programming exercises done daily for practice and memorization. Coding dojos are regular meetups where developers work on katas together for learning and fun away from work pressures. Code retreats are full-day intensive sessions focusing on fundamentals through pair programming and switching partners frequently. The goal is to learn through practice and experimentation rather than production work.
The document summarizes a Python coding dojo event that covered test-driven development and pair programming techniques. Attendees learned about TDD processes like writing tests first, red-green-refactor cycles, and practiced pair programming and switching roles frequently. They worked on a "word wrap" coding kata exercise in pairs using TDD and discussed reflections on the design of their code solutions and lessons learned at the end.
The document discusses an approach to test-driven development called "baby steps" where developers write one test and the minimum code to pass that test within a 2 minute timer. They then refactor within the next timer period before repeating the process. It recommends practicing this approach to build TDD skills when developing a tic-tac-toe game.
The London Python Code Dojo - An Education in Developer EducationNicholas Tollervey
Ā
The London Python Code Dojo is a monthly community meeting where Python developers practice coding together. Attendees can learn through hands-on practice, teaching each other, and exploring different solutions. The dojo aims to be fun and safe for learning from mistakes. Organizers focus on setting a positive goal and providing feedback to help learning. The dojo format has been adapted from its origins to better suit the community through show-and-tell, team projects, and informal socializing over food and drinks.
Five favorite features of native apps that you might not realize you can do on a web application.
Supporting slides for my presentation at JavaBin June 11, 2015.
Can you go faster with less weight? In 45 minutes, I build a web server with an address book with tests firsts and no frameworks. What can you do if you really understand what's going on?
Good programming is not something that can be explained, it has to be experienced. In this talk, you will see pair programming and test-driven development in action. The talk will involve the audience and draw on your insight to show how programming can be more fun! If you want to understand how serious test-driven development looks, this talk is for you.
The talk is based around a demonstration and interactive audience discussion, so the slides will not capture much of the content.
In this talk, we will go through a practical approach for remote pair programming adopted for high-latency situations. We will demonstrate remote pair programming with a live example and we will discuss the advantages and usages of the approach.
The document discusses agile architecture and solution design, outlining how an architect should understand the customer problem, uncover and communicate a feasible solution through describing the architecture, simplifying it based on constraints, and delivering the software solution through iterative development and demos using a technique called "rainbow planning".
The document describes Johannes Brodwall's philosophy of "bare-knuckle web development" which advocates for lightweight frameworks, test-driven development, and avoiding unnecessary complexity. It then demonstrates this approach through building a simple phonebook web application in Java using only the bare essentials like servlets and XML parsing. Finally, it discusses further directions this approach could be taken, such as building applications for the Norwegian agricultural authority and power grid operator.
This document summarizes the agenda for a coding dojo event, which includes demonstrations of test-driven development and pair programming, followed by several coding kata exercises involving topics like prime factorization, minesweeper, Yahtzee, and converting numbers to Roman numerals. Participants will work individually and in pairs on test cases for these kata. There will also be two rounds of an "extreme startup" code competition. Retrospectives are scheduled after each activity to discuss lessons learned.
This document discusses using agile principles and practices in government contracting. It proposes that customer collaboration over contract negotiation better serves agile values. It describes how some Norwegian government projects have incorporated elements of agile, like sprints and product backlogs, while still using traditional cost-plus contracts. The document suggests a model of competitive bidding between suppliers to deliver user stories could further foster collaboration over negotiation. Overall, it argues that Norway provides a starting point but there is still room for improvement in aligning contracts with agile principles.
This document discusses techniques for practicing and improving programming skills. It recommends practicing test-driven development, pairing programming, refactoring with all tests passing, and continuous integration. It emphasizes practicing testing contracts and interfaces rather than behavior, and testing programs from the outside-in perspective. The document concludes by encouraging freeing the mind and practicing programming as an art.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
Ā
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
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.
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 .
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!
āBuilding and Scaling AI Applications with the Nx AI Manager,ā a Presentation...Edge AI and Vision Alliance
Ā
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.
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.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
Ā
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
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.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Ā
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Ā
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.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Ā
Are you ready to revolutionize how you handle data? Join us for a webinar where weāll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, weāll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sourcesāfrom PDF floorplans to web pagesāusing FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether itās populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
Weāll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Ā
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.
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).
14. What did you see?
ā¢ How often did we switch ādriverā?
ā¢ Effects of pairing?
ā¢ What did the ānon-driverā do?
15. What did you see?
ā¢ Was the step size right?
ā¢ What was the first test?
ā¢ How did we decide next test?
ā¢ What was the final test?
16. What did you see?
ā¢ Language tricks?
ā¢ Did we refactor the right amount?
ā¢ How long was the code red?
ā¢ Strengths in final design
ā¢Weaknesses in final design
51. Thank you
johannes.brodwall@steria.no
http://johannesbrodwall.com
http://twitter.com/jhannes
(Please tweet in Cyrillic with
english-like words)
Editor's Notes
Note to translator: I willexplainthe game of minesweeper whileshowingthis slide.The game initiallypresents a fieldwheretherearehidden minesWhentheplayerclickson a cell, eitherhe Ā«stepsĀ» on a mine or he reveals thecellIf he Ā«stepson a mineĀ», the game is over, player losesIf he reveals thecell, thecelltellshowmany mines arenext to it
Note to translator: I willexplainthe game of minesweeper whileshowingthis slide.The game initiallypresents a fieldwheretherearehidden minesWhentheplayerclickson a cell, eitherhe Ā«stepsĀ» on a mine or he reveals thecellIf he Ā«stepson a mineĀ», the game is over, player losesIf he reveals thecell, thecelltellshowmany mines arenext to it
Note to translator:Here I willexplaintheworkingofthe program wewillcreate:Given a definitionof a minefieldwith mines as stars and non-mines as periods, the program should output the hints for eachcell (as in theprevious screen shot)Ā«If youāre not familiarwith mine sweeper, youcan just ask a project managerĀ»
Note to translator: Here, Iwill ask the English speakingmembersoftheaudience to give feedback onwhattheysaw. I will hand outchocolates to those to answer. ļ
Note to translator: If thereās not toomany questions beforethis, I willdemonstratethiscodewith in Eclipse, ratherthan talk about it.
Note to translator: If thereās not toomany questions beforethis, I willdemonstratethiscodewith in Eclipse, ratherthan talk about it.
Note to translator: Here, I willexplainhow pair programmingcanwork in practice:One person writes a failing test and theother person writesthecode to make it pass. Thenthe person whomadethe test pass writesthenext test.In theexamplewithme and Boris, weswitched Ā«driversĀ» (the person at thekeyboard) aboutonce a minute. On real lifeproject, I usuallyexperiencethatweswitch drivers everytenminutes or so.Itās alsoimportant to refactorbetween tests. I like to onlyrefactorwhenthecode is green. This way I knowthatthecodedoesnāt stop working. Therearetwoways to thinkaboutthis:Either, ifyoucan, refactorthecode and the tests a little to Ā«getreadyĀ» for thenext testOr, ifyouseethatyoucanāt make the test pass, commentout (or @Ignore) the test and refactoron green.
Note to translator:Here I willexplain a Ā«pair programming starĀ».If the team feels it wouldbenefit from more programmers pair programmingwitheachother, youcancreate a Ā«pair programming starĀ».First, writethenamesofeach team member in a circleWhensomeone pair program withsomeoneelse, put a line betweentheirnamesThe resulting Ā«starĀ» can be used to reflectonyour team. Itās not necessarily a bad thingthat Sergey and Dmitro program together a lot, butitāsworthnoting
Note to translator: I may show a practical demo here, iftheaudiencewants it
Note to translator: On thefollowing screenshots, therearepictures from Oslo CodingDojo and Kiev CodingDojo. I willexplain (eachbulletpointononeofthefollowing slides):WemeetaboutonceeverymonthWeusuallymeet in a pub and program around a projector (withbeer!)We have also done a Code Retreat, where 24 peoplesetaside a full Saturday to practicecoding. Ā«During theweek, youcode for money. Today, youcode for youĀ»After I gave this talk in Kiev, AlekseySolntsev and othersorganized Kiev codingdojoAnyvolunteers to organize a CodingDojo in Moscow?