There are plenty of materials on getting development and operations to work together. More conversations are happening around inclusion of other technology groups, such as DBAs and QA testers, into DevOps processes. That said, DevOps conversations has been largely devoid of talk about BizOps place at the table. The goal for any tech-centric group is not to build and/or architect the best technology, but rather to effectively support business. Yet, many of those groups are either not privy to or don't bother understanding the business goals and overarching effects of the technical decisions made. In this talk I'll discuss key areas and feedback points in every DevOps process fit for inclusion of business units in order to align technology and business goals and make your life easier.
Identifying and fixing issues in new code before deploying it to production is important for every software development cycle. However, relying on traditional testing methods in the age of Internet-scale data driven problems may prove to be incomplete. Identifying and fixing the issues in production quickly is crucial, but it requires insight into usage patterns and trends across the whole architecture and application logic. In this talk I touch on inefficiencies of some of the most common testing methods, provide real world examples of discovering odd edge cases with monitoring and offer recommendations on top-down metric instrumentation to help DevOps organizations with identifying and acting on business-effecting problems.
APIdays Paris 2019 - The (really) long journey to an API Community of Practic...apidays
The (really) long journey to an API Community of Practice in a 125 years old insurance company
Julien Duvanel, Head of API, Integration and Customer Facing at at Vaudoise Assurances
Jérome Freyre, Software Engineer at Vaudoise Assurances
Google has made its biggest algorithm update in years. Called Hummingbird the update was announced at Google's 15th birthday bash. In this presentation we explain how Hummingbird affects search
Lately, I've been having a lot of conversations with conference goers. Most attend numerous conferences, have great hallway discussions and yet are too hesitant to submit a proposal with their story. The reasons vary, but the hesitation (or even fear) to present a topic publicly is pretty common in our industry. Being a fairly new speaker myself, I can relate to a lot of these concerns. Hence the reason for this talk.
This talk covers a few of the more common objections to public speaking, recommendations on how to address them as well as tips for new (and maybe veteran) speakers. Everyone has a story. That story should be heard.
With emergence of DevOps approach to application development, deployment and management developers get more and more involved in day-to-day system operations. Lately, there has been a popular point of view that developers should be included in oncall rotation on equal grounds with sys admins. While I don't fully subscribe to that mentality, there are certain processes that must be implemented by every organization to get developers involved in production operation of the software they built. In this talk I'll walk through different aspects of operational oncall responsibilities and discuss ways in which developers should (and should not) be involved in operation of production systems.
DevOps has been a hot topic in the industry for some time now. A lot of people been talking about it. Some have built business models around DevOps-related tools and themes. There are even conferences and trade shows dedicated to DevOps-oriented things. People have made career around talking about it. In light of all of that, I find it chuckle-worthy that very few people actually know what DevOps is. So instead of trying to create a buzzword-infested definition of DevOps to suit my particular agenda, I’d like to talk about what DevOps is not.
There are a lot of great things about the cloud, but the "destroy and rebuild" philosophy which is really good for building a continuous delivery pipeline, really sucks when applied to troubleshooting production problems. When your application goes haywire, the most valuable engineering skill is not the the ability to bring up a copy of your system or even the knowledge of your technology stack (although it doesn't hurt). It is the skill of understanding and solving problems.
Finding the root cause of the issue and mitigating it with minimal disruption in production is a must-have skill for engineers responsible for managing and maintaining production systems, which nowadays includes ops, dbas and devs alike. In this talk I will discuss the skills required to troubleshoot complex systems, traits that prevent engineers from being successful at troubleshooting and discuss some techniques and tips and trick for troubleshooting complex systems in production.
PHP performance 101: so you need to use a databaseLeon Fayer
Being involved in performance audits on systems of every size, from start-up sites hacked together overnight, to a ginormous applications built by world-recognized brand companies, I’ve seen a lot of interesting (and sometimes very unique) performance issues in every level of the stack: code, architecture, databases (sometimes all of the above). But there are a few particular, very “Performance 101″, issues that (unfortunately) appear in a lot of code bases. In this talk I present the most common database-related performance bottlenecks that can happen in most PHP applications.
Identifying and fixing issues in new code before deploying it to production is important for every software development cycle. However, relying on traditional testing methods in the age of Internet-scale data driven problems may prove to be incomplete. Identifying and fixing the issues in production quickly is crucial, but it requires insight into usage patterns and trends across the whole architecture and application logic. In this talk I touch on inefficiencies of some of the most common testing methods, provide real world examples of discovering odd edge cases with monitoring and offer recommendations on top-down metric instrumentation to help DevOps organizations with identifying and acting on business-effecting problems.
APIdays Paris 2019 - The (really) long journey to an API Community of Practic...apidays
The (really) long journey to an API Community of Practice in a 125 years old insurance company
Julien Duvanel, Head of API, Integration and Customer Facing at at Vaudoise Assurances
Jérome Freyre, Software Engineer at Vaudoise Assurances
Google has made its biggest algorithm update in years. Called Hummingbird the update was announced at Google's 15th birthday bash. In this presentation we explain how Hummingbird affects search
Lately, I've been having a lot of conversations with conference goers. Most attend numerous conferences, have great hallway discussions and yet are too hesitant to submit a proposal with their story. The reasons vary, but the hesitation (or even fear) to present a topic publicly is pretty common in our industry. Being a fairly new speaker myself, I can relate to a lot of these concerns. Hence the reason for this talk.
This talk covers a few of the more common objections to public speaking, recommendations on how to address them as well as tips for new (and maybe veteran) speakers. Everyone has a story. That story should be heard.
With emergence of DevOps approach to application development, deployment and management developers get more and more involved in day-to-day system operations. Lately, there has been a popular point of view that developers should be included in oncall rotation on equal grounds with sys admins. While I don't fully subscribe to that mentality, there are certain processes that must be implemented by every organization to get developers involved in production operation of the software they built. In this talk I'll walk through different aspects of operational oncall responsibilities and discuss ways in which developers should (and should not) be involved in operation of production systems.
DevOps has been a hot topic in the industry for some time now. A lot of people been talking about it. Some have built business models around DevOps-related tools and themes. There are even conferences and trade shows dedicated to DevOps-oriented things. People have made career around talking about it. In light of all of that, I find it chuckle-worthy that very few people actually know what DevOps is. So instead of trying to create a buzzword-infested definition of DevOps to suit my particular agenda, I’d like to talk about what DevOps is not.
There are a lot of great things about the cloud, but the "destroy and rebuild" philosophy which is really good for building a continuous delivery pipeline, really sucks when applied to troubleshooting production problems. When your application goes haywire, the most valuable engineering skill is not the the ability to bring up a copy of your system or even the knowledge of your technology stack (although it doesn't hurt). It is the skill of understanding and solving problems.
Finding the root cause of the issue and mitigating it with minimal disruption in production is a must-have skill for engineers responsible for managing and maintaining production systems, which nowadays includes ops, dbas and devs alike. In this talk I will discuss the skills required to troubleshoot complex systems, traits that prevent engineers from being successful at troubleshooting and discuss some techniques and tips and trick for troubleshooting complex systems in production.
PHP performance 101: so you need to use a databaseLeon Fayer
Being involved in performance audits on systems of every size, from start-up sites hacked together overnight, to a ginormous applications built by world-recognized brand companies, I’ve seen a lot of interesting (and sometimes very unique) performance issues in every level of the stack: code, architecture, databases (sometimes all of the above). But there are a few particular, very “Performance 101″, issues that (unfortunately) appear in a lot of code bases. In this talk I present the most common database-related performance bottlenecks that can happen in most PHP applications.
One of the major risks when implementing a third party service is the reliance on the availability of that third party service. The service that you have no control over. And no matter how large or successful the service that you’re using is – it will go down at one point or another. This talk is intended to give a real-world disaster example of heavy integration with external social network and practical tips to mitigate or avoid similar issues.
Improving DevOps through better monitoringLeon Fayer
Some developers believe that monitoring is a function of operations team. Some operations teams firmly believe that monitoring the systems they maintain is sufficient to run the business successfully. Most of them are wrong. The complexity of today’s applications have gone far and beyond the capabilities of “traditional” system-level monitoring tools and approaches and requires much broader knowledge of business and application as a whole. The goal of DevOps is to connect all aspects of application development and operations, and monitoring provides visibility and troubleshooting tools to accomplish that goal.
This talk is intended to provide real-world examples of common gaps in monitoring approach and explain why holistic instrumentation of business and functionality monitors should be a part of any project scope.
Talk provided at ASQF meetup "Fachgruppentreffen" in Braunschweig, 18th August 2016
In the last decade, the speed of our industry has increased greatly. Agile Development, DevOps and Continuous Delivery are the main drivers for this paradigm shift which has now become widely accepted.
Ten years ago, it was common to only release a couple of new versions a year. Today, there are companies delivering hundreds of software deployments per day. This isn't only true in IT, but also e.g. for Tesla-Automobile, which delivers its software updates a few times a week.
Where does quality happen when we're releasing this often? Is it possible to have proper quality management and is there enough time for testing? How can we reduce what could be weeks of testing to deliver new features to our clients on a daily basis?
Alex is a long-term enthusiast for this topic. Based on his experiences with various products and companies, he'll share his insights into the mystery of "faster testing". The key questions are:
How can we guarantee quality
When do we test?
How do we test?
How often do we test and what don't we test?
and finallyt: Who does the testing?
Together we will discuss our common problems, approaches and best practices.
The API economy is here and it's fueling disruption in many established industries. In response to this. many companies are looking to increase their agility through breaking down legacy monoliths into discrete services focused around specific business capabilities. Whilst this approach has many advantages, there are potential pitfalls awaiting the unwary. The number of integration points between these distributed components is greatly increased. Considering such an architecture, a naïve approach could be to simply continue to apply traditional integration testing techniques as this can lead to spiraling cost of ownership through brittle test suites. What can we do to mitigate this risk while still giving us the confidence that the various services will work cohesively?
In this session we will explore using consumer driven contacts, specifically Pact, to solve this problem and share some lessons learned from the trenches.
Testing The Legacy: Making Existing Applications Testable Without Epic EffortsAlex Leonov
If you have an established product which came about before the widespread use of the unit and system testing, then you know the problem.
The old code cannot be made testable without a significant effort of throwing it away and writing it anew.
What does it mean for the QA? It means endless repetitions of manual test runs. Sounds like fun? Yeah.. Nah!
In this presentation you will find two ways to make legacy applications testable through automation: an easy one, and a good one. The main benefit they provide is a basis for the further refactoring of the application, without damaging it.
Think of it as a Catch-22: you can't make your old app code testable without severely changing it, and you can't be sure that your changes work because you have no tests to verify them.
If you are a QA and you work with older apps and systems doing a lot of manual testing, then this is the topic for you.
This talk was given at ITx 2016 in Wellington, New Zealand, for Testing Professionals Network.
The ability to see details of the service operations in a transparent way is one of the essential parts of being agile.
At the same time, too much detail hides the big picture. It takes increasingly more energy to see one as services spread over different channels, and reaction times are expected to get lower and lower.
But without the big picture steering the organisation is extremely hard. The challenge is to see operations as a whole, and seeing their details at the same time. Without some kind of a structured approach it seems to be a challenging, if not impossible, task.
In this presentation, you will find the ways to deal with the problem: keep and expand agile operations, and maintain a steady overview of the whole at the same time. It has practical advice on dealing with typical problems, and guidelines on customising the ideas to your own environment.
This talk was given at ITx 2016 in Wellington, New Zealand, for IT Service Management Forum.
Being involved in performance audits on systems of every size, from start-up sites hacked together overnight, to a ginormous applications built by world-recognized brand companies, I’ve seen a lot of interesting (and sometimes very unique) performance issues in every level of the stack: code, architecture, databases (sometimes all of the above). But there are a few particular, very “Performance 101″, issues that (unfortunately) appear in a lot of code bases. In this talk I'll present the most common database-related performance bottlenecks that can happen in most applications.
Let's build an Airport – How to estimate large scale projects☕ 🥧 🚲 Martin Gude
Estimating large scale projects always seems like a pain in the ass. In the end it's just a pretty straightforward three step process: gather the information, define the tasks and estimate those tasks. And you're done.
We’re all camping at UX Camp West, so I thought I’d use the metaphor of a tent to share with you my view on the field of User Experience. I will describe the 7 poles of the tent's structure (research, design, evaluation, implementation, business, strategy, and management) and show you some random objects that I found in its corners. It is my goal that afterwards, we can all appreciate the beauty of the big tent, and realise how we contribute to a happy stay.
I spent the morning launching the solutions, in a SofLayer cloud, that I need for multiple upcoming BizOps pilots. I love it! Build once and reuse often. Check out some of the activities and functional roles that are involved in the business transformation projects.
Microservices: Consumer Driven Contracts in PracticeQaiser Mazhar
In an environment with Microservices and multiple consumers of your APIs. Consumer Driven Contracts help facilitate communication and offers a structured way to migrate and evolve your APIs
My talk on Hadoop stack operations engineering at OSPConAlex Chistyakov
My talk on Hadoop stack operations engineering at OSPCon Nov 2015 (http://www.ospcon.ru/event/prakticheskaya-konferentsiya-tekhnologii-bolshikh-dannykh_130.html)
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
One of the major risks when implementing a third party service is the reliance on the availability of that third party service. The service that you have no control over. And no matter how large or successful the service that you’re using is – it will go down at one point or another. This talk is intended to give a real-world disaster example of heavy integration with external social network and practical tips to mitigate or avoid similar issues.
Improving DevOps through better monitoringLeon Fayer
Some developers believe that monitoring is a function of operations team. Some operations teams firmly believe that monitoring the systems they maintain is sufficient to run the business successfully. Most of them are wrong. The complexity of today’s applications have gone far and beyond the capabilities of “traditional” system-level monitoring tools and approaches and requires much broader knowledge of business and application as a whole. The goal of DevOps is to connect all aspects of application development and operations, and monitoring provides visibility and troubleshooting tools to accomplish that goal.
This talk is intended to provide real-world examples of common gaps in monitoring approach and explain why holistic instrumentation of business and functionality monitors should be a part of any project scope.
Talk provided at ASQF meetup "Fachgruppentreffen" in Braunschweig, 18th August 2016
In the last decade, the speed of our industry has increased greatly. Agile Development, DevOps and Continuous Delivery are the main drivers for this paradigm shift which has now become widely accepted.
Ten years ago, it was common to only release a couple of new versions a year. Today, there are companies delivering hundreds of software deployments per day. This isn't only true in IT, but also e.g. for Tesla-Automobile, which delivers its software updates a few times a week.
Where does quality happen when we're releasing this often? Is it possible to have proper quality management and is there enough time for testing? How can we reduce what could be weeks of testing to deliver new features to our clients on a daily basis?
Alex is a long-term enthusiast for this topic. Based on his experiences with various products and companies, he'll share his insights into the mystery of "faster testing". The key questions are:
How can we guarantee quality
When do we test?
How do we test?
How often do we test and what don't we test?
and finallyt: Who does the testing?
Together we will discuss our common problems, approaches and best practices.
The API economy is here and it's fueling disruption in many established industries. In response to this. many companies are looking to increase their agility through breaking down legacy monoliths into discrete services focused around specific business capabilities. Whilst this approach has many advantages, there are potential pitfalls awaiting the unwary. The number of integration points between these distributed components is greatly increased. Considering such an architecture, a naïve approach could be to simply continue to apply traditional integration testing techniques as this can lead to spiraling cost of ownership through brittle test suites. What can we do to mitigate this risk while still giving us the confidence that the various services will work cohesively?
In this session we will explore using consumer driven contacts, specifically Pact, to solve this problem and share some lessons learned from the trenches.
Testing The Legacy: Making Existing Applications Testable Without Epic EffortsAlex Leonov
If you have an established product which came about before the widespread use of the unit and system testing, then you know the problem.
The old code cannot be made testable without a significant effort of throwing it away and writing it anew.
What does it mean for the QA? It means endless repetitions of manual test runs. Sounds like fun? Yeah.. Nah!
In this presentation you will find two ways to make legacy applications testable through automation: an easy one, and a good one. The main benefit they provide is a basis for the further refactoring of the application, without damaging it.
Think of it as a Catch-22: you can't make your old app code testable without severely changing it, and you can't be sure that your changes work because you have no tests to verify them.
If you are a QA and you work with older apps and systems doing a lot of manual testing, then this is the topic for you.
This talk was given at ITx 2016 in Wellington, New Zealand, for Testing Professionals Network.
The ability to see details of the service operations in a transparent way is one of the essential parts of being agile.
At the same time, too much detail hides the big picture. It takes increasingly more energy to see one as services spread over different channels, and reaction times are expected to get lower and lower.
But without the big picture steering the organisation is extremely hard. The challenge is to see operations as a whole, and seeing their details at the same time. Without some kind of a structured approach it seems to be a challenging, if not impossible, task.
In this presentation, you will find the ways to deal with the problem: keep and expand agile operations, and maintain a steady overview of the whole at the same time. It has practical advice on dealing with typical problems, and guidelines on customising the ideas to your own environment.
This talk was given at ITx 2016 in Wellington, New Zealand, for IT Service Management Forum.
Being involved in performance audits on systems of every size, from start-up sites hacked together overnight, to a ginormous applications built by world-recognized brand companies, I’ve seen a lot of interesting (and sometimes very unique) performance issues in every level of the stack: code, architecture, databases (sometimes all of the above). But there are a few particular, very “Performance 101″, issues that (unfortunately) appear in a lot of code bases. In this talk I'll present the most common database-related performance bottlenecks that can happen in most applications.
Let's build an Airport – How to estimate large scale projects☕ 🥧 🚲 Martin Gude
Estimating large scale projects always seems like a pain in the ass. In the end it's just a pretty straightforward three step process: gather the information, define the tasks and estimate those tasks. And you're done.
We’re all camping at UX Camp West, so I thought I’d use the metaphor of a tent to share with you my view on the field of User Experience. I will describe the 7 poles of the tent's structure (research, design, evaluation, implementation, business, strategy, and management) and show you some random objects that I found in its corners. It is my goal that afterwards, we can all appreciate the beauty of the big tent, and realise how we contribute to a happy stay.
I spent the morning launching the solutions, in a SofLayer cloud, that I need for multiple upcoming BizOps pilots. I love it! Build once and reuse often. Check out some of the activities and functional roles that are involved in the business transformation projects.
Microservices: Consumer Driven Contracts in PracticeQaiser Mazhar
In an environment with Microservices and multiple consumers of your APIs. Consumer Driven Contracts help facilitate communication and offers a structured way to migrate and evolve your APIs
My talk on Hadoop stack operations engineering at OSPConAlex Chistyakov
My talk on Hadoop stack operations engineering at OSPCon Nov 2015 (http://www.ospcon.ru/event/prakticheskaya-konferentsiya-tekhnologii-bolshikh-dannykh_130.html)
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
You asked for it! We build a new, complete template based on top of the success of our free template. The bundle consists of Powerpoint & Keynote versions with three different color themes (classic, red, blue) with master slides included.
You will find all the details here: www.pitchdeck.improvepresentation.com
Professional and Clean PowerPoint slides. Fully editable, perfect to impress your audience on your next presentation.
1. FULL HD Aspect Ratio: 16:9 (1900×1080)
2. Fully animated
3. Quickly, Easy and Fully Editable in PowerPoint (All Graphic Resizable and Editable)
4. Drag and Drop Images
5. Print Version Included (A4 Handouts Ready)
6. Retina Ready
7. Data charts (Editable via Excel)
8. Sync in SharePoint
9. Based on Master Slide
10. Pictures Placeholder Ready
11. PPTX and PPT Files
12. Vector icons as Shape
Note: Not need Photoshop – All Photos not included
This is the digital Marketing A-Z info Slide. If you want to more ditiles you visit our YouTube Channel "onlineliveclassbd"
This channel is very helpful for your computer basic and advances course as digital marketing
Desktouch
(الطلب العرض والمرونة (عينة
هذا التصميم للمعاينه فقط، للطلب يُمكن مراسلتي من خلال موقع خمسات أو احدى مواقع التواصل الإجتماعي.
- https://www.about.me/islam.reda
- https://khamsat.com/user/eslam_reda
Professional and Clean PowerPoint slides. Fully editable, perfect to impress your audience on your next presentation.
1. FULL HD Aspect Ratio: 16:9 (1900×1080)
2. Fully animated
3. Quickly, Easy and Fully Editable in PowerPoint (All Graphic Resizable and Editable)
4. Drag and Drop Images
5. Print Version Included (A4 Handouts Ready)
6. Retina Ready
7. Data charts (Editable via Excel)
8. Sync in SharePoint
9. Based on Master Slide
10. Pictures Placeholder Ready
11. PPTX and PPT Files
12. Vector icons as Shape
Note: Not need Photoshop – All Photos not included
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
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/
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
3. @papa_fire
me
+87%
+68%
+50%
+34%
C Y N I C
D E V
L O S T
B I Z
Leon Fayer
• 20+ years in tech
• dev->manager->biz->dev
• engineer first
• currently @OmniTI
• build and operate large systems
7. @papa_fire
How people define
BizOps
Business Operations (BizOps) is revolutionizing how modern companies function, by
pulling together key business metrics from across departments to optimize business
functions and decision making.
— https://www.youtube.com/watch?v=MFrHJ3cFQuY
BizOps is a decision-support mechanism that helps with everything from optimizing
day-to-day options to carrying out high-priority initiatives to tackling the most
important strategic questions.
— https://www.linkedin.com/pulse/why-bizops-hottest-team-tech-dan-yoo
BizOps teams are generally an internal-facing group and broadly aim to create more
value for the company and to improve the profitability of the business
— https://medium.com/business-startup-development-and-more/why-your-startup-
also-needs-a-bizops-team-5d2e7d436a0#.h2kaemgq3
28. @papa_fire
Congratulations [FIRSTNAME]!
Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Aliquam et iaculis libero,
quis varius ligula. Vivamus a nibh
consequat, efficitur massa id, sollicitudin
ante.
Vivamus mattis magna libero, non
pulvinar quam blandit at.
Phasellus eget ornare ipsum.
Nullam vehicula fringilla diam, at semper
nisi. Duis non ullamcorper justo, sit amet
congue metus.
Sed vehicula egestas euismod.
WOW!
29. @papa_fire
Congratulations [FIRSTNAME]!
Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Aliquam et iaculis libero,
quis varius ligula. Vivamus a nibh
consequat, efficitur massa id, sollicitudin
ante.
Vivamus mattis magna libero, non
pulvinar quam blandit at.
Phasellus eget ornare ipsum.
Nullam vehicula fringilla diam, at semper
nisi. Duis non ullamcorper justo, sit amet
congue metus.
Sed vehicula egestas euismod.
WOW!
Congratulations [FIRSTNAME]!
Lorem ipsum dolor sit amet, consectetur
adipiscing elit.Aliquam et iaculis libero,
quis varius ligula. Vivamus a nibh
consequat, efficitur massa id, sollicitudin
ante.
Vivamus mattis magna libero, non
pulvinar quam blandit at.
Phasellus eget ornare ipsum.
Nullam vehicula fringilla diam, at semper
nisi. Duis non ullamcorper justo, sit amet
congue metus.
Sed vehicula egestas euismod.
WOW!
31. @papa_fire
Congratulations [FIRSTNAME]!
Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Aliquam et iaculis libero,
quis varius ligula. Vivamus a nibh
consequat, efficitur massa id, sollicitudin
ante.
Vivamus mattis magna libero, non
pulvinar quam blandit at.
Phasellus eget ornare ipsum.
Nullam vehicula fringilla diam, at semper
nisi. Duis non ullamcorper justo, sit amet
congue metus.
Sed vehicula egestas euismod.
WOW!
Congratulations [FIRSTNAME]!
Lorem ipsum dolor sit amet, consectetur
adipiscing elit.Aliquam et iaculis libero,
quis varius ligula. Vivamus a nibh
consequat, efficitur massa id, sollicitudin
ante.
Vivamus mattis magna libero, non
pulvinar quam blandit at.
Phasellus eget ornare ipsum.
Nullam vehicula fringilla diam, at semper
nisi. Duis non ullamcorper justo, sit amet
congue metus.
Sed vehicula egestas euismod.
WOW!
3%
+ revenue
32. @papa_fire
Congratulations [FIRSTNAME]!
Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Aliquam et iaculis libero,
quis varius ligula. Vivamus a nibh
consequat, efficitur massa id, sollicitudin
ante.
Vivamus mattis magna libero, non
pulvinar quam blandit at.
Phasellus eget ornare ipsum.
Nullam vehicula fringilla diam, at semper
nisi. Duis non ullamcorper justo, sit amet
congue metus.
Sed vehicula egestas euismod.
WOW!
Congratulations [FIRSTNAME]!
Lorem ipsum dolor sit amet, consectetur
adipiscing elit.Aliquam et iaculis libero,
quis varius ligula. Vivamus a nibh
consequat, efficitur massa id, sollicitudin
ante.
Vivamus mattis magna libero, non
pulvinar quam blandit at.
Phasellus eget ornare ipsum.
Nullam vehicula fringilla diam, at semper
nisi. Duis non ullamcorper justo, sit amet
congue metus.
Sed vehicula egestas euismod.
WOW!
3%
2.6%
+ revenue