No matter what profession you’re in, our jobs can contain a variety of stress factors, which are unknown to individuals looking from the outside.
“TECH-LIVES MATTER: HANDS UP, DON’T REBOOT” is a lecture based on research that recommends corporations should devote in IT specific employee assistance agendas. Working as a Developer, Specialist, Designer, Engineer, Expert, Manager, and Technician demands a high level of precision over the extended period, and any minute lapse in one’s job could be disastrous.
MY METHOD OF HUMOR AND AFFECTION TITLED THE “DR. DRE METHOD.” ATTENDEES WILL LEARN TO:
D. DOWNLOAD the cause of your Stress.
R. Use a mental ROUTER to direct the stress to a secure site in your mind.
D. Learn to DELETE future Stress elements.
R. REBOOT yourself and focus on positive aspects.
E. ENCRYPT your mind to secure the positive parts.
The pressure of working in the field of computer technology can be a dream for the observers and the nightmare for the workers.
Working in the world of technology can be a great experience, which DEVELOPERS, SPECIALISTS, DESIGNERS, ENGINEERS, EXPERTS, MANAGERS AND TECHNICIANS create and dive each time they start working.
“TECH-LIVES MATTER, HANDS UP, DON’T REBOOT” offers solutions to support individuals who are afflicted by stress within the IT community is employee input, better task content, amplified job control, equal production values, career expansion, enhanced peer socialization, and more excellent workplace ergonomics.
Key Takeaways:
Overall Alertness- Regarding the Onset to Stress
Stress at one’s place of employment
Mentally Supporting Yourself
Recognize the best method in a tense setting
Identify Development Pains and Resolve Them with Idea FlowTechWell
With the explosion of new frameworks, a mountain of automation, and our applications distributed across hundreds of services in the cloud, the level of complexity in software development is growing at an insane pace. With increased complexity comes increased costs and risks. When diagnosing unexpected behavior can take days, weeks, or sometimes months, all while our release is on the line, our projects plunge into chaos. In the invisible world of software development, how do we identify what's causing our pain? How do we escape the chaos? Janelle Klein presents a novel approach to measuring the chaos, identifying the causes, and systematically driving improvement with a data-driven feedback loop. Rather than measuring the problems in the code, Janelle suggests measuring the "friction in Idea Flow", the time it takes a developer to diagnose and resolve unexpected confusion, which disrupts the flow of progress during development. With visibility of the symptoms, we can identify the cause—whether it's bad architecture, collaboration problems, or technical debt. Janelle discusses how to measure Idea Flow, why it matters, and the implications for our teams, our organizations, and our industry.
Detangling complex systems with compassion & production excellenceDevOpsDays DFW
Taming the complex distributed systems we're responsible for requires changing not just the tools and technical approaches we use; it also requires changing who is involved in production, how they collaborate, and how we measure success.
In this talk, you'll learn about several practices core to production excellence: giving everyone a stake in production, collaborating to ensure observability, measuring with Service Level Objectives, and prioritizing improvements using risk analysis.
How does a technical writer build a super-productive relationship with an engineering team? This presentation shares some tips ranging from co-location (a fancy word for sitting together) to capitalising on your core skills as technical writer (a sure-fire way of becoming a valued member of the team).
Doc sprints: The ultimate in collaborative document developmentSarah Maddox
This session discusses how to plan and run a successful doc sprint. The result is high-quality documentation, happy customers, and an enhanced reputation for your tech comm team.
The recording in https://eviltester.com/talks has:
- longer practice session recording
- live recording - local recording better quality
- 8 bonus recordings with an extra hour of material
- will automation take over
- impact of buzzwords
- how to cope with trends
- contextual problem solving
- information about the references
- exercises
- behind the scenes look at how the talk was prepared and tools used
- transcripts
- subtitles
Test Driven Development: Blueprint, Toolbox, and Master CraftStephen Ritchie
Many say that the practice of test driven development (TDD) has the ability to transform software engineering. Let’s break it down from a skeptical pragmatist’s viewpoint. This presentation focuses on three key ideas; the blueprint, the toolbox, and the master craft. Let’s look at TDD as a blueprint for writing code and discuss the implications and benefit. Let’s go beyond the theoretical application of TDD and focus on the toolbox, with examples of what developers need to know to get going. Finally, TDD is a master craft of Agile engineering. To be effective with TDD, let’s look at the progression of skills needed to achieve the promised results of TDD and to maximize its value.
Stephen is the organizer of DC Alt.Net (http://bit.ly/ZRDxUj). He frequent speaker and trainer on many .NET topics, including automated testing, continuous integration, code analysis, and .NET best practices.Stephen is the author of the book "Pro .NET Best Practices" (http://amzn.to/v8TD8E).
No matter what profession you’re in, our jobs can contain a variety of stress factors, which are unknown to individuals looking from the outside.
“TECH-LIVES MATTER: HANDS UP, DON’T REBOOT” is a lecture based on research that recommends corporations should devote in IT specific employee assistance agendas. Working as a Developer, Specialist, Designer, Engineer, Expert, Manager, and Technician demands a high level of precision over the extended period, and any minute lapse in one’s job could be disastrous.
MY METHOD OF HUMOR AND AFFECTION TITLED THE “DR. DRE METHOD.” ATTENDEES WILL LEARN TO:
D. DOWNLOAD the cause of your Stress.
R. Use a mental ROUTER to direct the stress to a secure site in your mind.
D. Learn to DELETE future Stress elements.
R. REBOOT yourself and focus on positive aspects.
E. ENCRYPT your mind to secure the positive parts.
The pressure of working in the field of computer technology can be a dream for the observers and the nightmare for the workers.
Working in the world of technology can be a great experience, which DEVELOPERS, SPECIALISTS, DESIGNERS, ENGINEERS, EXPERTS, MANAGERS AND TECHNICIANS create and dive each time they start working.
“TECH-LIVES MATTER, HANDS UP, DON’T REBOOT” offers solutions to support individuals who are afflicted by stress within the IT community is employee input, better task content, amplified job control, equal production values, career expansion, enhanced peer socialization, and more excellent workplace ergonomics.
Key Takeaways:
Overall Alertness- Regarding the Onset to Stress
Stress at one’s place of employment
Mentally Supporting Yourself
Recognize the best method in a tense setting
Identify Development Pains and Resolve Them with Idea FlowTechWell
With the explosion of new frameworks, a mountain of automation, and our applications distributed across hundreds of services in the cloud, the level of complexity in software development is growing at an insane pace. With increased complexity comes increased costs and risks. When diagnosing unexpected behavior can take days, weeks, or sometimes months, all while our release is on the line, our projects plunge into chaos. In the invisible world of software development, how do we identify what's causing our pain? How do we escape the chaos? Janelle Klein presents a novel approach to measuring the chaos, identifying the causes, and systematically driving improvement with a data-driven feedback loop. Rather than measuring the problems in the code, Janelle suggests measuring the "friction in Idea Flow", the time it takes a developer to diagnose and resolve unexpected confusion, which disrupts the flow of progress during development. With visibility of the symptoms, we can identify the cause—whether it's bad architecture, collaboration problems, or technical debt. Janelle discusses how to measure Idea Flow, why it matters, and the implications for our teams, our organizations, and our industry.
Detangling complex systems with compassion & production excellenceDevOpsDays DFW
Taming the complex distributed systems we're responsible for requires changing not just the tools and technical approaches we use; it also requires changing who is involved in production, how they collaborate, and how we measure success.
In this talk, you'll learn about several practices core to production excellence: giving everyone a stake in production, collaborating to ensure observability, measuring with Service Level Objectives, and prioritizing improvements using risk analysis.
How does a technical writer build a super-productive relationship with an engineering team? This presentation shares some tips ranging from co-location (a fancy word for sitting together) to capitalising on your core skills as technical writer (a sure-fire way of becoming a valued member of the team).
Doc sprints: The ultimate in collaborative document developmentSarah Maddox
This session discusses how to plan and run a successful doc sprint. The result is high-quality documentation, happy customers, and an enhanced reputation for your tech comm team.
The recording in https://eviltester.com/talks has:
- longer practice session recording
- live recording - local recording better quality
- 8 bonus recordings with an extra hour of material
- will automation take over
- impact of buzzwords
- how to cope with trends
- contextual problem solving
- information about the references
- exercises
- behind the scenes look at how the talk was prepared and tools used
- transcripts
- subtitles
Test Driven Development: Blueprint, Toolbox, and Master CraftStephen Ritchie
Many say that the practice of test driven development (TDD) has the ability to transform software engineering. Let’s break it down from a skeptical pragmatist’s viewpoint. This presentation focuses on three key ideas; the blueprint, the toolbox, and the master craft. Let’s look at TDD as a blueprint for writing code and discuss the implications and benefit. Let’s go beyond the theoretical application of TDD and focus on the toolbox, with examples of what developers need to know to get going. Finally, TDD is a master craft of Agile engineering. To be effective with TDD, let’s look at the progression of skills needed to achieve the promised results of TDD and to maximize its value.
Stephen is the organizer of DC Alt.Net (http://bit.ly/ZRDxUj). He frequent speaker and trainer on many .NET topics, including automated testing, continuous integration, code analysis, and .NET best practices.Stephen is the author of the book "Pro .NET Best Practices" (http://amzn.to/v8TD8E).
More Aim, Less Blame: How to use postmortems to turn failures into something ...Daniel Kanchev
Mistakes and failure are inevitable. Instead of being afraid of them, we should use them as lessons that help identify weak points in our organisations and systems. One way to do this is by writing blameless postmortems. Daniel details exactly how postmortems can help organizations and teams focus on improvement, and how that boosts work morale, makes products better, and strengthens your relationship with customers.
Data Science Popup Austin: Privilege and Supervised Machine LearningDomino Data Lab
Watch talk ⇒ http://bit.ly/1SGuwNs
I'll use the example of sentiment analysis to show that supervised machine learning has the potential to amplify the voices of the most privileged people in society. A sentiment analysis algorithm is considered ‘table stakes’ for any serious text analytics platform in social media, finance, or security. As an example of supervised machine learning, I'll show how these systems are trained. But I'll also show that they have the unavoidable property that they are better at spotting unsubtle expressions of extreme emotion. Such crude expressions are used by a particularly privileged group of authors: men. In this way, brands that depend on sentiment analysis to 'learn what people think' inevitably pay more attention to men. The problem doesn't stop with sentiment analysis: at every step of any model building process, we make choices that can introduce bias, enhance privilege, or break the law! I'll review these pitfalls, talk about how you can recognize them in your own work, and touch on some new academic work that aims to mitigate these harms.
The Junior Developer Survival Guide - GDI Ann Arbor 2/10/15James York
Are you new to the professional world of software development? Do you have new developers on your team? Are you wondering why college and the School of Hard Knocks did such a bad job preparing you to be a functional member of a high-performing team? Take some advice from a junior dev who has walked the path and learn to avoid rookie mistakes. Learn the skills employers value and how to get them. We will discuss quick return actions that can be undertaken immediately, as well as long term, slow-burn investments in your career. This session will focus on technical and interpersonal advice to help make your first job search, entry-level hire, and first year as a developer go smoothly. A great career won’t just fall into your lap. It takes dedication, skill, persistence, and more than a little luck. Happily, we make our own luck.
Data Science Popup Austin: Conflict in Growing Data Science Organizations Domino Data Lab
Watch talk ➟ http://bit.ly/1NKPpQh
Eduardo Arino De La Rubia, VP of Product and Data Scientist in residence at Domino Data Lab talks about how to manage conflict in growing data science teams.
What is Shift Left Testing? Do you need to use that term to improve your Software Testing and Development process? I don't think so.
- why I don't use the term Shift Left
- Explanation of what Shift Left means when people use it
- Explanation of what Shift Left might mean when people hear it
- How to Shift Left incorrectly
- How to improve your test process without using the phrase Shift Left.
Hire me for consultancy and buy my online books and training at:
- https://compendiumdev.co.uk
- http://eviltester.com
- http://seleniumsimplified.com
- http://javafortesters.com
Achieving Technical Excellence in Your Software Teams - from Devternity Peter Gfader
Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers.
Great software engineer teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live.
I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions.
Why would a company like to be "agile"?
How can a company achieve that?
How can you achieve Technical Excellence in your software teams?
What developer skills are more important than languages, methods or frameworks?
This will be an interactive session with a Q&A at the end.
Chaos Engineering, When should you release the monkeys?Thoughtworks
Chaos Engineering is listed as 'Trial' in the ThoughtWorks Tech Radar, but what is it really and how is it different from traditional testing? When and why should you get started with Chaos Engineering and is Chaos Monkey the right place to start when you do?
A tour of challenges today's software engineers will fast (and material they should familiarize themselves with) to cope with the issues that arise due to the distributed nature of today's applications.
DOES SFO 2016 - Greg Padak - Default to OpenGene Kim
Large enterprises have hierarchical organizations to define areas of responsibility and drive better accountability. Those structures often block cross-team interactions and knowledge sharing that slow innovation and agility. We will discuss strategies that use open platforms to drive meaningful development outcomes through collaboration and productivity across the enterprise.
Presentation for Harvard's ABCD Technology in Education group:
The Institute for Quantitative Social Science (IQSS) is a unique entity at Harvard - it combines research, software development, and specialized services to provide innovative solutions to research and scholarship problems at Harvard and beyond. I will talk about the software projects that IQSS is currently working on (Dataverse, Zelig, Consilience, and OpenScholar), including the research and development processes, the benefits provided to the Harvard community, and the impacts on research and scholarship.
You are a clever and talented person. You create beautiful designs, or perhaps you can architect a system that even a cat could use. Your peers adore you. Your clients love you. But (until now) you haven't *&^#^ been able to make Git bend to your will. It makes you angry inside that you have to ask your co-worker, again, for that *&^#^ command to share your work.
It's not you. It's Git. Promise.
We'll kick off this session with an explanation of why Git is so freaking hard to learn. Then we'll flip the tables and make YOU (not Git) the centre of attention. You'll learn how to define, and sketch out how version control works, using terms and scenarios that make sense to you. Yup, sketch. On paper. (Tablets and other electronic devices will be allowed, as long as you promise not to get distracted choosing the perfect shade for rage.) To this diagram you'll layer on the common Git commands that are used regularly by efficient Git-using teams. It'll be the ultimate cheat sheet, and specific to your job. If you think this sounds complicated, it's not! Your fearless leader, Emma Jane, has been successfully teaching people how-to-tech for over a decade. She is well known for her non-technical metaphors which ease learners into complex, work-related topics that previously felt inaccessible.
Yes, this is an introductory session. No, you don't have to have Git installed to attend. You don't even need to know where the command line is on your computer. Yes, you should attend if you've been embarrassed to ask team-mates what Git command you used three weeks ago to upload your work...just in case you're supposed to remember.
If you're a super-human Git fanatic who is frustrated by people who don't just "git it", this session is also for you. You'll learn new ways to effectively communicate your ever-loving Git, and you may develop a deeper understanding of why your previous attempts to explain Git have failed.
Hidden Speed Bumps on the Road to "Continuous"Sonatype
As a companion piece for our '2015 State of the Software Supply Chain Report' this ebook explores the hidden complexities in modern software development by drawing analogies to a traditional supply chain. This is a real eye-opener for anyone who cares about development speed, efficiency and quality.
More Aim, Less Blame: How to use postmortems to turn failures into something ...Daniel Kanchev
Mistakes and failure are inevitable. Instead of being afraid of them, we should use them as lessons that help identify weak points in our organisations and systems. One way to do this is by writing blameless postmortems. Daniel details exactly how postmortems can help organizations and teams focus on improvement, and how that boosts work morale, makes products better, and strengthens your relationship with customers.
Data Science Popup Austin: Privilege and Supervised Machine LearningDomino Data Lab
Watch talk ⇒ http://bit.ly/1SGuwNs
I'll use the example of sentiment analysis to show that supervised machine learning has the potential to amplify the voices of the most privileged people in society. A sentiment analysis algorithm is considered ‘table stakes’ for any serious text analytics platform in social media, finance, or security. As an example of supervised machine learning, I'll show how these systems are trained. But I'll also show that they have the unavoidable property that they are better at spotting unsubtle expressions of extreme emotion. Such crude expressions are used by a particularly privileged group of authors: men. In this way, brands that depend on sentiment analysis to 'learn what people think' inevitably pay more attention to men. The problem doesn't stop with sentiment analysis: at every step of any model building process, we make choices that can introduce bias, enhance privilege, or break the law! I'll review these pitfalls, talk about how you can recognize them in your own work, and touch on some new academic work that aims to mitigate these harms.
The Junior Developer Survival Guide - GDI Ann Arbor 2/10/15James York
Are you new to the professional world of software development? Do you have new developers on your team? Are you wondering why college and the School of Hard Knocks did such a bad job preparing you to be a functional member of a high-performing team? Take some advice from a junior dev who has walked the path and learn to avoid rookie mistakes. Learn the skills employers value and how to get them. We will discuss quick return actions that can be undertaken immediately, as well as long term, slow-burn investments in your career. This session will focus on technical and interpersonal advice to help make your first job search, entry-level hire, and first year as a developer go smoothly. A great career won’t just fall into your lap. It takes dedication, skill, persistence, and more than a little luck. Happily, we make our own luck.
Data Science Popup Austin: Conflict in Growing Data Science Organizations Domino Data Lab
Watch talk ➟ http://bit.ly/1NKPpQh
Eduardo Arino De La Rubia, VP of Product and Data Scientist in residence at Domino Data Lab talks about how to manage conflict in growing data science teams.
What is Shift Left Testing? Do you need to use that term to improve your Software Testing and Development process? I don't think so.
- why I don't use the term Shift Left
- Explanation of what Shift Left means when people use it
- Explanation of what Shift Left might mean when people hear it
- How to Shift Left incorrectly
- How to improve your test process without using the phrase Shift Left.
Hire me for consultancy and buy my online books and training at:
- https://compendiumdev.co.uk
- http://eviltester.com
- http://seleniumsimplified.com
- http://javafortesters.com
Achieving Technical Excellence in Your Software Teams - from Devternity Peter Gfader
Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers.
Great software engineer teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live.
I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions.
Why would a company like to be "agile"?
How can a company achieve that?
How can you achieve Technical Excellence in your software teams?
What developer skills are more important than languages, methods or frameworks?
This will be an interactive session with a Q&A at the end.
Chaos Engineering, When should you release the monkeys?Thoughtworks
Chaos Engineering is listed as 'Trial' in the ThoughtWorks Tech Radar, but what is it really and how is it different from traditional testing? When and why should you get started with Chaos Engineering and is Chaos Monkey the right place to start when you do?
A tour of challenges today's software engineers will fast (and material they should familiarize themselves with) to cope with the issues that arise due to the distributed nature of today's applications.
DOES SFO 2016 - Greg Padak - Default to OpenGene Kim
Large enterprises have hierarchical organizations to define areas of responsibility and drive better accountability. Those structures often block cross-team interactions and knowledge sharing that slow innovation and agility. We will discuss strategies that use open platforms to drive meaningful development outcomes through collaboration and productivity across the enterprise.
Presentation for Harvard's ABCD Technology in Education group:
The Institute for Quantitative Social Science (IQSS) is a unique entity at Harvard - it combines research, software development, and specialized services to provide innovative solutions to research and scholarship problems at Harvard and beyond. I will talk about the software projects that IQSS is currently working on (Dataverse, Zelig, Consilience, and OpenScholar), including the research and development processes, the benefits provided to the Harvard community, and the impacts on research and scholarship.
You are a clever and talented person. You create beautiful designs, or perhaps you can architect a system that even a cat could use. Your peers adore you. Your clients love you. But (until now) you haven't *&^#^ been able to make Git bend to your will. It makes you angry inside that you have to ask your co-worker, again, for that *&^#^ command to share your work.
It's not you. It's Git. Promise.
We'll kick off this session with an explanation of why Git is so freaking hard to learn. Then we'll flip the tables and make YOU (not Git) the centre of attention. You'll learn how to define, and sketch out how version control works, using terms and scenarios that make sense to you. Yup, sketch. On paper. (Tablets and other electronic devices will be allowed, as long as you promise not to get distracted choosing the perfect shade for rage.) To this diagram you'll layer on the common Git commands that are used regularly by efficient Git-using teams. It'll be the ultimate cheat sheet, and specific to your job. If you think this sounds complicated, it's not! Your fearless leader, Emma Jane, has been successfully teaching people how-to-tech for over a decade. She is well known for her non-technical metaphors which ease learners into complex, work-related topics that previously felt inaccessible.
Yes, this is an introductory session. No, you don't have to have Git installed to attend. You don't even need to know where the command line is on your computer. Yes, you should attend if you've been embarrassed to ask team-mates what Git command you used three weeks ago to upload your work...just in case you're supposed to remember.
If you're a super-human Git fanatic who is frustrated by people who don't just "git it", this session is also for you. You'll learn new ways to effectively communicate your ever-loving Git, and you may develop a deeper understanding of why your previous attempts to explain Git have failed.
Hidden Speed Bumps on the Road to "Continuous"Sonatype
As a companion piece for our '2015 State of the Software Supply Chain Report' this ebook explores the hidden complexities in modern software development by drawing analogies to a traditional supply chain. This is a real eye-opener for anyone who cares about development speed, efficiency and quality.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1fjTxvB.
Trisha Gee and Todd Montgomery attack the technology industry’s sacred cows by exposing the motivations that hide behind them. They discuss how these motivations lead us into practices that hinder rather than help us deliver quality software. Also, they discuss why some organisations seem to be achieving things that the traditional corporate IT departments can only dream of. Filmed at qconnewyork.com.
Todd Montgomery is Ex-NASA researcher, Chief Architect at Kaazing. Trisha Gee is Java Champion and Engineer.
Teaching Elephants to Dance (and Fly!): A Developer's Journey to Digital Tran...Burr Sutter
We can be brilliant developers, but we won’t succeed—and won’t lead our organizations to succeed—without a new perspective (if you will) and new assumptions about the components of the “technology ecosystem” that are fundamentally critical to our success. This includes the operators, QA team, DBAs, security folks, and even the pure business contingent—in most cases, each of these individuals and groups plays a critical role in the success of what we create and give birth to as developers. What we do in isolation might be genius, but if we insulate ourselves—especially with arrogance—from these colleagues, neither our code nor our organizations will realize their full potential, and most will fail. The bottom line is that our old ways are no longer viable, and as the elite within our industry, we will be the leaders and heroes who discard old assumptions and adopt a new perspective in this exciting journey to digital transformation—where the impossible can become reality.
Slides from my DevOpsExpo London talk "From oops to NoOps".
They tell you in these conferences that DevOps is not about tools, but about culture. And they are partially right. I am going to tell you that it’s not only about culture or tools but also abstractions.
It is a lot about how you see software and its value. About our mental model of what software is: how it runs, evolves, and interacts with the other facets of an enterprise.
We used to view software as code. As a state of code. Now we think about software as change, as a flow. A dynamic system where people, machines, and processes interact continuously.
At Platform.sh we spend a bunch of time asking ourselves not “How do you build?” - or even “How do you build consistently?” - but rather “What does it mean to consistently build in a world where change is good?” A world that lets you push security fixes into production as soon as they’re available because you don’t want to be an Equifax but you do want stability.
In this presentation, I will go over what we think software is and why having the right ideas about software will help you get your culture right and your tooling aligned, as well as gain in productivity, and general happiness and well-being.
Synergy of Human and Artificial Intelligence in Software EngineeringTao Xie
Keynote Talk by Tao Xie at International NSF sponsored Workshop on Realizing Artificial Intelligence Synergies in Software Engineering (RAISE 2013) http://promisedata.org/raise/2013/
How do you maintain millions of lines of code for a project in the Julia programming language? In this talk we will showcase how the Julia SciML organization grew from being research solvers into an industrial-scale platform which is used throughout many highly regulated industries such as pharmacology and aerospace. How do you develop Julia code that is safe for highly regulated environments? Chris Rackauckas will walk through many of the major tenants of the SciML style of contributions: the pieces which has allowed the list of contributors to grow far beyond what's seen in many of the Python and R developer ecosystems.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
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.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
3. “Dark Matter Developers”
Scott Hanselman (March 2012)
!
[We] hypothesize that there is another kind
of developer than the ones we meet all the
time. We call them Dark Matter Developers.
They don't read a lot of blogs, they never write blogs,
they don't go to user groups, they don't tweet or
facebook, and you don't often see them at large
conferences... [They] aren't chasing the latest beta
or pushing...limits, they are just producing.
!
!
http://www.hanselman.com/blog/DarkMatterDevelopersTheUnseen99.aspx
!3
4. We’re Not That Optimistic
l
90% of hydrologists have their heads down
−
l
l
Doing hydrology instead of talking about using
Charm++ to asynchronously distribute their CUDAaccelerated heterogeneous N-body Universe
simulations
Not because they don't
want to do all that Star
Trek stuff
But because the
majority of the field isn’t
there yet.
!4
8. Surely You're Exaggerating
1. How many graduate students write shell
scripts to analyze each new data set
instead of running those analyses by hand?
!8
9. Surely You're Exaggerating
2. How many of them use version control
to keep track of their work and collaborate
with colleagues?
!9
10. Surely You're Exaggerating
3.
How many routinely break large problems
into pieces small enough to be
- comprehensible,
- testable, and
- reusable?
!10
11. Surely You're Exaggerating
3.
How many routinely break large problems
into pieces small enough to be
- comprehensible,
- testable, and
- reusable?
And how many know those are the
same things?
!11
13. We've Left the Majority Behind
Other than
Googling for things,
the majority of scientists
do not use computers
more effectively today
than they did 28 years ago.
!13
14. “Not My Problem”
Actually your biggest problem
•
•
•
Application Yesterday’s models are solving today’s
million dollar problems, because nobody knows how to
update them.
Collaboration Hundreds of person-years of effort are
redundantly combining to create a year’s worth of result
Credibility Many published results can’t be trusted,
because the scientific code isn’t modular, can’t be
tested, and sometimes isn’t even released
And Hydrology Loses
!14
15. Jeff Hammond
Your code will outlive your
supercomputer. Most
successful supercomputers
lasts 5 years. The most
successful codes may reach 5
decades. There are currently
40 year-old modeling codes
still being used.
Argonne Leadership
Computing Facility
!15
16. Where Are Your Goalposts?
A hydrologist is computationally competent if she
can build, use, validate, and share software to:
•Manage software and data
•Tell if it's working correctly
•Find and fix problems when it isn’t
•Keep track of what she’s done
•Share work with others
•Do all of these things efficiently
!16
17. A Driver's License Exam
l
l
Developed with the Software Sustainability
Institute for the DiRAC Consortium
Formative assessment
−
l
Do you know what you need to know in order to
get the most out of this gear?
Pencils ready?
Note: actual exam allows for several different
programming languages, version control systems, etc.
!17
18. A Driver's License Exam
1.
2.
3.
4.
5.
6.
7.
Check out a working copy of the exam
materials from a git repository.
Could do it easily
Could struggle through
1
0.5
Wouldn’t know where to start
0
Don’t understand the question
-1
!18
19. A Driver's License Exam
1.
2.
3.
4.
5.
6.
7.
Use find and grep in a pipe to create a
list of all .dat files in the working copy,
redirect the output to a file, and add that
file to the repository.
Could do it easily
Could struggle through
1
0.5
Wouldn’t know where to start
0
Don’t understand the question
-1
!19
20. A Driver's License Exam
1.
2.
3.
4.
5.
6.
7.
Write a shell script that runs a legacy
program for each parameter in a set.
Could do it easily
Could struggle through
1
0.5
Wouldn’t know where to start
0
Don’t understand the question
-1
!20
21. A Driver's License Exam
1.
2.
3.
4.
5.
6.
7.
Edit the Makefile provided so that if any
.dat file changes, analyze.py is re-run to
create the corresponding .out file.
Could do it easily
Could struggle through
1
0.5
Wouldn’t know where to start
0
Don’t understand the question
-1
!21
22. A Driver's License Exam
1.
2.
3.
4.
5.
6.
7.
Write four unit tests to exercise a function
that calculates running sums. Explain why
your four tests are most likely to uncover
bugs in the function.
Could do it easily
Could struggle through
1
0.5
Wouldn’t know where to start
0
Don’t understand the question
-1
!22
23. A Driver's License Exam
1.
2.
3.
4.
5.
6.
7.
Explain when and how a function could
pass your tests, but still fail on real data.
Could do it easily
Could struggle through
1
0.5
Wouldn’t know where to start
0
Don’t understand the question
-1
!23
24. A Driver's License Exam
1.
2.
3.
4.
5.
6.
7.
Do a code review of the legacy program
from Q3 (about 50 lines long) and list
the four most important improvements
you would make.
Could do it easily
Could struggle through
1
0.5
Wouldn’t know where to start
0
Don’t understand the question
-1
!24
26. How Are We Doing?
a) How well did you do?
b) How well do you think most hydrologists would
do?
!26
27. How Are We Doing?
a) How well did you do?
b) How well do you think most hydrologists would do?
c) Do you think a hydrologist could use your software
without having these skills?
d) Or a grasp of the principles behind them?
!27
28. What Has Worked
l
Target graduate students
l
Intensive short courses (2 days to 2 weeks)
l
Focus on practical skills
!28
29. What Has Worked
l
Target graduate students
l
Intensive short courses (2 days to 2 weeks)
l
Focus on practical skills
http://software-carpentry.org
!29
31. What We Teach
l
Unix shell
how to automate repetitive tasks
l
Git and GitHub
how to use distributed version control to manage,
collaborate and share work
l
Python or R
how to grow a program in a structured, modular,
testable, reusable way
l
Databases
the difference between structured and unstructured data
!31
33. “That's Merely Useful”
l
None of this is publishable any longer
−
Which means it's ineffective career-wise for
academic computer scientists
!33
34. “That's Merely Useful”
l
None of this is publishable any longer
−
l
Which means it's ineffective career-wise for
academic computer scientists
But it works
−
Two independent assessments have validated the
impact of what we do
!34
36. Teach a Workshop
l
All our materials are CC-BY licensed
l
We will help train you
Text
???
!36
37. Shine Some Light
l
l
Include a few lines about your software stack
and working practices in your scientific papers
Ask about them when reviewing
−
−
−
Where's the repository containing the code?
What's the coverage of your unit tests?
How did you track provenance?
!37
38. Links!
Find this talk on Twitter: @ahmadia
!
Me:
http://aron.ahmadia.net
!
Software Carpentry:
http://software-carpentry.org
!
US Army Engineer Research and
Development Center:
http://www.erdc.usace.army.mil/
!38