Lunch and Learn I did on some general Agile and other practices that can make developers more productive.
Most of the content was in the speech though unfortunately.
(Ignite) OPEN SOURCE - OPEN CHOICE: HOW TO CHOOSE AN OPEN-SOURCE PROJECT, HIL...DevOpsDays Tel Aviv
Choosing the right Open Source project can be challenging, BUT! Asking yourself the right questions can ease the process
In this talk I'm going to talk about the key indicators of how to choose an open-source project for integration in your environment, as well as set the weight for the specific key indicators based on your needs and specific pain points.
How Do We Better Sell DevOps? - PuppetConf 2013Puppet
"How Do We Better Sell DevOps?" by Gene Kim, Author of "The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win", IT Revolution Press.
Presentation Overview: In this talk, Gene shares his top lessons learned over my years studying high performing IT organizations on how to sell the value of DevOps, and help other stakeholders and executives have their own a-ha moments. He talks about specific stories about the circumstances that led to these a-ha moments, how they created DevOps champions in surprising places (e.g., Development, CTOs, Product Management, UX, Infosec) in organizations you'll recognize, and how they enabled implementing DevOps patterns that had awesome results.
Speaker Bio: Gene is a multiple award winning CTO, researcher and author. He was founder and CTO of Tripwire for 13 years. He has written three books, including “The Visible Ops Handbook” and “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win." Gene is a huge fan of IT operations, and how it can enable developers to maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He has worked with some of the top Internet companies on improving deployment flow and increasing the rigor around IT operational processes. In 2007, ComputerWorld added Gene to the “40 Innovative IT People Under The Age Of 40” list.
Ernest Mueller, Karthik Gaekwad, and James Wickett, the Agile Admins (http://theagileadmin.com) delivered this presentation on what's hot in DevOps in 2015 for the BrightTALK Summit. The video is online at https://www.brighttalk.com/webcast/5742/154715
The Development Graveyard: How Software Projects DieErika Barron
Learn the top 5 reasons why software projects fail. The scariest part is that the failure causes are easily avoidable - yet as IT professionals, we continue to make life more difficult than it really needs to be.
(Ignite) OPEN SOURCE - OPEN CHOICE: HOW TO CHOOSE AN OPEN-SOURCE PROJECT, HIL...DevOpsDays Tel Aviv
Choosing the right Open Source project can be challenging, BUT! Asking yourself the right questions can ease the process
In this talk I'm going to talk about the key indicators of how to choose an open-source project for integration in your environment, as well as set the weight for the specific key indicators based on your needs and specific pain points.
How Do We Better Sell DevOps? - PuppetConf 2013Puppet
"How Do We Better Sell DevOps?" by Gene Kim, Author of "The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win", IT Revolution Press.
Presentation Overview: In this talk, Gene shares his top lessons learned over my years studying high performing IT organizations on how to sell the value of DevOps, and help other stakeholders and executives have their own a-ha moments. He talks about specific stories about the circumstances that led to these a-ha moments, how they created DevOps champions in surprising places (e.g., Development, CTOs, Product Management, UX, Infosec) in organizations you'll recognize, and how they enabled implementing DevOps patterns that had awesome results.
Speaker Bio: Gene is a multiple award winning CTO, researcher and author. He was founder and CTO of Tripwire for 13 years. He has written three books, including “The Visible Ops Handbook” and “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win." Gene is a huge fan of IT operations, and how it can enable developers to maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He has worked with some of the top Internet companies on improving deployment flow and increasing the rigor around IT operational processes. In 2007, ComputerWorld added Gene to the “40 Innovative IT People Under The Age Of 40” list.
Ernest Mueller, Karthik Gaekwad, and James Wickett, the Agile Admins (http://theagileadmin.com) delivered this presentation on what's hot in DevOps in 2015 for the BrightTALK Summit. The video is online at https://www.brighttalk.com/webcast/5742/154715
The Development Graveyard: How Software Projects DieErika Barron
Learn the top 5 reasons why software projects fail. The scariest part is that the failure causes are easily avoidable - yet as IT professionals, we continue to make life more difficult than it really needs to be.
YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...DevOpsDays Tel Aviv
From idea to execution, the challenges of publishing an open source project are very similar to initializing a startup when it comes to creating a successful product that people will love and use.
Most open source projects are not “taking-off”, although they are really good! This is because developers (which are usually the creators of open source projects) think that writing the code is the hard part and “neglect” the other parts of publishing a good open source project.
In this talk, I will use my experience as a contributor to open source and product head of a startup, to go beyond writing the code itself and cover the other central aspects of creating an open source project, like MVP, product/market fit, marketing and more.
Github Copilot and tools that help us code better are cool. But I’m lucky if I spend 90 minutes a day writing code. We really need to optimize the hours we spend reviewing code, updating tickets and tracing where our code is deployed. Learn how I save an hour a day streamlining non-coding tasks.
This talk is unique because 99% of developer productivity tools and hacks are about coding faster, better, smarter. And yet the vast majority of our time is spent doing all of this other stuff. After I started focusing on optimizing the 10 hours I spend every day on non-coding tasks, I found I my productivity went up and my frustration at annoying stuff went way down. I cover how to save time by reducing cognitive load and by cutting menial, non-coding tasks that we have to perform 10-50 times every day. For example:
Bug or hotfix comes through and you want to start working on it right away so you create a branch and start fixing. What you don’t do is create a Jira ticket but then later your boss/PM/CSM yells at your due to lack of visibility. I share how I automated ticket creation in Slack by correlating Github to Jira.
You have 20 minutes until your next meeting and you open a pull request and start a review. But you get pulled away half way through and when you come back the next day you forgot everything and have to start over. Huge waste of time. I share an ML job I wrote that tells me how long the review will take so I can pick PRs that fit the amount of time I have.
You build. You ship it. You own it. Great. But after I merge my code I never know where it actually is. Did the CI job fail? Is it release under feature flag? Did it just go GA to everyone? I share a bot I wrote that personally tells me where my code is in the pipeline after it leaves my hands so I can actually take full ownership without spending tons of time figuring out what code is in what release.
Learn Fast, Fail Fast, Deliver Fast: The MOD Squad Way at MetLifeDocker, Inc.
The introduction of Microservices and Containers present challenges to organizations that go beyond implementation and operation. These are inherently disruptive technologies and a risk-averse enterprise can struggle as the business culture adapts to change. At MetLife we tackled change and disruption with a highly focused and nimble innovation team called The ModSquad, that is empowered to push the envelope, break the rules, and challenge established norms. The good news is that it is working!
This talk will dive into the story of our innovation team that rapidly implemented Docker and our first production microservices-based application. We’ll talk about executive support and recognition, empowering people, and encouraging a fail-fast mentality. We’ll explore the boundary conditions that we learned along the way that enhances the success of the team, project, and business. We’ll dig into how we have grown and evolved the team based on both our successes and failures and the pitfalls we would have liked to avoid. Finally, we’ll take a look at what we think will be the future state of the team, and some of the disruptive technologies we may tackle on the horizon.
SecOps Armageddon: A look into the future of security & operationsPhillip Maddux
Presented on November 7, 2018 at Triangle DevOps (https://www.meetup.com/triangle-devops/).
With the continuing evolution of the shift to the cloud and automation, this talk explores what the future might look like for security and operations. Will security and operations be abstracted away, resulting in only developers having jobs?
DevOps and the Importance of Single Source Code Repos Perforce
Companies are increasingly moving to DevOps practices to streamline product development and delivery. In this presentation DevOps author and evangelist Gene Kim will discuss how version control has moved from a development concern to a fundamental practice for everyone in the value stream, especially Operations. He will discuss the importance of the single, shared source code repository in high performing technology organizations.
He will discuss the research he has done over the last 16 years about the top predictors of DevOps performance, and how best to overcome the cultural and workflow friction that can exist between Development teams and Operations.
He will discuss the research he has done over the last 16 years about the top predictors of DevOps performance, and how best to overcome the cultural and workflow friction that can exist between Development teams and Operations."
Rock Stars, Builders, and Janitors: You're Doing it WrongDocker, Inc.
You know these roles: the rock star, who is always rolling out a new demo or installing a new technology in your stack; the builder, who makes it reliable and makes it scale; the janitor, who cleans up all your messes, writes your docs, and tweaks your configs. Grow an engineering team to a certain size, and these roles reveal themselves and cement themselves into your processes.
You come to rely on these roles and the people who fill them. And that’s bad.
Yes, rock stars get the spotlight, while builders toil away in the background, and janitors are forgotten. But it’s not all about glory. Pigeonholing engineers hurts everyone and can slow down your engineering organization in the long run. If you’re only a rock star, you’ll never understand scale or user experience. If you’re only a builder, you’ll never learn to write clean configs or care about future use cases. If you’re only a janitor, you’ll never appreciate change or technical growth. You need to be all three to succeed.
In every development process there is the question, do we invest enough on quality? Do we need to invest more? Every team knows about the dilemma of how many tests is the right amount of tests we should write. Is 80% test coverage is good enough? Maybe 90%? 100%? Should we invest more time in unit testing? Are we wasting too much time on unit-testing? Should we invest time on a faster rollback mechanism?
WIIFM
“Without data, you’re just another person with an opinion” - W. Edwards Deming
SLO Driven Development is a framework that helps the developers focus on impact and balance of every aspect of the dev process. When working currently with SLI, SLA, SLO and error budget you can learn where to invest in the development process.
Let’s talk about the importance of good SLOs and how they can help us improve our day2day
Athletes, Firemen and Doctors train everyday to be the best at their chosen profession. As engineers, we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. In this talk, we'll discuss the need for and the options of creating a game day culture. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior. We'll look at tools like toxiproxy and the simian army for ways to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems.
The left is not wrong, just not right; It's time to shift right!Phillip Maddux
In the last few years of AppSec and DevOps, we've heard the calls to shift left. But how far left can we go, and is it really going to help eliminate exploitable bugs or scale your AppSec program? What if we consider a different direction, shifting right! Can a focus on shifting to the right be more effective in mitigating real-world threats and prioritization? In this presentation, I'll explore these questions and propose concepts that show why shifting right is right!
Implementing DevOps is one of the most important investments a growing Salesforce team can make. An effective DevOps process can greatly reduce release overhead and ensure faster feature and bugfix delivery. But there is no easy solution for Salesforce DevOps: there are a multitude of options out there with varying levels of complexity. Do you buy a third-party solution, or build your own using Salesforce DX and other tools? Technical Architect, Chandler Anderson will share his experience working with various Salesforce DevOps solutions and give some insight on what might work for you.
Painless DevSecOps: Building Security Into Your DevOps PipelineTasktop
When a security vulnerability is found, your team needs to be able to address it quickly without having to check and update multiple systems.
Watch the accompanying video to see how you can
* Automate the creation of defects in HPE Quality Center when vulns are detected by WhiteHat Sentinel
* Improve compliance by providing traceability between vulns and their fixes
* Enable real-time reporting on status of security vulnerabilities
Good project from scratch - from developer's point of viewPaweł Lewtak
Slides for my talk at PHPExperience 2018 in São Paulo.
It's about 10 things I believe are important in order to have a successful long-term IT project.
There are no two SDLC processes that are the same. Every company/project has their own specific SDLC process, however the only thing that most have in common is their bloat. The bloat is most evident in the time-to-market aspect of the project. Other evidence of this bloat is slow QA cycles, implementation of design changes are slow, and deployment of the product is slow also.
Building Robust Applications with Chaos EngineeringPostman
Postman's rich feature set can improve the efficiency of development, and testing and monitoring—but what happens when things start to break in unexpected ways? Together, let's examine how Postman can help our teams proactively uncover fragility, create more robust applications, and improve the resilience of our systems.
YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...DevOpsDays Tel Aviv
From idea to execution, the challenges of publishing an open source project are very similar to initializing a startup when it comes to creating a successful product that people will love and use.
Most open source projects are not “taking-off”, although they are really good! This is because developers (which are usually the creators of open source projects) think that writing the code is the hard part and “neglect” the other parts of publishing a good open source project.
In this talk, I will use my experience as a contributor to open source and product head of a startup, to go beyond writing the code itself and cover the other central aspects of creating an open source project, like MVP, product/market fit, marketing and more.
Github Copilot and tools that help us code better are cool. But I’m lucky if I spend 90 minutes a day writing code. We really need to optimize the hours we spend reviewing code, updating tickets and tracing where our code is deployed. Learn how I save an hour a day streamlining non-coding tasks.
This talk is unique because 99% of developer productivity tools and hacks are about coding faster, better, smarter. And yet the vast majority of our time is spent doing all of this other stuff. After I started focusing on optimizing the 10 hours I spend every day on non-coding tasks, I found I my productivity went up and my frustration at annoying stuff went way down. I cover how to save time by reducing cognitive load and by cutting menial, non-coding tasks that we have to perform 10-50 times every day. For example:
Bug or hotfix comes through and you want to start working on it right away so you create a branch and start fixing. What you don’t do is create a Jira ticket but then later your boss/PM/CSM yells at your due to lack of visibility. I share how I automated ticket creation in Slack by correlating Github to Jira.
You have 20 minutes until your next meeting and you open a pull request and start a review. But you get pulled away half way through and when you come back the next day you forgot everything and have to start over. Huge waste of time. I share an ML job I wrote that tells me how long the review will take so I can pick PRs that fit the amount of time I have.
You build. You ship it. You own it. Great. But after I merge my code I never know where it actually is. Did the CI job fail? Is it release under feature flag? Did it just go GA to everyone? I share a bot I wrote that personally tells me where my code is in the pipeline after it leaves my hands so I can actually take full ownership without spending tons of time figuring out what code is in what release.
Learn Fast, Fail Fast, Deliver Fast: The MOD Squad Way at MetLifeDocker, Inc.
The introduction of Microservices and Containers present challenges to organizations that go beyond implementation and operation. These are inherently disruptive technologies and a risk-averse enterprise can struggle as the business culture adapts to change. At MetLife we tackled change and disruption with a highly focused and nimble innovation team called The ModSquad, that is empowered to push the envelope, break the rules, and challenge established norms. The good news is that it is working!
This talk will dive into the story of our innovation team that rapidly implemented Docker and our first production microservices-based application. We’ll talk about executive support and recognition, empowering people, and encouraging a fail-fast mentality. We’ll explore the boundary conditions that we learned along the way that enhances the success of the team, project, and business. We’ll dig into how we have grown and evolved the team based on both our successes and failures and the pitfalls we would have liked to avoid. Finally, we’ll take a look at what we think will be the future state of the team, and some of the disruptive technologies we may tackle on the horizon.
SecOps Armageddon: A look into the future of security & operationsPhillip Maddux
Presented on November 7, 2018 at Triangle DevOps (https://www.meetup.com/triangle-devops/).
With the continuing evolution of the shift to the cloud and automation, this talk explores what the future might look like for security and operations. Will security and operations be abstracted away, resulting in only developers having jobs?
DevOps and the Importance of Single Source Code Repos Perforce
Companies are increasingly moving to DevOps practices to streamline product development and delivery. In this presentation DevOps author and evangelist Gene Kim will discuss how version control has moved from a development concern to a fundamental practice for everyone in the value stream, especially Operations. He will discuss the importance of the single, shared source code repository in high performing technology organizations.
He will discuss the research he has done over the last 16 years about the top predictors of DevOps performance, and how best to overcome the cultural and workflow friction that can exist between Development teams and Operations.
He will discuss the research he has done over the last 16 years about the top predictors of DevOps performance, and how best to overcome the cultural and workflow friction that can exist between Development teams and Operations."
Rock Stars, Builders, and Janitors: You're Doing it WrongDocker, Inc.
You know these roles: the rock star, who is always rolling out a new demo or installing a new technology in your stack; the builder, who makes it reliable and makes it scale; the janitor, who cleans up all your messes, writes your docs, and tweaks your configs. Grow an engineering team to a certain size, and these roles reveal themselves and cement themselves into your processes.
You come to rely on these roles and the people who fill them. And that’s bad.
Yes, rock stars get the spotlight, while builders toil away in the background, and janitors are forgotten. But it’s not all about glory. Pigeonholing engineers hurts everyone and can slow down your engineering organization in the long run. If you’re only a rock star, you’ll never understand scale or user experience. If you’re only a builder, you’ll never learn to write clean configs or care about future use cases. If you’re only a janitor, you’ll never appreciate change or technical growth. You need to be all three to succeed.
In every development process there is the question, do we invest enough on quality? Do we need to invest more? Every team knows about the dilemma of how many tests is the right amount of tests we should write. Is 80% test coverage is good enough? Maybe 90%? 100%? Should we invest more time in unit testing? Are we wasting too much time on unit-testing? Should we invest time on a faster rollback mechanism?
WIIFM
“Without data, you’re just another person with an opinion” - W. Edwards Deming
SLO Driven Development is a framework that helps the developers focus on impact and balance of every aspect of the dev process. When working currently with SLI, SLA, SLO and error budget you can learn where to invest in the development process.
Let’s talk about the importance of good SLOs and how they can help us improve our day2day
Athletes, Firemen and Doctors train everyday to be the best at their chosen profession. As engineers, we spend much of our time getting stuff to production and making sure our infrastructure doesn’t burn down out right. In this talk, we'll discuss the need for and the options of creating a game day culture. Where we as engineers not only write, maintain and operate our software platforms but actively pursue ways to learn and predict its (non-functional) behavior. We'll look at tools like toxiproxy and the simian army for ways to prepare teams to tweak their testing and monitoring setup and work instructions to quickly observe, react to and resolve problems.
The left is not wrong, just not right; It's time to shift right!Phillip Maddux
In the last few years of AppSec and DevOps, we've heard the calls to shift left. But how far left can we go, and is it really going to help eliminate exploitable bugs or scale your AppSec program? What if we consider a different direction, shifting right! Can a focus on shifting to the right be more effective in mitigating real-world threats and prioritization? In this presentation, I'll explore these questions and propose concepts that show why shifting right is right!
Implementing DevOps is one of the most important investments a growing Salesforce team can make. An effective DevOps process can greatly reduce release overhead and ensure faster feature and bugfix delivery. But there is no easy solution for Salesforce DevOps: there are a multitude of options out there with varying levels of complexity. Do you buy a third-party solution, or build your own using Salesforce DX and other tools? Technical Architect, Chandler Anderson will share his experience working with various Salesforce DevOps solutions and give some insight on what might work for you.
Painless DevSecOps: Building Security Into Your DevOps PipelineTasktop
When a security vulnerability is found, your team needs to be able to address it quickly without having to check and update multiple systems.
Watch the accompanying video to see how you can
* Automate the creation of defects in HPE Quality Center when vulns are detected by WhiteHat Sentinel
* Improve compliance by providing traceability between vulns and their fixes
* Enable real-time reporting on status of security vulnerabilities
Good project from scratch - from developer's point of viewPaweł Lewtak
Slides for my talk at PHPExperience 2018 in São Paulo.
It's about 10 things I believe are important in order to have a successful long-term IT project.
There are no two SDLC processes that are the same. Every company/project has their own specific SDLC process, however the only thing that most have in common is their bloat. The bloat is most evident in the time-to-market aspect of the project. Other evidence of this bloat is slow QA cycles, implementation of design changes are slow, and deployment of the product is slow also.
Building Robust Applications with Chaos EngineeringPostman
Postman's rich feature set can improve the efficiency of development, and testing and monitoring—but what happens when things start to break in unexpected ways? Together, let's examine how Postman can help our teams proactively uncover fragility, create more robust applications, and improve the resilience of our systems.
Don’t Let Process Hold You Back: Best Practices for Cross-Functional Collabor...Tasktop
Creating great software takes many skilled people. There’s business requirements to fulfill, technical requirements to consider, development, testing, packaging, and the release.
While having a single cohesive process is crucial to helping all these teams work together, they’re often working in disparate systems with their own processes and workflows. What’s more, these teams are often spread across different departments, buildings and even time zones.
How can you ensure your teams stay in sync and create better processes that allow individual teams to move fast and be agile, while maintaining effective cross-team collaboration? In this webinar with GitLab, we discuss how establishing a ‘single source of truth’ is critical to functional collaboration, and cover the best practices for:
- Building processes that yield better results
- Keeping cross-functional teams in sync
- Integrating tools for better workflows
- Tips for remote teams
How to Manage the Risk of your Polyglot EnvironmentsDevOps.com
In this webinar, we’ll explore how to navigate the tension between speed and security when it comes to open source languages.
Enterprises are challenged by conflicting interests:
Engineering teams want more time to focus on code quality, but product managers want to ship faster.
Developers want the best tool for the job, but companies resist adding more technology stacks to their growing tech debt.
Retrofitting for security and vulnerabilities after the fact becomes a big blocker for Development and Engineering teams. Enterprises are challenged with resolving new threats and vulnerabilities at the pace at which they crop up. And yet, speed wins over security because faster time-to-market takes a greater priority over fixing vulnerabilities.
Our expert panel will cover how to resolve the tension between speed and security by practices which:
Minimize DevOps overhead from retrofitting programming languages with new versions, dependencies, security patches, etc.
Enable Continuous Builds to keep up with your continuous deployments
Use Build Validation to vet your continuous builds against smoke tests
Presentation about the basics of Agile Methodologies and how they can be applied to Scientific Research. This presentation later evolved into the Agile Research method. June 2008
my understanding of fundamentals of DevOps and how it relates conceptually to Agile, Scrum, Kanban, etc.
SlideShare does not allow uploading a new version of existing presentation. Hence I have to upload the new verson.
Goto https://www.slideshare.net/nitinbhide/devops-understanding-core-concepts for latest version.
Overview of the agile software development. This contents was originally created for my team's internal workshop. It includes basic concept of the agile software development, and introduction of some practices and tools for it.
Critical Capabilities to Shifting Left the Right WaySmartBear
The concept of testing earlier in the SDLC isn't new, but the term "shift left" has reignited its importance. See how shifting left can help you, and how to do it right.
This is the English version of my talk about agile software development practices at Agile Talks seminars in Ankara, Turkey. I tried to focus on the nature of software development and figure out the development practices that let us build software in natural way.
This 1 day, hands-on, workshop will introduce the processes and workflows necessary to manage a Business Intelligence team in a flexible, iterative and agile manner. Through standard agile management methods (Scrum, Kanban and Test-Driven Development), this workshop will provide you with the tools to manage your workflow, BI development, demand management, and customer engagement.
The goal of this workshop is to expose you to different ways of working and give you potential tactics and techniques to improve your BI project delivery.
Similar to Agile Development Practices - Productivity (20)
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
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.
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.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
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.
2. Traditional Big „A‟ Agile
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
3. Traditional Big „A‟ Agile
Agile Modeling
Agile Unified Process (AUP)
Dynamic Systems Development Method (DSDM)
Essential Unified Process (EssUP)
Extreme Programming (XP)
Feature Driven Development (FDD)
Open Unified Process (OpenUP)
Scrum
Velocity tracking
6. Little „a‟ agile
1. Can you react immediately and without
panic if external constraints on your
project change?
2. Do you review your process frequently
and regularly to make sure the answer to
the first question is always yes?
7. How can we do this in
waterfall or constrained
environments?
14. What Git is about
1. Use CVS as an example of what NOT to
do.
2. Support a distributed workflow
3. Strong safeguards against corruption,
PEBKAC or malicious
4. High Performance
Horse: http://www.flickr.com/photos/cristic/265149677/ CC Attribution 2.0 Generic (CC BY 2.0)Bunny: http://squeak.preeminent.org/orgBlog/C244531379/E20051003220643/Media/trojanBunny.jpg Fair Use
http://lostechies.com/wp-content/uploads/2011/03/pablos_solid_ebook.pdfSingle responsibility principlethe notion that an object should have only a single responsibility.Open/closed principlethe notion that “software entities … should be open for extension, but closed for modification”.Liskov substitution principlethe notion that “objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program”. See also design by contract.Interface segregation principlethe notion that “many client specific interfaces are better than one general purpose interface.”Dependency inversion principlethe notion that one should “Depend upon Abstractions. Do not depend upon concretions.”Dependency injection is one method of following this principle.
PIE – Program Intently and ExpressivelyBaby Steps – Don’t try to do the whole thing in once giant leap, cut off small pieces, work on them, test them, rinse, repeat. Keep this cycle tight so you know exactly when/where you messed something up.KISS – Don’t build a space shuttle, a bottle rocket would probably do.YAGNI – THROW AWAY CODE IF ITS COMMENTED OUT OR NOT IN USEDRY – Smack yourself if you copy paste code more than once. Move to method is great here, start with procedural then move to more genericized code.Boy Scout Rule – Leave it cleaner than you found it – renaming variables helps muchoGood Neighbor Rule – Cut your grass, make tests, automate things so you don’t leave a mess for your coworkers.
http://en.wikipedia.org/wiki/Git_(software)
Explain story with flaky VPN.Don’t have to be connected to the server to branch, merge, swap changes with coworkers.http://nvie.com/posts/a-successful-git-branching-model/- creative commons