Pipelines to production
•
0 likes•165 views
This document discusses problems in development and operations that DevOps aims to solve, including inflexible practices, slow systems, faulty recovery processes, and lack of control. It presents DevOps approaches like empowering autonomous teams, automating repetitive tasks, continuously integrating and deploying changes, implementing version control, monitoring production, and promoting collaboration between development and operations. The key message is that DevOps success depends on open communication and understanding between teams.
Report
Share
Report
Share
Download to read offline
Recommended
Ixda slides
This document summarizes Lucas Colusso's presentation on behavior change design sprints. It discusses how the sprints incorporate behavior change theories into the design process. The sprints follow a 6 step process: 1) translating scenarios into user journeys, 2) selecting behavior change strategies, 3) generating design hypotheses, 4) brainstorming applications of strategies, 5) finding inspiring sketches, and 6) prototyping and advocacy. The sprints aim to help designers and students apply behavior theories to encourage behaviors like using public transit or reading diverse news articles. Over 10 sprints were conducted with 42 participants in total.
Drupal Product Development
Core Developer Lighting Talk for DrupalCon San Francsisco by Doug Green
douggreen, http://drupal.org/user/29191
I've been involved with Drupal for about 4 years. I've presented something at every DrupalCon I've been to (but won't at SF2010).
I wrote coder, lots of search engine work including d6 core improvements, the new d7 search hooks, views_fastsearch, and dozens of other modules I no longer maintain
I worked for CivicActions for 3 years.
I've work for NowPublic.com, Examiner.com since last October.
Conversion Rate Optimization Takeaways - Behave2016 Conference
This is a presentation of takeaways about conversion rate optimization from Behave2016 Conference in Austin TX.
Requirements are Boring, and other Myths (EclipseCon 2013 Lightning talk)
The document discusses requirements and how to write them effectively. It recommends understanding why requirements matter, measuring whether they are realized, and trying to automate requirements as much as possible through modeling. It provides tips for writing good requirements, such as keeping them simple, defining their scope clearly, quantifying objectives when feasible, and ensuring they are complete, clear, and avoid contradictions. Automating requirements through modeling and formal specification can help realize, refine, justify, and test requirements throughout the development process.
Discussion Board RubricParticipation is measured by posting an i
This document outlines a rubric for grading student participation in online class discussions. Students are expected to make an initial post by Sunday and at least two response posts. Initial posts should be a minimum of 7 sentences and connect to course content. Response posts should be a minimum of 5 sentences and extend the discussion. Timely posts that allow others to respond receive more points. Grammar, spelling, relevance, and length also factor into scoring. Postings are graded on a scale from A to F.
Radical Quality From Toyota to Tech
Where defects in the industry are counted as defects per million parts produced, a developer introduces an average of 70 bugs for every 1000 lines of code produced. We immersed ourselves in the experiments of Sadao Nomura, who launched Dantotsu "Better than the best" activities in Toyota factories, a 3-year program capable of reducing defects by 85%.
The tech practices, visual management, and tools of Dantotsu inspired us to:
- Eradicate the root causes of a bug within 24 hours of its detection
- Identify "weak points", typical problems that require strengthening the training system
- Create a culture of quality where everyone shares their solved bugs
We cover the theory of Dantotsu radical quality and the experiments we ran before October 2022.
Woody is the CTO and co-founder of Sipios, a fintech development agency. Flavian is a co-author of Build To Sell, CTO, and lean coach.
Retrospectives er spild af tid!
This document discusses how retrospectives in agile development teams can be improved using concepts from the Toyota Production System called Toyota Kata. It argues that traditional retrospectives often result in many planned actions that are not executed or followed up on. The document recommends that teams adopt the Toyota Kata approach of establishing a process vision, understanding the current condition, setting target conditions, and experimenting through short cycles towards the target condition. This changes the role of the Scrum Master from a facilitator to a leader driving process improvement through goal-focused experiments rather than problem-focused actions.
Dealing with Estimation, Uncertainty, Risk, and Commitment
Software projects are known to have challenges with estimation, uncertainty, risk, and commitment—and the most valuable projects often carry the most risk. Other industries also encounter risk and generate value by understanding and managing that risk effectively. Todd Little explores techniques used in a number of risky businesses—product development, oil and gas exploration, investment banking, medicine, weather forecasting, and gambling—and shares what those industries have done to manage uncertainty. With studies of software development estimations and uncertainties, Todd discusses how software practitioners can learn from a better understanding of uncertainty and its dynamics. In addition, he introduces techniques and approaches to estimation and risk management including utilizing real options and one of its key elements—understanding commitment. Take away a better understanding of the challenges of estimation and what software practitioners can do to better manage estimation, risks, and their commitments.
Recommended
Ixda slides
This document summarizes Lucas Colusso's presentation on behavior change design sprints. It discusses how the sprints incorporate behavior change theories into the design process. The sprints follow a 6 step process: 1) translating scenarios into user journeys, 2) selecting behavior change strategies, 3) generating design hypotheses, 4) brainstorming applications of strategies, 5) finding inspiring sketches, and 6) prototyping and advocacy. The sprints aim to help designers and students apply behavior theories to encourage behaviors like using public transit or reading diverse news articles. Over 10 sprints were conducted with 42 participants in total.
Drupal Product Development
Core Developer Lighting Talk for DrupalCon San Francsisco by Doug Green
douggreen, http://drupal.org/user/29191
I've been involved with Drupal for about 4 years. I've presented something at every DrupalCon I've been to (but won't at SF2010).
I wrote coder, lots of search engine work including d6 core improvements, the new d7 search hooks, views_fastsearch, and dozens of other modules I no longer maintain
I worked for CivicActions for 3 years.
I've work for NowPublic.com, Examiner.com since last October.
Conversion Rate Optimization Takeaways - Behave2016 Conference
This is a presentation of takeaways about conversion rate optimization from Behave2016 Conference in Austin TX.
Requirements are Boring, and other Myths (EclipseCon 2013 Lightning talk)
The document discusses requirements and how to write them effectively. It recommends understanding why requirements matter, measuring whether they are realized, and trying to automate requirements as much as possible through modeling. It provides tips for writing good requirements, such as keeping them simple, defining their scope clearly, quantifying objectives when feasible, and ensuring they are complete, clear, and avoid contradictions. Automating requirements through modeling and formal specification can help realize, refine, justify, and test requirements throughout the development process.
Discussion Board RubricParticipation is measured by posting an i
This document outlines a rubric for grading student participation in online class discussions. Students are expected to make an initial post by Sunday and at least two response posts. Initial posts should be a minimum of 7 sentences and connect to course content. Response posts should be a minimum of 5 sentences and extend the discussion. Timely posts that allow others to respond receive more points. Grammar, spelling, relevance, and length also factor into scoring. Postings are graded on a scale from A to F.
Radical Quality From Toyota to Tech
Where defects in the industry are counted as defects per million parts produced, a developer introduces an average of 70 bugs for every 1000 lines of code produced. We immersed ourselves in the experiments of Sadao Nomura, who launched Dantotsu "Better than the best" activities in Toyota factories, a 3-year program capable of reducing defects by 85%.
The tech practices, visual management, and tools of Dantotsu inspired us to:
- Eradicate the root causes of a bug within 24 hours of its detection
- Identify "weak points", typical problems that require strengthening the training system
- Create a culture of quality where everyone shares their solved bugs
We cover the theory of Dantotsu radical quality and the experiments we ran before October 2022.
Woody is the CTO and co-founder of Sipios, a fintech development agency. Flavian is a co-author of Build To Sell, CTO, and lean coach.
Retrospectives er spild af tid!
This document discusses how retrospectives in agile development teams can be improved using concepts from the Toyota Production System called Toyota Kata. It argues that traditional retrospectives often result in many planned actions that are not executed or followed up on. The document recommends that teams adopt the Toyota Kata approach of establishing a process vision, understanding the current condition, setting target conditions, and experimenting through short cycles towards the target condition. This changes the role of the Scrum Master from a facilitator to a leader driving process improvement through goal-focused experiments rather than problem-focused actions.
Dealing with Estimation, Uncertainty, Risk, and Commitment
Software projects are known to have challenges with estimation, uncertainty, risk, and commitment—and the most valuable projects often carry the most risk. Other industries also encounter risk and generate value by understanding and managing that risk effectively. Todd Little explores techniques used in a number of risky businesses—product development, oil and gas exploration, investment banking, medicine, weather forecasting, and gambling—and shares what those industries have done to manage uncertainty. With studies of software development estimations and uncertainties, Todd discusses how software practitioners can learn from a better understanding of uncertainty and its dynamics. In addition, he introduces techniques and approaches to estimation and risk management including utilizing real options and one of its key elements—understanding commitment. Take away a better understanding of the challenges of estimation and what software practitioners can do to better manage estimation, risks, and their commitments.
Android design lecture #1
This document summarizes an Android design course presented by Yonatan Levin. It discusses:
1. The history and goals of the course, which aims to teach designers and developers how to better integrate and communicate through hands-on lessons and a hackathon.
2. Logistics of the course including its schedule over multiple sessions and expectations for watching online videos between lessons.
3. Key technical concepts in Android design like using density-independent pixels (dp) to account for different screen densities, providing multiple versions of assets, and naming conventions.
Constantly Contributing Pretty Patches FLCD
Many times we developers have come across the perfect contributed module, with a section of code that just doesn't do it for us. Since the Drupal infrastructure is Open to all, it is simpler to take that awesome-ish module and make the changes we need to make it full on awesome. Then we need to take those changes and apply it back to the module and let the whole world bask in the awesome, but we don't get to commit, to Git. (Rule of threes). Therefore we need to create a patch that allows the maintainer of the module to easily combine your great code with theirs. In this session we'll go over the acceptable ways to clone a projects repository, create a great looking patch and contribute said greatness back to the project. Thus, adding to the great chain of life. Oh, was it mentioned that this will work with Drupal Core as well? It should have been.
From four to forty in four years - lessons from growing a team
Between 2016 and 2020, the PureGym IT Team grew from 4 to 40 people. During that time Rich worked closely with them to navigate the tricky process of scaling. This talk is a journey through that growth period and discusses the variety of processes and practices that were applied in order to stay "Agile".
We'll touch on the various approaches taken including topics such as Scrum, Lean, Kanban, GIST planning, Lean Startup, DevOps, IaC, Azure, Story Mapping, BDD, TDD, Project vs Product and we'll be looking at the successes, failures and lessons learned.
We'll also look at how concepts from Team Topologies were applied, what team structures and interaction models were chosen and how that shifted the team dynamic. We will discuss what, in Rich's opinion, has worked well and what hasn't worked well during that time.
At very least you will walk away from this session with a long list of books to read and hopefully some insights into whether you might want to try some of the approaches discussed during the talk.
REAL Eval 6
The student learned several skills from collaboratively constructing a blog and film project. They used a blog to post updates and receive feedback, and learned how to design and format a blog. SurveyMonkey was used to collect feedback, and YouTube and social media helped share work. Skills learned included uploading videos to YouTube, inserting screenshots, and using a microphone, camera, tripod, and lighting rig for filming. Editing software taught continuity editing, split screens, adjusting volume and fades, adding text, rendering, and shortcuts to improve efficiency. Feedback helped improve lighting, effects, and overall production quality.
How HipChat Ships and Recovers Fast with DevOps Practices
HipChat operates a ‘You Build It, You Run It’ service model, where developers are responsible for building, testing, and operating their systems. While we have a high speed of development, things can break – but we also recover quickly. Learn about how we've integrated best practices within our planning, building, operating and learning processes to optimize for speed and efficiency but also mitigate, prepare for, and handle incidents.
The presenter will walk you through four steps for how to operate at a high speed of development and also prepare for any incident — planning, prevention, preparation and collecting feedback— and instruct you on how you can build these processes into your Atlasssian workflow (including JIRA Software, HipChat, Bitbucket, Confluence, Bamboo, and StatusPage).
Learn about:
- Planning: How we use JIRA Software and Confluence to plan roadmaps and sync up with teams
- Prevention: Best practices during code reviews and testing
- Preparation: How we prepare for incidents with war games
Review: Collecting feedback, assessing incident causes and improving our processes
Come out of this session with a newfound understanding of how to use Atlassian products within your DevOps workflow!
Mickie Betz, Software Developer, Atlassian
Optimizing developer onboarding
The document discusses optimizing developer onboarding by focusing on three key questions: how easy it is for developers to understand a product, how quickly developers can get started using a product, and how easy it is for developers to find references and examples. It provides examples from Netlify, Twilio, GitHub, and other companies that effectively address these questions through approaches like descriptive messaging, fast deployment templates, and embedded documentation with live examples.
Visual Studio Mobile Center: A story about mobile DevOps
This story summarizes the journey of a mobile app development team implementing DevOps practices to continuously improve their app quality and release process. The team faced issues with outdated test builds, poor app ratings, and a manual release process. They started using Visual Studio Team Services (VSTS) to automate builds, implement branching for quality, add crash analytics and usage tracking, and configure a release pipeline for staged rollouts. This helped improve app quality through testing, get feedback from users, and release new versions more reliably and frequently. While VSTS was missing some features like store deployments and secret management, it helped the team establish better DevOps practices for continuous delivery.
Being a Little Agile
The document discusses Agile Scrum methodology and how it was used to develop PanoPla, a virtual reality tool. It describes the Scrum process which involves daily stand-ups, bi-weekly deliverables, and retrospectives. A team including students and a Scrum Master from Bit Space Development iteratively built PanoPla over several months, gaining early feedback from users. The result was an open beta version of PanoPla with over 5,000 users in just 4 months.
ContentsTeam Work Schedule3Team Task Assignment3Project .docx
Contents
Team Work Schedule 3
Team Task Assignment 3
Project Plan 4
Step 1: Define the Problem 4
Step 2: Create a Plan 4
Step 3: Execute 4
Step 4: Check Work 6
Step 5: Learn and Generalize 6
House of Quality (HOQ) for Theia’s Smart Glasses 7
Step 1: Define the Problem 7
Step 2: Create a Plan 7
Step 3: Execute 8
Step 4: Check Work 14
Step 5: Learn and Generalize 14
Aggregate Project Plan 15
Step 1: Define the Problem 15
Step 2: Create a Plan 15
Step 3: Execute 16
Step 4: Check Work 22
Step 5: Learn and Generalize 22
I was able to use the APP skills from the midterm and apply it to our actual project. We learned that project #2 yields the highest EMV so that will be the industry we will be focusing on. 22
Theia’s Conceptual Design Process 23
Step 1: Define the Problem 23
Step 2: Create a Plan 23
Step 3: Execute 24
Concept 1 27
Concept 2 28
Concept 3 29
Concept 4 30
Concept 5 31
Concept 6 32
Step 4: Check Work 34
Step 5: Learn and Generalize 34
Phase Ⅱ Reportca 36
Step 1: Define the Problem 36
Step 2: Create a Plan 36
Step 3: Execute 36
Project Planning 36
House of Quality 37
Aggregate Project Plan 37
Reverse Engineering (includes FAST analysis + diagram) 38
Conceptual Design 38
Step 4: Check Work 38
Step 5: Learn and Generalize 39
Team Work Schedule
Date
Task
10/24
Homework assigned, touch bases with team to decide weekend plans.
10/25
Read handout and HOQ example. Everyone assigned to do individual research about AR Glasses.
10/26
Read handout and HOQ example. Everyone assigned to do individual research about AR Glasses.
10/27
Meet at a cafe downtown, due to the power outage. Meeting time is 1 hour.
10/28
Everyone working remotely. Also everyone is working on Phase I/II at the moment. HOQ problem is postponed for a while as we are working on Phase I/II.
10/29
Meet at TBD. Meeting time is 1 hour.
10/30
Revise our work.
10/31
Final revisions. Turn in homework.
Team Task Assignment
Task
Phase 1 - Missing Info + Tech Strategy
Phase 1 - Missing Functional Maps
Project Planning
House of Quality for Product
Aggregate Project Plan
Reverse Engineering
Conceptual Design
Phase II ReportProject PlanStep 1: Define the Problem
We need to clearly determine the tasks required of this project and develop a systematic plan of action to tackle these tasks.Step 2: Create a Plan
Framework for Project Planning:
1. Clearly state the intent of the Project
2. Determine the Design/Development sub-tasks and activities Comment by Christopher Chiang: Develop OS
Develop Display technology
Develop glasses framework
Audio Output
Develop Bluetooth compatibility
Battery development
Charge development
Environment sensing capability
3. Create a design/development activity matrix
4. Create a schedule for each subtask using a GANTT Chart
5. Identify the Critical Path for the Project
6. Assign Clear Roles and Responsibilities & track progressStep 3: Execute
1. Clearly state the intent of the Project
a. Develop smart glasses wearable technology prototype within a 1 year timesp.
video marketing cheat sheet
This document discusses the benefits of using video marketing and provides tips for creating videos. Some key benefits outlined are that video builds trust and makes you more relatable without requiring much time. It also helps increase search engine optimization and visibility across devices. Guidelines are provided for both creating videos using cameras or screen recording software, as well as tips for editing, uploading, optimizing, and sharing videos.
Designer vs Developer (Barcamp Memphis 2009)
The document discusses the relationship between designers and developers, highlighting potential points of conflict and providing advice for effective collaboration. It acknowledges that designers and developers may see things differently and offers tips for open communication, trust-building, compromise, and keeping the end user's needs as the top priority. Working together effectively requires understanding different perspectives, finding solutions, and having each other's backs.
Tour of Mobile usability testing apps and services
Ok, you have been asked to go off and research how to design/architect a mobile user experience. After the initial excitement and learning all about mobile UX, you decide to jump head-on and start designing.
Then comes the realization, how are you going to test the designs in context of a mobile device? Do you have to package everything in an app or is there a way to test preliminary designs? What tools are available? Which works for what Mobile OS? When to use a particular tool? Can, we, designers use it without developer help?
In this presentation I have various testing app/methods/tools/services available specifically for Mobile, for which OS, when to best use them during design process, cost associated with some of the tools, and what are pros & cons of each of them.
Pair Programming, TDD and other impractical things
"Why should we write our tests first? Isn't that going to slow my development?" "What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!" "Look, in the perfect world your advises are great, but I have a project to finish here." In this talk Marcello explores efficiency in contrast to effectiveness. He looks into how practices, traditionally accepted as efficient, sometimes turn out to be less effective than a few "impractical" things he has come across.
Producing Effective Screencasts
Sharing the content of your screen has become a standard for both prerecorded and live video. Whether you’re teaching software, giving a slide presentation, or hosting a business meeting this is a great technique. Rich Harrington has been producing screencasts for 20 years and clients including Apple, Adobe, Microsoft, Skylum, and many more.
In this course, he offers practical advice for organizing, producing, and running a screencast or webinar that works with most hosting platforms. He explores choosing the right software tools and web cameras. Learn how to get the best video and sound from a computer screen.
Choosing the right recording tools (software vs. hardware)
Organizing your content
Setting up your presentation computer
Selecting a microphone for recording
Using a pro camera via Thunderbolt or USBC
Optimizing slides
Why Is Managing Software So Hard?
This presentation explores the reasons why software projects are significantly more difficult to manage than other types of projects. Software-specific issues related to scope, resources, and time are explored, as well as how software projects differ from other projects in the physical world. An argument for why software constitutes a “Wicked Problem” is expanded, and numerous software development myths are attacked with real-world anecdotes and solutions.
Essential Prototyping for Entrepreneurs
Prototyping is a skill that every entrepreneur should have. As a UX designer who turns to startup founder myself, I crafted this course and hope it can help a non-technical people can get started doing something toward from their idea to the next step.
SW Engineering Management
- Software engineering is extremely complex and expensive work, with large software systems costing more than buildings and often having high failure rates.
- The two main factors that cause "runaway" software projects that exceed budgets and schedules are poor estimation done too early and unstable requirements that change frequently.
- Programmers are often given impossible tasks with too much work and not enough time, leading them to produce workarounds and quick fixes rather than well-designed solutions.
Bringing Quality Design Systems to Life with Storybook & Applitools
** Full webinar recording: https://youtu.be/R6WnEzlMHac **
Bringing design systems and component libraries to life can be a large, challenging process without the right tools. On top of that, maintaining a high level of quality throughout those systems brings its own challenge.
While there’s no shortage of ways to manually create a design system from scratch, doing so can be time consuming and can lead to technical debt when the system itself isn’t itself in a structure.
Storybook is a tool for developers that helps bring design systems and component libraries to life, providing structured tooling and a web dashboard. It gives those developers, and even designers, a way to focus on each individual component while being able to see the system from a higher perspective.
On top of that, Applitools is an automated Visual Testing solution that easily stacks right on top of Storybook with the Storybook Eyes SDK. With a single command, Applitools provides full test coverage for each component of your design system.
Join Developer Advocate, Colby Fayock, as he walks through:
How to take advantage of using Storybook to build scalable design systems
How Applitools makes automating the testing of those components easy
How to focus on building great experiences while automating quality checks with visual testing
Fowd Recap
This document summarizes the highlights from the FOWD 2009 conference, compressing 8 hours of talks into 25 minutes. It includes summaries of presentations on progressive enhancements with CSS3, designing for user feedback at Digg, the future of web design with new display technologies, actively designing community at Vimeo, getting work done without worrying, the future of markup languages, and creating art with technology. The document also notes that a panel debate on short form vs. long form content did not produce many clear answers.
Sedgwick e0498336-d0105-30534-assessment 02-portfolio
This document provides an assessment overview for a graphic design portfolio assignment. Students are asked to design graphic elements for both 2D and 3D applications to showcase a hypothetical graphic design studio space. The assessment involves three parts: 1) Formalizing a design brief, 2) Gaining feedback and collaborating with others, and 3) Presenting design concepts and a production plan. Students are evaluated on their understanding and application of the graphic design process.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Climate Impact of Software Testing at Nordic Testing Days
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.
More Related Content
Similar to Pipelines to production
Android design lecture #1
This document summarizes an Android design course presented by Yonatan Levin. It discusses:
1. The history and goals of the course, which aims to teach designers and developers how to better integrate and communicate through hands-on lessons and a hackathon.
2. Logistics of the course including its schedule over multiple sessions and expectations for watching online videos between lessons.
3. Key technical concepts in Android design like using density-independent pixels (dp) to account for different screen densities, providing multiple versions of assets, and naming conventions.
Constantly Contributing Pretty Patches FLCD
Many times we developers have come across the perfect contributed module, with a section of code that just doesn't do it for us. Since the Drupal infrastructure is Open to all, it is simpler to take that awesome-ish module and make the changes we need to make it full on awesome. Then we need to take those changes and apply it back to the module and let the whole world bask in the awesome, but we don't get to commit, to Git. (Rule of threes). Therefore we need to create a patch that allows the maintainer of the module to easily combine your great code with theirs. In this session we'll go over the acceptable ways to clone a projects repository, create a great looking patch and contribute said greatness back to the project. Thus, adding to the great chain of life. Oh, was it mentioned that this will work with Drupal Core as well? It should have been.
From four to forty in four years - lessons from growing a team
Between 2016 and 2020, the PureGym IT Team grew from 4 to 40 people. During that time Rich worked closely with them to navigate the tricky process of scaling. This talk is a journey through that growth period and discusses the variety of processes and practices that were applied in order to stay "Agile".
We'll touch on the various approaches taken including topics such as Scrum, Lean, Kanban, GIST planning, Lean Startup, DevOps, IaC, Azure, Story Mapping, BDD, TDD, Project vs Product and we'll be looking at the successes, failures and lessons learned.
We'll also look at how concepts from Team Topologies were applied, what team structures and interaction models were chosen and how that shifted the team dynamic. We will discuss what, in Rich's opinion, has worked well and what hasn't worked well during that time.
At very least you will walk away from this session with a long list of books to read and hopefully some insights into whether you might want to try some of the approaches discussed during the talk.
REAL Eval 6
The student learned several skills from collaboratively constructing a blog and film project. They used a blog to post updates and receive feedback, and learned how to design and format a blog. SurveyMonkey was used to collect feedback, and YouTube and social media helped share work. Skills learned included uploading videos to YouTube, inserting screenshots, and using a microphone, camera, tripod, and lighting rig for filming. Editing software taught continuity editing, split screens, adjusting volume and fades, adding text, rendering, and shortcuts to improve efficiency. Feedback helped improve lighting, effects, and overall production quality.
How HipChat Ships and Recovers Fast with DevOps Practices
HipChat operates a ‘You Build It, You Run It’ service model, where developers are responsible for building, testing, and operating their systems. While we have a high speed of development, things can break – but we also recover quickly. Learn about how we've integrated best practices within our planning, building, operating and learning processes to optimize for speed and efficiency but also mitigate, prepare for, and handle incidents.
The presenter will walk you through four steps for how to operate at a high speed of development and also prepare for any incident — planning, prevention, preparation and collecting feedback— and instruct you on how you can build these processes into your Atlasssian workflow (including JIRA Software, HipChat, Bitbucket, Confluence, Bamboo, and StatusPage).
Learn about:
- Planning: How we use JIRA Software and Confluence to plan roadmaps and sync up with teams
- Prevention: Best practices during code reviews and testing
- Preparation: How we prepare for incidents with war games
Review: Collecting feedback, assessing incident causes and improving our processes
Come out of this session with a newfound understanding of how to use Atlassian products within your DevOps workflow!
Mickie Betz, Software Developer, Atlassian
Optimizing developer onboarding
The document discusses optimizing developer onboarding by focusing on three key questions: how easy it is for developers to understand a product, how quickly developers can get started using a product, and how easy it is for developers to find references and examples. It provides examples from Netlify, Twilio, GitHub, and other companies that effectively address these questions through approaches like descriptive messaging, fast deployment templates, and embedded documentation with live examples.
Visual Studio Mobile Center: A story about mobile DevOps
This story summarizes the journey of a mobile app development team implementing DevOps practices to continuously improve their app quality and release process. The team faced issues with outdated test builds, poor app ratings, and a manual release process. They started using Visual Studio Team Services (VSTS) to automate builds, implement branching for quality, add crash analytics and usage tracking, and configure a release pipeline for staged rollouts. This helped improve app quality through testing, get feedback from users, and release new versions more reliably and frequently. While VSTS was missing some features like store deployments and secret management, it helped the team establish better DevOps practices for continuous delivery.
Being a Little Agile
The document discusses Agile Scrum methodology and how it was used to develop PanoPla, a virtual reality tool. It describes the Scrum process which involves daily stand-ups, bi-weekly deliverables, and retrospectives. A team including students and a Scrum Master from Bit Space Development iteratively built PanoPla over several months, gaining early feedback from users. The result was an open beta version of PanoPla with over 5,000 users in just 4 months.
ContentsTeam Work Schedule3Team Task Assignment3Project .docx
Contents
Team Work Schedule 3
Team Task Assignment 3
Project Plan 4
Step 1: Define the Problem 4
Step 2: Create a Plan 4
Step 3: Execute 4
Step 4: Check Work 6
Step 5: Learn and Generalize 6
House of Quality (HOQ) for Theia’s Smart Glasses 7
Step 1: Define the Problem 7
Step 2: Create a Plan 7
Step 3: Execute 8
Step 4: Check Work 14
Step 5: Learn and Generalize 14
Aggregate Project Plan 15
Step 1: Define the Problem 15
Step 2: Create a Plan 15
Step 3: Execute 16
Step 4: Check Work 22
Step 5: Learn and Generalize 22
I was able to use the APP skills from the midterm and apply it to our actual project. We learned that project #2 yields the highest EMV so that will be the industry we will be focusing on. 22
Theia’s Conceptual Design Process 23
Step 1: Define the Problem 23
Step 2: Create a Plan 23
Step 3: Execute 24
Concept 1 27
Concept 2 28
Concept 3 29
Concept 4 30
Concept 5 31
Concept 6 32
Step 4: Check Work 34
Step 5: Learn and Generalize 34
Phase Ⅱ Reportca 36
Step 1: Define the Problem 36
Step 2: Create a Plan 36
Step 3: Execute 36
Project Planning 36
House of Quality 37
Aggregate Project Plan 37
Reverse Engineering (includes FAST analysis + diagram) 38
Conceptual Design 38
Step 4: Check Work 38
Step 5: Learn and Generalize 39
Team Work Schedule
Date
Task
10/24
Homework assigned, touch bases with team to decide weekend plans.
10/25
Read handout and HOQ example. Everyone assigned to do individual research about AR Glasses.
10/26
Read handout and HOQ example. Everyone assigned to do individual research about AR Glasses.
10/27
Meet at a cafe downtown, due to the power outage. Meeting time is 1 hour.
10/28
Everyone working remotely. Also everyone is working on Phase I/II at the moment. HOQ problem is postponed for a while as we are working on Phase I/II.
10/29
Meet at TBD. Meeting time is 1 hour.
10/30
Revise our work.
10/31
Final revisions. Turn in homework.
Team Task Assignment
Task
Phase 1 - Missing Info + Tech Strategy
Phase 1 - Missing Functional Maps
Project Planning
House of Quality for Product
Aggregate Project Plan
Reverse Engineering
Conceptual Design
Phase II ReportProject PlanStep 1: Define the Problem
We need to clearly determine the tasks required of this project and develop a systematic plan of action to tackle these tasks.Step 2: Create a Plan
Framework for Project Planning:
1. Clearly state the intent of the Project
2. Determine the Design/Development sub-tasks and activities Comment by Christopher Chiang: Develop OS
Develop Display technology
Develop glasses framework
Audio Output
Develop Bluetooth compatibility
Battery development
Charge development
Environment sensing capability
3. Create a design/development activity matrix
4. Create a schedule for each subtask using a GANTT Chart
5. Identify the Critical Path for the Project
6. Assign Clear Roles and Responsibilities & track progressStep 3: Execute
1. Clearly state the intent of the Project
a. Develop smart glasses wearable technology prototype within a 1 year timesp.
video marketing cheat sheet
This document discusses the benefits of using video marketing and provides tips for creating videos. Some key benefits outlined are that video builds trust and makes you more relatable without requiring much time. It also helps increase search engine optimization and visibility across devices. Guidelines are provided for both creating videos using cameras or screen recording software, as well as tips for editing, uploading, optimizing, and sharing videos.
Designer vs Developer (Barcamp Memphis 2009)
The document discusses the relationship between designers and developers, highlighting potential points of conflict and providing advice for effective collaboration. It acknowledges that designers and developers may see things differently and offers tips for open communication, trust-building, compromise, and keeping the end user's needs as the top priority. Working together effectively requires understanding different perspectives, finding solutions, and having each other's backs.
Tour of Mobile usability testing apps and services
Ok, you have been asked to go off and research how to design/architect a mobile user experience. After the initial excitement and learning all about mobile UX, you decide to jump head-on and start designing.
Then comes the realization, how are you going to test the designs in context of a mobile device? Do you have to package everything in an app or is there a way to test preliminary designs? What tools are available? Which works for what Mobile OS? When to use a particular tool? Can, we, designers use it without developer help?
In this presentation I have various testing app/methods/tools/services available specifically for Mobile, for which OS, when to best use them during design process, cost associated with some of the tools, and what are pros & cons of each of them.
Pair Programming, TDD and other impractical things
"Why should we write our tests first? Isn't that going to slow my development?" "What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!" "Look, in the perfect world your advises are great, but I have a project to finish here." In this talk Marcello explores efficiency in contrast to effectiveness. He looks into how practices, traditionally accepted as efficient, sometimes turn out to be less effective than a few "impractical" things he has come across.
Producing Effective Screencasts
Sharing the content of your screen has become a standard for both prerecorded and live video. Whether you’re teaching software, giving a slide presentation, or hosting a business meeting this is a great technique. Rich Harrington has been producing screencasts for 20 years and clients including Apple, Adobe, Microsoft, Skylum, and many more.
In this course, he offers practical advice for organizing, producing, and running a screencast or webinar that works with most hosting platforms. He explores choosing the right software tools and web cameras. Learn how to get the best video and sound from a computer screen.
Choosing the right recording tools (software vs. hardware)
Organizing your content
Setting up your presentation computer
Selecting a microphone for recording
Using a pro camera via Thunderbolt or USBC
Optimizing slides
Why Is Managing Software So Hard?
This presentation explores the reasons why software projects are significantly more difficult to manage than other types of projects. Software-specific issues related to scope, resources, and time are explored, as well as how software projects differ from other projects in the physical world. An argument for why software constitutes a “Wicked Problem” is expanded, and numerous software development myths are attacked with real-world anecdotes and solutions.
Essential Prototyping for Entrepreneurs
Prototyping is a skill that every entrepreneur should have. As a UX designer who turns to startup founder myself, I crafted this course and hope it can help a non-technical people can get started doing something toward from their idea to the next step.
SW Engineering Management
- Software engineering is extremely complex and expensive work, with large software systems costing more than buildings and often having high failure rates.
- The two main factors that cause "runaway" software projects that exceed budgets and schedules are poor estimation done too early and unstable requirements that change frequently.
- Programmers are often given impossible tasks with too much work and not enough time, leading them to produce workarounds and quick fixes rather than well-designed solutions.
Bringing Quality Design Systems to Life with Storybook & Applitools
** Full webinar recording: https://youtu.be/R6WnEzlMHac **
Bringing design systems and component libraries to life can be a large, challenging process without the right tools. On top of that, maintaining a high level of quality throughout those systems brings its own challenge.
While there’s no shortage of ways to manually create a design system from scratch, doing so can be time consuming and can lead to technical debt when the system itself isn’t itself in a structure.
Storybook is a tool for developers that helps bring design systems and component libraries to life, providing structured tooling and a web dashboard. It gives those developers, and even designers, a way to focus on each individual component while being able to see the system from a higher perspective.
On top of that, Applitools is an automated Visual Testing solution that easily stacks right on top of Storybook with the Storybook Eyes SDK. With a single command, Applitools provides full test coverage for each component of your design system.
Join Developer Advocate, Colby Fayock, as he walks through:
How to take advantage of using Storybook to build scalable design systems
How Applitools makes automating the testing of those components easy
How to focus on building great experiences while automating quality checks with visual testing
Fowd Recap
This document summarizes the highlights from the FOWD 2009 conference, compressing 8 hours of talks into 25 minutes. It includes summaries of presentations on progressive enhancements with CSS3, designing for user feedback at Digg, the future of web design with new display technologies, actively designing community at Vimeo, getting work done without worrying, the future of markup languages, and creating art with technology. The document also notes that a panel debate on short form vs. long form content did not produce many clear answers.
Sedgwick e0498336-d0105-30534-assessment 02-portfolio
This document provides an assessment overview for a graphic design portfolio assignment. Students are asked to design graphic elements for both 2D and 3D applications to showcase a hypothetical graphic design studio space. The assessment involves three parts: 1) Formalizing a design brief, 2) Gaining feedback and collaborating with others, and 3) Presenting design concepts and a production plan. Students are evaluated on their understanding and application of the graphic design process.
Similar to Pipelines to production (20)
From four to forty in four years - lessons from growing a team
From four to forty in four years - lessons from growing a team
How HipChat Ships and Recovers Fast with DevOps Practices
How HipChat Ships and Recovers Fast with DevOps Practices
Visual Studio Mobile Center: A story about mobile DevOps
Visual Studio Mobile Center: A story about mobile DevOps
ContentsTeam Work Schedule3Team Task Assignment3Project .docx
ContentsTeam Work Schedule3Team Task Assignment3Project .docx
Tour of Mobile usability testing apps and services
Tour of Mobile usability testing apps and services
Pair Programming, TDD and other impractical things
Pair Programming, TDD and other impractical things
Bringing Quality Design Systems to Life with Storybook & Applitools
Bringing Quality Design Systems to Life with Storybook & Applitools
Sedgwick e0498336-d0105-30534-assessment 02-portfolio
Sedgwick e0498336-d0105-30534-assessment 02-portfolio
Recently uploaded
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Climate Impact of Software Testing at Nordic Testing Days
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.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.OpenID AuthZEN Interop Read Out - Authorization
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
CAKE: Sharing Slices of Confidential Data on Blockchain
Presented at the CAiSE 2024 Forum, Intelligent Information Systems, June 6th, Limassol, Cyprus.
Synopsis: Cooperative information systems typically involve various entities in a collaborative process within a distributed environment. Blockchain technology offers a mechanism for automating such processes, even when only partial trust exists among participants. The data stored on the blockchain is replicated across all nodes in the network, ensuring accessibility to all participants. While this aspect facilitates traceability, integrity, and persistence, it poses challenges for adopting public blockchains in enterprise settings due to confidentiality issues. In this paper, we present a software tool named Control Access via Key Encryption (CAKE), designed to ensure data confidentiality in scenarios involving public blockchains. After outlining its core components and functionalities, we showcase the application of CAKE in the context of a real-world cyber-security project within the logistics domain.
Paper: https://doi.org/10.1007/978-3-031-61000-4_16
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Things to Consider When Choosing a Website Developer for your Website | FODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Recently uploaded (20)
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
CAKE: Sharing Slices of Confidential Data on Blockchain
CAKE: Sharing Slices of Confidential Data on Blockchain
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
Things to Consider When Choosing a Website Developer for your Website | FODUU
Things to Consider When Choosing a Website Developer for your Website | FODUU
Pipelines to production
- 1. chef.io Detangling the DevOps Web (of Lies?) Pipelines to Production
- 2. @jo@joderita @drrk derita @drrk chef.io@joderita @drrk What are the problems people are trying to solve? What brings people to DevOps? How does DevOps solve them? And how does it fail?
- 3. @jo@joderita @drrk derita @drrk chef.io@joderita @drrk Jody Wolfborn - @joderita ● A lifetime in public speaking, 10+ years in technology ● Made a career out of understanding languages: non-verbal, spoken, and programming ● Slightly obsessed with exclamation marks!!!! Who we are Kimball Johnson - @drrk ● A lifetime in tech, 20+ years getting paid for it ● Made a career out of understanding languages: ADA, Fortran, Pascal, and Prolog--plus all the normal ones ● Slightly obsessed with Lego (free Yoda, anyone??)
- 4. To place an image: 1. Insert image into slide 2. With the image selected, click arrow next to the crop symbol 3. Select the rectangle shape and crop image to fit area. 4 chef.io@joderita @drrk Inflexible, rigid practices Create and enable cross-functional, autonomous teams Automate all the (repetitive, time-consuming, or mundane) things Photo by Johan Bos from Pexels
- 5. To place an image: 1. Insert image into slide 2. With the image selected, click arrow next to the crop symbol 3. Select the rectangle shape and crop image to fit area. 5 chef.io@joderita @drrk Sloooooow systems Use the right tools for the problem Continuously test and integrate new changes Continuously deploy production goodness Make small, iterative changes cc-by-nc-sa/2.0 https://www.flickr.com/photos/rwd/33305109244/
- 6. To place an image: 1. Insert image into slide 2. With the image selected, click arrow next to the crop symbol 3. Select the rectangle shape and crop image to fit area. 6 chef.io@joderita @drrk Faulty fault recovery Source and version control all the things Proactively monitor production
- 7. To place an image: 1. Insert image into slide 2. With the image selected, click arrow next to the crop symbol 3. Select the rectangle shape and crop image to fit area. 7 chef.io@joderita @drrk Lack of control Peer review production changes Automate acceptance testing End-to-end responsibility through agreed-upon change processes
- 8. To place an image: 1. Insert image into slide 2. With the image selected, click arrow next to the crop symbol 3. Select the rectangle shape and crop image to fit area. 8 chef.io@joderita @drrk It’s better than what we have!! Promote and develop win-win relationship (and outcomes) between Dev and Ops Culture! The seaweed is always greener in somebody else’s lake cc-by-sa /2.0 - Sheep against fence bbt Trevor Littlewood geograph.org.uk/p/4299350
- 9. chef.io DevOps is about Communication Breakdowns in DevOps are breakdowns in Communication Communicate your needs empathetically, but more importantly.... You have two ears and one mouth (Nathen Harvey) So listen, and respond empathetically.