The document discusses implementing shared on-call responsibilities between developers and operations teams to build empathy. It argues that simply telling developers they should care more is not a solution, and that giving them a real view of production problems through shared pain of being on-call together could incentivize better practices. The document addresses objections that developers may not have proper access or knowledge, responding that the goal is to solve problems as a team rather than any one person having all the answers.
IA Summit 2010 - Career Workshop - April 8, 2010 -Phoenix, AZRuss U
http://2010.iasummit.org/talks/9703
The Career Workshop for Information Architects and other User Experience
Professionals is a half-day event that teaches attendees how to optimize their
career search. Attendees will learn the skills needed in today’s market, and
will get the opportunity to network and share ideas.
Divided into four information-packed sessions, the workshop will include
discussions, and individual and team exercises:
1. Career Listings, Career Sites and Agencies
Looking at recent career listings to understand what employers are looking for
Communicating what IA’s do to recruiters
Applying lessons learned to cover letters and interview conversations
2. Resumes
Examining sample resumes
Tips for designing an IA-oriented resume that stands out
3. Portfolios
Understanding what makes a great portfolio
Determining the best method to display it
4. Interviewing
Examining what interviewers want to hear
Presenting yourself through your portfolio
Communication tips for before, during and after the interview
The document provides guidance to students on developing a business plan for a new beverage product called Dr. Tigercrab. It directs students to various websites to research business structures, name their business, understand entrepreneur traits, and identify the key elements of a business plan. The students decide on an LLC structure for their business and that marketing and sales projections will be an important part of their business plan.
This document provides guidance on transitioning an organization to a DevOps model. It discusses how organizational structures can impact technical designs based on Conway's Law. It then covers common anti-patterns when shifting to DevOps like relying on a single consultant. The document proposes using a logical rather than structural view of the organization and modeling it after Spotify's Guild model. It offers tips for facilitating collaboration between teams and overcoming challenges to change. Finally, it addresses technical transition topics like security as code and environment consistency. The overall message is that organizational change requires clear communication, addressing business needs, facilitating cross-team work, and setting ambitious yet achievable goals.
Presentation at Mastering SAP 21st May 2017
Struggling with agile at scale? Thinking about scaling agile beyond the team? Want to learn from others’ mistakes? There is a lot to be learnt from those who have successfully hitchhiked their way through the galaxy of scaled agile. This session celebrates the scaled agile hitchhiker, the people who bravely tried ideas that were occasionally brilliant but often plain stupid. You will laugh, you will cry but you will also walk away with a nice long list of ideas not to try when scaling agile!
• Seven failure patterns in scaling agile
• An understanding of why these patterns lead to less than optimal results
• Tips on how to avoid falling into these failure patterns
Thoughts on why the world needs open source, and how we can use the ideal of open source to ensure more open, collaborative businesses and business models.
Outages, APIs, Benchmarks and Other Atrocities of Cloud MarketingShanley Kane
The document criticizes misleading and nonsensical marketing language used by cloud computing vendors. It provides examples of buzzwords that don't actually mean anything, such as "big data" when a company likely doesn't have big data. It also criticizes poorly done benchmarks that don't resemble real-world usage. The document advocates for more honest and accurate marketing language and benchmarks that show how products perform under realistic conditions.
Business Model Canvas mash-up with the 4Qs Framework. Mash-up by Allen Pattis...run_frictionless
Allen Pattiselanno shares his own special blend of SWOT Analysis, Business Model Canvas, and 4Qs to create a unique approach to digital transformation.
This document provides an overview of design thinking. It discusses how design thinking is an iterative process that involves empathizing with users, defining problems from the user's perspective, ideating solutions, prototyping ideas, and testing prototypes. Rather than taking problems at face value, design thinking challenges assumptions to reframe problems in a human-centered way. It encourages exploring unknown aspects of problems and generating alternative solutions. The document provides examples of how well-known problems could be viewed more broadly and solved innovatively using a design thinking approach focused on user needs rather than predefined solutions.
IA Summit 2010 - Career Workshop - April 8, 2010 -Phoenix, AZRuss U
http://2010.iasummit.org/talks/9703
The Career Workshop for Information Architects and other User Experience
Professionals is a half-day event that teaches attendees how to optimize their
career search. Attendees will learn the skills needed in today’s market, and
will get the opportunity to network and share ideas.
Divided into four information-packed sessions, the workshop will include
discussions, and individual and team exercises:
1. Career Listings, Career Sites and Agencies
Looking at recent career listings to understand what employers are looking for
Communicating what IA’s do to recruiters
Applying lessons learned to cover letters and interview conversations
2. Resumes
Examining sample resumes
Tips for designing an IA-oriented resume that stands out
3. Portfolios
Understanding what makes a great portfolio
Determining the best method to display it
4. Interviewing
Examining what interviewers want to hear
Presenting yourself through your portfolio
Communication tips for before, during and after the interview
The document provides guidance to students on developing a business plan for a new beverage product called Dr. Tigercrab. It directs students to various websites to research business structures, name their business, understand entrepreneur traits, and identify the key elements of a business plan. The students decide on an LLC structure for their business and that marketing and sales projections will be an important part of their business plan.
This document provides guidance on transitioning an organization to a DevOps model. It discusses how organizational structures can impact technical designs based on Conway's Law. It then covers common anti-patterns when shifting to DevOps like relying on a single consultant. The document proposes using a logical rather than structural view of the organization and modeling it after Spotify's Guild model. It offers tips for facilitating collaboration between teams and overcoming challenges to change. Finally, it addresses technical transition topics like security as code and environment consistency. The overall message is that organizational change requires clear communication, addressing business needs, facilitating cross-team work, and setting ambitious yet achievable goals.
Presentation at Mastering SAP 21st May 2017
Struggling with agile at scale? Thinking about scaling agile beyond the team? Want to learn from others’ mistakes? There is a lot to be learnt from those who have successfully hitchhiked their way through the galaxy of scaled agile. This session celebrates the scaled agile hitchhiker, the people who bravely tried ideas that were occasionally brilliant but often plain stupid. You will laugh, you will cry but you will also walk away with a nice long list of ideas not to try when scaling agile!
• Seven failure patterns in scaling agile
• An understanding of why these patterns lead to less than optimal results
• Tips on how to avoid falling into these failure patterns
Thoughts on why the world needs open source, and how we can use the ideal of open source to ensure more open, collaborative businesses and business models.
Outages, APIs, Benchmarks and Other Atrocities of Cloud MarketingShanley Kane
The document criticizes misleading and nonsensical marketing language used by cloud computing vendors. It provides examples of buzzwords that don't actually mean anything, such as "big data" when a company likely doesn't have big data. It also criticizes poorly done benchmarks that don't resemble real-world usage. The document advocates for more honest and accurate marketing language and benchmarks that show how products perform under realistic conditions.
Business Model Canvas mash-up with the 4Qs Framework. Mash-up by Allen Pattis...run_frictionless
Allen Pattiselanno shares his own special blend of SWOT Analysis, Business Model Canvas, and 4Qs to create a unique approach to digital transformation.
This document provides an overview of design thinking. It discusses how design thinking is an iterative process that involves empathizing with users, defining problems from the user's perspective, ideating solutions, prototyping ideas, and testing prototypes. Rather than taking problems at face value, design thinking challenges assumptions to reframe problems in a human-centered way. It encourages exploring unknown aspects of problems and generating alternative solutions. The document provides examples of how well-known problems could be viewed more broadly and solved innovatively using a design thinking approach focused on user needs rather than predefined solutions.
This document discusses seven traps that large, successful organizations can fall into as they grow: 1) Slow growth as organizations get bigger, 2) Holding onto old products for too long, 3) Success breeding complacency, 4) Shifting from generalization to specialization, 5) Prioritizing efficiency over creativity, 6) Focusing on rules rather than tasks, 7) Shifting from curiosity to complacency. It provides examples and sources for each trap and suggests that organizations must adapt to changes, question the status quo, and remain innovative in order to avoid stagnating.
Corporate Innovation - Challenges of Lean Startup inside a Fortune 25Kunjorn Chambundabongse
This is from a talk I gave at Lean Startup Labs Enterprise session in NYC about many of the challenges you'll run into (as well as things you can do) running a Lean Startup incubation group to focus on disruptive or adjacent innovation inside a very large public corporation, given in a fun Pac Man style theme!
From the GitLab Data Team member, a first-face story about how the asynchronous way of working helps us manage the “chaos” (as folks usually think about remote work) in the 24/7 work environment. In this session, I like to demystify transparency and how it can leverage your success. The narrative is related to the Data team in GitLab and can be used for any matter. Will wrap the topics and guide you through: - Why transparency is an organic way to communicate and cooperate, - How to stay secure when you share everything or almost everything with the outer world, - How to leverage your data usage and still stay a good boy of the IT world, - What you should promise to your community
The document provides advice for startups, including focusing on solving one problem at a time, using agile development practices, understanding customer needs, executing effectively, collaborating with others, marketing through blogs and videos, seeking mentors, and potentially joining incubators for resources and support. It also cautions startups to build less features than competitors initially and discusses fundraising and investors.
This document provides a brief guide to IT project management. It summarizes several studies that found a significant number of IT projects fail due to a lack of proper planning and management. The document outlines best practices for successfully managing an IT project, including having a clear target and timeline, a structured plan, communication with stakeholders, and allowing time for testing.
#FounderHacks by Raj Kapoor - cofounder.coRajil Kapoor
This document discusses lessons learned from the Snapfish story and what investors look for in founders and companies. It provides key takeaways from Snapfish including focusing on passion, hiring strong talent, and being open to change. For investors, they seek experienced internet-focused teams tackling big problems, that can execute quickly and have a recurring revenue model. Investors also look for founders who are product-obsessed, can code, are well-connected, and have a track record of success.
Great Ideas Do Not Succeed On Their Moral Authoritycarlkessler
Technical staff often think that because an idea is a good, it should succeed of its own merit. In reality, one needs a good business case and solid effort in selling the value to the corporation. This presentation covers many of the pitfalls awaiting the person as the beginning selling their idea.
This document provides guidance for interning at startups. It emphasizes that startups are different than large companies and interning will change interns. It includes tips for preparing like reading about startups and building portfolio projects. The document lists 50 experimental projects interns can tackle and provides schedules of internship application periods. It also shares advice from past interns about learning to take action and work without strict hierarchies in startups.
Jazz Yao-Tsung Wang shares their methodology for career development and design thinking which involves 5 steps: 1) Finding your strengths, 2) Linking past experiences, 3) Writing down goals, 4) Being aware of market demands and supplies, and 5) Being outcomes-oriented. Wang provides examples from their own career journey and encourages attendees to focus on their unique strengths, experiences, and goals when designing their career path. Career design is presented as an ongoing and non-linear process.
Growth Hacking for Corporates (www.wepullthetrigger.com)Trigger
Growth hacking is not only a startup trend, but also for corporates. Dive in to some of the fundamentals that corporates need to adopt to maximise the benefits of growth hacking and discover four things only a growth hacker can do (things a traditional marketer never will have the skills or guts to do). Hiring a growth hacker is one of the first steps for unlocking your growth!
Lean Innovation at UnitedHealth Group, Kunjorn Chambungdabongse, OptumLean Startup Co.
Learn how a group of corporate innovation leaders, change agents, and intrapreneurs implemented a Lean innovation incubator inside a Fortune 14 organization. Hear the story of The Garage, challenges to innovation in the enterprise, and lessons we have learned along the way.
Have you reached an inflection point in your career? Not sure how to get to the next step – or even what the next step will be? In this hands-on session, you will get an overview of the hiring landscape and salary trends for UX professionals. You’ll hear about the most in-demand positions and skills that employers are willing to pay a premium for – and learn how you can target your own skill set to those opportunities. You’ll also participate in a few exercises to help actively identify new career directions, keep your digital skills relevant to employers, overcome job-hunting obstacles and, ultimately, forge a fulfilling professional path.
Class 1 - course overview Berkeley/Columbia Lean Launchpad Xmba 296tStanford University
The document provides an overview of the Lean LaunchPad course, including its objectives, structure, teams, projects, grading, and intellectual property guidelines. The course aims to teach students how to evaluate business opportunities, develop business models, conduct customer discovery and validation, and operate with insufficient data. It focuses on startups with scalable business models and opportunities over $500 million in size.
Cyril Ebersweiler and Benjamin Joffe of HAX at Stanford discuss building lean hardware startups. They outline a lean hardware philosophy of validating problems, partnering with factories, moving fast to market, being capital effective, being user backed, and focusing on sustainability. The document discusses why China makes sense for hardware startups due to low costs, economies of scale, and access to manufacturing knowledge and supply chains. It notes challenges like intellectual property protection but says hardware startups can protect IP through complex manufacturing. The document provides an overview of HAX's mission to empower founders and the hardware accelerator program they offer.
The Importance of presence, reputation, and working differentKushtrim Xhakli
This document discusses various online tools and services that can help with different aspects of starting and running a business such as building apps and prototypes, measuring analytics, crowdsourcing design work, testing with users, raising funding, and more. It provides the names and URLs of over 50 specific tools and platforms mentioned across various categories. The overall message is about recommending resources that can help accelerate and improve the process of starting and growing a new venture.
Time flies while you are chasing the dream.
In this talk about product development I will tell you why you should develop your own product, how I did it and some tips along the way.
Social media for business best practices.Eric Ritter
The document discusses best practices for using social media for business. It recommends choosing social media channels based on your audience and goals. It emphasizes having a plan, actively participating in conversations, showing your personality, and measuring your success through interactions, followers, and website traffic. The key is to create an audience and turn them into an engaged community.
The document provides an overview of the Lean LaunchPad course including:
- The course objectives are to analyze opportunities, build products, get customer orders, and work as a team using a methodology to learn about entrepreneurship.
- Students will learn about opportunity evaluation, business models, customer development, decision making with little data, and fundraising.
- The course consists of lectures, student presentations, readings, and 10-15 hours per week of work outside class in teams on startup projects.
- Grades are based on team's out-of-building progress, weekly presentations, and a final presentation and report. The focus is on how much students learn, not on selling.
Session 8/8. Workshop roundup. The Strategic Content Alliance, JISC sponsored workshops on Maximising Online Resource Effectiveness, held on different occasions throughout 2010 and delivered by Netskills.
1. The document discusses managing technical debt by treating it as a financial tool, with costs and terms that must be understood and managed.
2. It encourages engineering teams to explicitly track technical debt, including estimating costs like time to resolve issues and pay down debt, in order to negotiate priorities and pace of work with business partners.
3. By making technical debt visible, teams can incorporate debt repayment into their processes and ensure flow of work is maintained over time.
Original crack at talking about technical debt. Idea developing from this LinkedIn Post - https://www.linkedin.com/feed/update/urn:li:activity:6957393517170110464/
Thanks to Cloud Austin for putting on the Dog Days of DevOps - https://www.meetup.com/cloudaustin/events/285856645/
This document discusses seven traps that large, successful organizations can fall into as they grow: 1) Slow growth as organizations get bigger, 2) Holding onto old products for too long, 3) Success breeding complacency, 4) Shifting from generalization to specialization, 5) Prioritizing efficiency over creativity, 6) Focusing on rules rather than tasks, 7) Shifting from curiosity to complacency. It provides examples and sources for each trap and suggests that organizations must adapt to changes, question the status quo, and remain innovative in order to avoid stagnating.
Corporate Innovation - Challenges of Lean Startup inside a Fortune 25Kunjorn Chambundabongse
This is from a talk I gave at Lean Startup Labs Enterprise session in NYC about many of the challenges you'll run into (as well as things you can do) running a Lean Startup incubation group to focus on disruptive or adjacent innovation inside a very large public corporation, given in a fun Pac Man style theme!
From the GitLab Data Team member, a first-face story about how the asynchronous way of working helps us manage the “chaos” (as folks usually think about remote work) in the 24/7 work environment. In this session, I like to demystify transparency and how it can leverage your success. The narrative is related to the Data team in GitLab and can be used for any matter. Will wrap the topics and guide you through: - Why transparency is an organic way to communicate and cooperate, - How to stay secure when you share everything or almost everything with the outer world, - How to leverage your data usage and still stay a good boy of the IT world, - What you should promise to your community
The document provides advice for startups, including focusing on solving one problem at a time, using agile development practices, understanding customer needs, executing effectively, collaborating with others, marketing through blogs and videos, seeking mentors, and potentially joining incubators for resources and support. It also cautions startups to build less features than competitors initially and discusses fundraising and investors.
This document provides a brief guide to IT project management. It summarizes several studies that found a significant number of IT projects fail due to a lack of proper planning and management. The document outlines best practices for successfully managing an IT project, including having a clear target and timeline, a structured plan, communication with stakeholders, and allowing time for testing.
#FounderHacks by Raj Kapoor - cofounder.coRajil Kapoor
This document discusses lessons learned from the Snapfish story and what investors look for in founders and companies. It provides key takeaways from Snapfish including focusing on passion, hiring strong talent, and being open to change. For investors, they seek experienced internet-focused teams tackling big problems, that can execute quickly and have a recurring revenue model. Investors also look for founders who are product-obsessed, can code, are well-connected, and have a track record of success.
Great Ideas Do Not Succeed On Their Moral Authoritycarlkessler
Technical staff often think that because an idea is a good, it should succeed of its own merit. In reality, one needs a good business case and solid effort in selling the value to the corporation. This presentation covers many of the pitfalls awaiting the person as the beginning selling their idea.
This document provides guidance for interning at startups. It emphasizes that startups are different than large companies and interning will change interns. It includes tips for preparing like reading about startups and building portfolio projects. The document lists 50 experimental projects interns can tackle and provides schedules of internship application periods. It also shares advice from past interns about learning to take action and work without strict hierarchies in startups.
Jazz Yao-Tsung Wang shares their methodology for career development and design thinking which involves 5 steps: 1) Finding your strengths, 2) Linking past experiences, 3) Writing down goals, 4) Being aware of market demands and supplies, and 5) Being outcomes-oriented. Wang provides examples from their own career journey and encourages attendees to focus on their unique strengths, experiences, and goals when designing their career path. Career design is presented as an ongoing and non-linear process.
Growth Hacking for Corporates (www.wepullthetrigger.com)Trigger
Growth hacking is not only a startup trend, but also for corporates. Dive in to some of the fundamentals that corporates need to adopt to maximise the benefits of growth hacking and discover four things only a growth hacker can do (things a traditional marketer never will have the skills or guts to do). Hiring a growth hacker is one of the first steps for unlocking your growth!
Lean Innovation at UnitedHealth Group, Kunjorn Chambungdabongse, OptumLean Startup Co.
Learn how a group of corporate innovation leaders, change agents, and intrapreneurs implemented a Lean innovation incubator inside a Fortune 14 organization. Hear the story of The Garage, challenges to innovation in the enterprise, and lessons we have learned along the way.
Have you reached an inflection point in your career? Not sure how to get to the next step – or even what the next step will be? In this hands-on session, you will get an overview of the hiring landscape and salary trends for UX professionals. You’ll hear about the most in-demand positions and skills that employers are willing to pay a premium for – and learn how you can target your own skill set to those opportunities. You’ll also participate in a few exercises to help actively identify new career directions, keep your digital skills relevant to employers, overcome job-hunting obstacles and, ultimately, forge a fulfilling professional path.
Class 1 - course overview Berkeley/Columbia Lean Launchpad Xmba 296tStanford University
The document provides an overview of the Lean LaunchPad course, including its objectives, structure, teams, projects, grading, and intellectual property guidelines. The course aims to teach students how to evaluate business opportunities, develop business models, conduct customer discovery and validation, and operate with insufficient data. It focuses on startups with scalable business models and opportunities over $500 million in size.
Cyril Ebersweiler and Benjamin Joffe of HAX at Stanford discuss building lean hardware startups. They outline a lean hardware philosophy of validating problems, partnering with factories, moving fast to market, being capital effective, being user backed, and focusing on sustainability. The document discusses why China makes sense for hardware startups due to low costs, economies of scale, and access to manufacturing knowledge and supply chains. It notes challenges like intellectual property protection but says hardware startups can protect IP through complex manufacturing. The document provides an overview of HAX's mission to empower founders and the hardware accelerator program they offer.
The Importance of presence, reputation, and working differentKushtrim Xhakli
This document discusses various online tools and services that can help with different aspects of starting and running a business such as building apps and prototypes, measuring analytics, crowdsourcing design work, testing with users, raising funding, and more. It provides the names and URLs of over 50 specific tools and platforms mentioned across various categories. The overall message is about recommending resources that can help accelerate and improve the process of starting and growing a new venture.
Time flies while you are chasing the dream.
In this talk about product development I will tell you why you should develop your own product, how I did it and some tips along the way.
Social media for business best practices.Eric Ritter
The document discusses best practices for using social media for business. It recommends choosing social media channels based on your audience and goals. It emphasizes having a plan, actively participating in conversations, showing your personality, and measuring your success through interactions, followers, and website traffic. The key is to create an audience and turn them into an engaged community.
The document provides an overview of the Lean LaunchPad course including:
- The course objectives are to analyze opportunities, build products, get customer orders, and work as a team using a methodology to learn about entrepreneurship.
- Students will learn about opportunity evaluation, business models, customer development, decision making with little data, and fundraising.
- The course consists of lectures, student presentations, readings, and 10-15 hours per week of work outside class in teams on startup projects.
- Grades are based on team's out-of-building progress, weekly presentations, and a final presentation and report. The focus is on how much students learn, not on selling.
Session 8/8. Workshop roundup. The Strategic Content Alliance, JISC sponsored workshops on Maximising Online Resource Effectiveness, held on different occasions throughout 2010 and delivered by Netskills.
Similar to Longhorn PHP - Stop Doing It Wrong (20)
1. The document discusses managing technical debt by treating it as a financial tool, with costs and terms that must be understood and managed.
2. It encourages engineering teams to explicitly track technical debt, including estimating costs like time to resolve issues and pay down debt, in order to negotiate priorities and pace of work with business partners.
3. By making technical debt visible, teams can incorporate debt repayment into their processes and ensure flow of work is maintained over time.
Original crack at talking about technical debt. Idea developing from this LinkedIn Post - https://www.linkedin.com/feed/update/urn:li:activity:6957393517170110464/
Thanks to Cloud Austin for putting on the Dog Days of DevOps - https://www.meetup.com/cloudaustin/events/285856645/
As Ops and DevOps leaders we tend to focus on risks. We shoulder the burden of unmitigated risk. We lose sight of probability and cost. These slides outline a way to approach risk in a small company that builds shared accountability across all teams. Everyone is aware of the risks, everyone is aware of the choice to accept them. Everyone sleeps a bit better.
Deploying PHP Applications to AWS Elastic BeanstalkBoyd Hemphill
Delivered first at the Austin PHP Meetup. A 30,000 foot view of why Victory CTO chooses to deliver applications to Elastic Beanstalk when possible. Simply, scalable and developer friendly. Our customers win.
2017-10-24 All Day DevOps - Disposable Development EnvironmentsBoyd Hemphill
Why let your developers suffer in their own private, bespoke hell when you can standardize to improve non-functional requirements with Vagrant and Docker?
Why Docker? Is it cool? Is it the newest thing? Does it solve _my_ problem? In reality, as DevOps thought leaders and professionals the question is really, "How can the cost of a Docker adoption -- in terms of risk and opportunity cost -- benefit my company?"
Is Docker really the security risk that is generally raged about? Or, is this more about understanding where and when a business should consider adoption new and revolutionary infrastructure?
HomeOps - Reasoning About DevOps at HomeBoyd Hemphill
We all feel the need to change. But what do we change to? How do we identify what to change? Why are we changing? Looking at our daily life, my family started its own DevOps journey.
This document discusses the benefits of using Docker containers. It notes that containers have existed since 2000 but were difficult to use until Docker simplified the process in 2013. Docker allows for microservices and micro teams to work independently and at their own pace. It also enables faster build and test times through increased parallelism. Docker reduces configuration management overhead and simplifies development environments.
Docker enables new agile practices by allowing developers to work in environments that closely match production. However, DevOps thought leaders must determine how Docker adoption fits with their organization's culture and ensure it leads to business benefits like increased velocity without disrupting existing processes and tools. While Docker shows promise for accelerating development and operations, its impact on an organization depends on how well leaders apply agile and DevOps principles during implementation.
Why do containers suddenly matter so much when they have been around since 1998? Take a look at the potential of OpenStack's Magnum, Murano and Nova-Docker in the context leveraging the incredible interest in Linux Containers brought about by Docker.
Check out www.stackengine.com to learn more about our excellent container management solution.
Ever wanted to explain DevOps to your friends or family? What about that executive in sales or the project management office? LaundryOps is a metaphor for Continuous Delivery and applied DevOps thinking. It may even explain why your boss won't let you try that latest, greatest idea!
We all have a commute, but what we do with it separates DevOps thought leaders from the masses. This slide deck is was prepared for DevOps Days Austin 2015's Ignite Block. Please feel free to add the books, blogs and videos that inspire you!
The pillars of DevOps are Culture, Automation, Measurement and Sharing. Docker is a rare tool at enables DevOps through all 4 pillars. These slides take a look at how Docker can affect each pillar in your organization through a Lean lens.
Docker Enables DevOps - Keep C.A.L.M.S. and Docker on ...Boyd Hemphill
The pillars of DevOps are Culture, Automation, Measurement and Sharing. Docker is a rare tool at enables DevOps through all 4 pillars. These slides take a look at how Docker can affect each pillar in your organization through a Lean lens.
StackEngine has talked to over 100 businesses about the direction and needs of companies ranging from start ups still in Stealth mode to the Fortune 100. Combine these learnings with the features currently included in the StackEngine Controller and a solution to production operation begins to come to light.
To think about a production operation we:
* Establish the characteristics of an ideal containerized application.
* Motivate those characteristics in terms of business benefit.
* Discuss the "final mile" problem of taking a containerized service and making it available to the operations team.
* Now that containers are running, how do we inventory what we have and the state that it is in?
* Demo Host, Container and Search pages as a means of inventory management.
* When our monitoring tells us something is wrong on a host, what do we do?
* How do services find each other?
* Discuss how StackEngine will provide service discovery.
* Provide a roadmap overview
Some technologies are tools of the DevOps trade. Chef, Jenkins, Vagrant and Zookeeper are all tools that can be used for huge leverage and impact by the right people. Rarely, however, is there a technology that *enables* the practice of DevOps. The advent of the cloud and disposable infrastructure is one example. Docker is in this second, more rarified class.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Fueling AI with Great Data with Airbyte WebinarZilliz
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.
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
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.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
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.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
2. 04/20/2018 - STOP THE WRONG
BOYD HEMPHILL - CTO - VICTORY CTO
▸ Community guy …
▸ Austin DevOps Meetup
▸ DevOps Days Austin
▸ Container Days Austin
▸ Docker Austin
▸ Former - Austin PHP Meetup Host
▸ Former - Austin MySql Meetup
▸ Developer, DBA, Ops, Director, Exec
▸ I was The Director of DevOps. Be sure to pwn me
after this talk!
▸ Extroverted Nerd
6. 04/20/2018 - STOP THE WRONG
RULES OF ENGAGEMENT
▸ You will be uncomfortable - Good
▸ You will want to yell at me - Good
7. 04/20/2018 - STOP THE WRONG
RULES OF ENGAGEMENT
▸ You will be uncomfortable - Good
▸ You will want to yell at me - Good
▸ You will think I am wrong - I think
you’re wrong too, but I have the
mic
8. 04/20/2018 - STOP THE WRONG
RULES OF ENGAGEMENT
▸ You will be uncomfortable - Good
▸ You will want to yell at me - Good
▸ You will think I am wrong - I think
you’re wrong too, but I have the
mic
▸ I don’t necessarily believe what I
am saying. But I will argue it with
you to our mutual benefit.
9. 04/20/2018 - STOP THE WRONG
RULES OF ENGAGEMENT
▸ You will be uncomfortable - Good
▸ You will want to yell at me - Good
▸ You will think I am wrong - I think
you’re wrong too, but I have the
mic
▸ I don’t necessarily believe what I
am saying. But I will argue it with
you to our mutual benefit.
▸ Don’t get your knickers in a twist
10. THERE ARE INFINITE WAYS TO SCREW
UP. THERE ARE ABOUT A DOZEN THAT
ARE RIGHT THEREFORE, THE
PROBABILITY OF GETTING IT RIGHT BY
CHANCE = 0.
Math
04/20/2018 - STOP THE WRONG
12. 04/20/2018 - STOP THE WRONG
AGILE DEVELOPMENT IS A PHILOSOPHY
▸ Agile has a manifesto.
13. 04/20/2018 - STOP THE WRONG
AGILE DEVELOPMENT IS A PHILOSOPHY
▸ Agile has a manifesto.
▸ Agile can be applied in many
different situations.
14. 04/20/2018 - STOP THE WRONG
AGILE DEVELOPMENT IS A PHILOSOPHY
▸ Agile has a manifesto.
▸ Agile can be applied in many
different situations.
▸ There is no department of the
Agiles
15. 04/20/2018 - STOP THE WRONG
AGILE DEVELOPMENT IS A PHILOSOPHY
▸ Agile has a manifesto.
▸ Agile can be applied in many
different situations.
▸ There is no department of the
Agiles
▸ Scrum is one model of the Agile
philosophy that is frequently
implemented
16. 04/20/2018 - STOP THE WRONG
AGILE DEVELOPMENT IS A PHILOSOPHY
▸ Agile has a manifesto.
▸ Agile can be applied in many
different situations.
▸ There is no department of the Agiles
▸ Scrum is one model of the Agile
philosophy that is frequently
implemented
▸ Scrum sucks if your on an ops team.
Agile does not.
17. SCRUM IS A TRAIL OF TEARS ON
OPS TEAMS. AGILE IS A BREATH OF
LIFE. THESE ARE NOT A
CONTRADICTORY STATEMENTS.
School of Hard Knocks
04/20/2018 - STOP THE WRONG
18. 04/20/2018 - STOP THE WRONG
DEVOPS IS A PHILOSOPHY
▸ Philosophies have pillars.
19. 04/20/2018 - STOP THE WRONG
DEVOPS IS A PHILOSOPHY
▸ Philosophies have pillars.
▸ C.A.L.M.S.
20. 04/20/2018 - STOP THE WRONG
DEVOPS IS A PHILOSOPHY
▸ Philosophies have pillars.
▸ C.A.L.M.S.
▸ I really would rather a fabric
metaphor. Each pillar is really
strands of interwoven fabric. The
weave determines the strength of
the model.
21. DEVOPS IS THE WAY A TECHNOLOGY
PRACTICE EMBEDS ITSELF IN AN
ORGANIZATION TO THE BENEFIT OF
THAT ORGANIZATION.
Some Know-it-all
04/20/2018 - STOP THE WRONG
23. 04/20/2018 - STOP THE WRONG
THINKING DEVOPS
▸ I have a hammer, so everything
looks like a … (Jenkins)
24. 04/20/2018 - STOP THE WRONG
THINKING DEVOPS
▸ I have a hammer, so everything
looks like a … (Jenkins)
▸ Why are you implementing a CI
tool? - Philosophy
25. 04/20/2018 - STOP THE WRONG
THINKING DEVOPS
▸ I have a hammer, so everything
looks like a … (Jenkins)
▸ Why are you implementing a CI
tool? - Philosophy
▸ Does it align with your philosophy?
- Model
26. 04/20/2018 - STOP THE WRONG
THINKING DEVOPS
▸ I have a hammer, so everything
looks like a … (Jenkins)
▸ Why are you implementing a CI
tool? - Philosophy
▸ Does it align with your philosophy?
- Model
▸ How will you make it happen? -
Implementation
27. 04/20/2018 - STOP THE WRONG
THINKING DEVOPS
▸ I have a hammer, so everything looks
like a … (Jenkins)
▸ Why are you implementing a CI tool?
- Philosophy
▸ Does it align with your philosophy? -
Model
▸ How will you implement it? -
Implementation
▸ What tool should it be? - Tool
(https://bit.ly/1fkKn1Q)
28. IF YOU DON’T KNOW WHAT YOU ARE
DOING, AUTOMATION ONLY MAKES
YOU DO IT FASTER.
Some Know-it-all
04/20/2018 - STOP THE WRONG
29. 04/20/2018 - STOP THE WRONG
JENKINS IS A SIRENS CALL
▸ Swiss army knife allure. Common.
30. 04/20/2018 - STOP THE WRONG
JENKINS IS A SIRENS CALL
▸ Swiss army knife allure. Common.
▸ Doesn’t allow the build to be
described in code
31. 04/20/2018 - STOP THE WRONG
JENKINS IS A SIRENS CALL
▸ Swiss army knife allure. Common.
▸ Doesn’t allow the build to be
described in code
▸ Creates immense friction for build
management, ownership and
change.
32. KNOWLEDGE OF A TOOL HELPS TO
UNDERSTAND THE BROADER
PROBLEM. DON’T USE CRAP
BECAUSE YOU KNOW HOW TO POOP.
Some Know-it-all
04/20/2018 - STOP THE WRONG
33. 04/20/2018 - STOP THE WRONG
RUNDECK NEEDS A REWRITE
▸ Job code stored as XML via the
software on disk.
34. 04/20/2018 - STOP THE WRONG
RUNDECK NEEDS A REWRITE
▸ Job code stored as XML via the
software on disk.
▸ No developer workflow
35. 04/20/2018 - STOP THE WRONG
RUNDECK NEEDS A REWRITE
▸ Job code stored as XML via the
software on disk.
▸ No developer workflow
▸ This is the worst of old school
systems administration - hack, cut,
paste, pray.
36. 04/20/2018 - STOP THE WRONG
RUNDECK NEEDS A REWRITE
▸ Job code stored as XML via the
software on disk.
▸ No developer workflow
▸ This is the worst of old school
systems administration - hack, cut,
paste, pray.
▸ What would a tool born of DevOps
philosophy really look like?
37. DEVOPS ASSUMES THE AGILE
PHILOSOPHY AND USES THE
MODELS OF WORKFLOWS TYPICAL
TO DEVELOPERS.
That Same Know-it-all
04/20/2018 - STOP THE WRONG
39. 04/20/2018 - STOP THE WRONG
YOU ONLY NEED TWO SKILLS …
▸ The ability to own your outcomes
▸ Owning outcomes your not done
until the feature is in production,
defect free and driving revenue.
40. 04/20/2018 - STOP THE WRONG
YOU ONLY NEED TWO SKILLS …
▸ The ability to own your outcomes
▸ Owning outcomes your not done
until the feature is in production,
defect free and driving revenue.
▸ The ability to rapidly learn and
implement
▸ Implement implies adhering to the
philosophy driving your
organization.
41. SKILL ACQUISITION IS YOUR
PRIMARY SKILL.
Paul Czarkowski
04/20/2018 - STOP THE WRONG
42. 04/20/2018 - STOP THE WRONG
GO FORTH AND DEVOP
▸ Once you have chosen a way
forward learn why and how others
did it.
43. 04/20/2018 - STOP THE WRONG
GO FORTH AND DEVOP
▸ Once you have chosen a way
forward learn why and how others
did it.
▸ Learn about common mistakes.
44. 04/20/2018 - STOP THE WRONG
GO FORTH AND DEVOP
▸ Once you have chosen a way
forward learn why and how others
did it.
▸ Learn about common mistakes.
▸ Get certified while doing the first
implementation.
45. 04/20/2018 - STOP THE WRONG
GO FORTH AND DEVOP
▸ Once you have chosen a way
forward learn why and how others
did it.
▸ Learn about common mistakes.
▸ Get certified while doing the first
implementation.
▸ Start certification bounties in your
organization.
46. IF YOU ARE NOT A LEARNING
ORGANIZATION YOU ARE LOSING TO
ONE.
Andrew Clay Shafer (knows a lot!)
04/20/2018 - STOP THE WRONG
48. 04/20/2018 - STOP THE WRONG
SILO EFFECTS - 1
▸ Developer introduces a
performance killing bug.
49. 04/20/2018 - STOP THE WRONG
SILO EFFECTS - 1
▸ Developer introduces a
performance killing bug.
▸ Site crashes.
50. 04/20/2018 - STOP THE WRONG
SILO EFFECTS - 1
▸ Developer introduces a
performance killing bug.
▸ Site crashes.
▸ “DevOps” (see how stupid that
term is in this context) wakes up
and solves the problem
51. 04/20/2018 - STOP THE WRONG
SILO EFFECTS - 1
▸ Developer introduces a
performance killing bug.
▸ Site crashes.
▸ “DevOps” (see how stupid that
term is in this context) wakes up
and solves the problem
▸ Developer sleeps through the
night.
52. DEVELOPERS ARE SELF ABSORBED
ASSHOLES WHO ARE TOO LAZY TO
ENSURE THEIR SHIT WORKS.
Ops who can’t Dev
04/20/2018 - STOP THE WRONG
53. 04/20/2018 - STOP THE WRONG
SILO EFFECTS - 2
▸ A developer needs infrastructure
to do performance testing.
54. 04/20/2018 - STOP THE WRONG
SILO EFFECTS - 2
▸ Developer needs infrastructure to
do performance testing.
▸ He launches infrastructure and
tests.
55. 04/20/2018 - STOP THE WRONG
SILO EFFECTS - 2
▸ Developer needs infrastructure to
do performance testing.
▸ He launches infrastructure and
tests.
▸ He leaves it up.
56. 04/20/2018 - STOP THE WRONG
SILO EFFECTS - 2
▸ Developer needs infrastructure to
do performance testing.
▸ He launches infrastructure and
tests.
▸ He leaves it up.
▸ Director of DevOps budget is
blown. She jumps off a ledge.
57. DEVELOPERS ARE SELF ABSORBED
ASSHOLES WHO ARE TOO LAZY TO
ENSURE THEIR RESPONSIBILITIES.
Mangers who’ve never developed in the cloud.
04/20/2018 - STOP THE WRONG
58. 04/20/2018 - STOP THE WRONG
CULTURE OF EMPATHY
▸ Developers introduce error to the
system because they are human,
not because they are jerks.
59. 04/20/2018 - STOP THE WRONG
CULTURE OF EMPATHY
▸ Developers introduce error to the
system because they are human,
not because they are jerks.
▸ Developers have no incentive to
care and no real view of the
consequences.
60. 04/20/2018 - STOP THE WRONG
CULTURE OF EMPATHY
▸ Developers introduce error to the
system because they are human,
not because they are jerks.
▸ Developers have no incentive to
care and no real view of the
consequences.
▸ Saying, “You developers should
care” is not a solution. It is
codependent and stupid.
61. 04/20/2018 - STOP THE WRONG
CULTURE OF EMPATHY
▸ Developers introduce error to the
system because they are human,
not because they are jerks.
▸ Developers have no incentive to
care and no real view of the
consequences.
▸ Saying, “You developers should
care” is not a solution. It is
codependent and stupid.
▸ Real world pain is a solution.
62. NOTHING SAYS, “I CARE,” LIKE,
“OUCH”. BUILD A CULTURE OF
EMAPTHY.
That Know-it-all (again)
04/20/2018 - STOP THE WRONG
65. 04/20/2018 - STOP THE WRONG
REASONS TO NOT TO …
▸ Developer: “But I don’t have the
right access”
66. 04/20/2018 - STOP THE WRONG
REASONS TO NOT TO …
▸ Developer: “But I don’t have the
right access”
▸ Developer: “I don’t know what to
do.”
67. 04/20/2018 - STOP THE WRONG
REASONS TO NOT TO …
▸ Developer: “But I don’t have the
right access”
▸ Developer: “I don’t know what to
do.”
▸ DevOps (dumb title, yeah?):
“Those snowflakes will just harsh
my mellow.”
68. 04/20/2018 - STOP THE WRONG
REASONS TO NOT TO …
▸ Developer: “But I don’t have the
right access”
▸ Developer: “I don’t know what to
do.”
▸ DevOps (dumb title, yeah?):
“Those snowflakes will just harsh
my mellow.”
▸ Developer: “That’s not what I
signed up for!”
69. SOLVE THE BLOODY PROBLEM! WE
ARE ENGINEERS RIGHT? WE SORTA
GET PAID TO SOLVE PROBLEMS?
That Know-it-all (again)
04/20/2018 - STOP THE WRONG
70. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“BUT I DON’T HAVE THE RIGHT ACCESS”
▸ Not the point.
71. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“BUT I DON’T HAVE THE RIGHT ACCESS”
▸ Not the point.
▸ When there is a production
incident, nobody’s paycheck is
getting funded.
72. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“BUT I DON’T HAVE THE RIGHT ACCESS”
▸ Not the point.
▸ When there is a production
incident, nobody’s paycheck is
getting funded.
▸ Your simple ability to triage an
event just saved some poor
burned-out soul from doing it for
the 1000th time.
73. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“BUT I DON’T HAVE THE RIGHT ACCESS”
▸ Not the point.
▸ When there is a production incident,
nobody’s paycheck is getting funded.
▸ Your simple ability to determine it is
not an incident worth waking up at
the team just saved some poor
burned-out soul from doing it for the
1000th time.
▸ You don’t want to be the person who
introduced the fault.
74. ACCESS IS ONLY ONE ASPECT OF A
SOLUTION TO A PRODUCTION
INCIDENT. OFTEN KNOWLEDGE OF
THE CODE IS JUST AS IMPORTANT.
An Ops who Devs
04/20/2018 - STOP THE WRONG
75. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“I DON’T KNOW WHAT TO DO.”
▸ Not the point.
76. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“I DON’T KNOW WHAT TO DO.”
▸ Not the point.
▸ Remember the thing about
learning organizations?
77. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“I DON’T KNOW WHAT TO DO.”
▸ Not the point.
▸ Remember the thing about
learning organizations?
▸ You gain a very valuable skill set:
incident response team
78. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“I DON’T KNOW WHAT TO DO.”
▸ Not the point.
▸ Remember the thing about
learning organizations?
▸ You gain a very valuable skill set:
incident response team
▸ You gain a valuable skill set: use
and configuration of monitoring
and logging.
79. WE IN OPS DON’T KNOW EITHER.
BUT IT STILL NEEDS TO GET FIXED.
IF WE KNEW WHAT WAS WRONG, IT
WOULDN’T HAVE HAPPENED.
A cry for help
04/20/2018 - STOP THE WRONG
80. 04/20/2018 - STOP THE WRONG
DEVOPS (DUMB TITLE, YEAH?):
“THOSE SNOWFLAKES WILL JUST HARSH MY MELLOW”
▸ Strike one. This person may need
to go.
81. 04/20/2018 - STOP THE WRONG
DEVOPS (DUMB TITLE, YEAH?):
“THOSE SNOWFLAKES WILL JUST HARSH MY MELLOW”
▸ Strike one. This person may need
to go.
▸ The “snowflakes” are intelligent
professionals who can learn to
read graphs and log messages.
82. 04/20/2018 - STOP THE WRONG
DEVOPS (DUMB TITLE, YEAH?):
“THOSE SNOWFLAKES WILL JUST HARSH MY MELLOW”
▸ Strike one. This person may need
to go.
▸ The “snowflakes” are intelligent
professionals who can learn to
read graphs and log messages.
▸ The “snowflakes” can be taught to
lead the incident so you can work
the incident.
83. 04/20/2018 - STOP THE WRONG
DEVOPS (DUMB TITLE, YEAH?):
“THOSE SNOWFLAKES WILL JUST HARSH MY MELLOW”
▸ Strike one. This person may need
to go.
▸ The “snowflakes” are intelligent
professionals who can learn to
read graphs and log messages.
▸ The “snowflakes” can be taught to
run the incident so you can work
the incident.
▸ Boredom is the goal. Hero’s mean
your organization is losing.
84. DON’T MOVE MY CHEESE.
Some angry dude in the unemployment line.
04/20/2018 - STOP THE WRONG
85. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“THAT’S NOT WHAT I SIGNED UP FOR”
▸ Strike one. This person may need
to go.
86. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“THAT’S NOT WHAT I SIGNED UP FOR”
▸ Strike one. This person may need
to go.
▸ Check the clause in your job
description that reads, “And other
duties as assigned …”
87. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“THAT’S NOT WHAT I SIGNED UP FOR”
▸ Strike one. This person may need
to go.
▸ Check the clause in your job
description that reads, “And other
duties as assigned …”
▸ You can learn this stuff now or risk
unemployment later because you
cannot get through an interview
without it.
88. 04/20/2018 - STOP THE WRONG
DEVELOPER:
“THAT’S NOT WHAT I SIGNED UP FOR”
▸ Strike one. This person may need
to go.
▸ Check the clause in your job
description that reads, “And other
duties as assigned …”
▸ You can learn this stuff now or risk
unemployment later because you
cannot get through an interview
without it.
▸ World’s changing, get on board.
89. WHATEVER DUTIES YOU THINK YOU
HAVE TODAY WILL BE DIFFERENT IN
18 MONTHS. (UMM ….
SERVERLESS … SHHH)
The Future
04/20/2018 - STOP THE WRONG
91. 04/20/2018 - STOP THE WRONG
SELF ACTUALIZATION
▸ Developer - lines of code written.
92. 04/20/2018 - STOP THE WRONG
SELF ACTUALIZATION
▸ Developer - lines of code written.
▸ Ops - Love to help out on one-off
problems.
93. 04/20/2018 - STOP THE WRONG
SELF ACTUALIZATION
▸ Developer - lines of code written.
▸ Ops - Love to help out on one-off
problems.
▸ Someone has to create the features
and someone must ensure the
underlying systems are secure and
available.
94. 04/20/2018 - STOP THE WRONG
SELF ACTUALIZATION
▸ Developer - lines of code written.
▸ Ops - Love to help out on one-off
problems.
▸ Someone has to create the features
and someone must ensure the
underlying systems are secure and
available.
▸ Both should be responsible for that
production outcome.
95. PASSIONS SHOULD ALIGN WITH
INCENTIVES AND NATURAL
CONSEQUENCES. ESPECIALLY IN THE
PRODUCTION ENVIRONMENT.
The Future
04/20/2018 - STOP THE WRONG
96. 04/20/2018 - STOP THE WRONG
SKILLS AND CONSEQUENCES
▸ Developer - create features,
introduce defects
97. 04/20/2018 - STOP THE WRONG
SKILLS AND CONSEQUENCES
▸ Developer - create features,
introduce defects
▸ Ops - Problem Solvers, abhor risk
98. 04/20/2018 - STOP THE WRONG
SKILLS AND CONSEQUENCES
▸ Developer - create features,
introduce defects
▸ Ops - Problem Solvers, abhor risk
▸ There is a risk in humans
introducing change.
99. 04/20/2018 - STOP THE WRONG
SKILLS AND CONSEQUENCES
▸ Developer - create features,
introduce defects
▸ Ops - Problem Solvers, abhor risk
▸ There is a risk in humans
introducing change.
▸ There is a need to engineer the risk
to a minimum. This outcome is
owned by both skills. (e.g. unit
tests & monitoring)
100. RISK IS JUST ANOTHER
ENGINEERING PROBLEM.
ENGINEERING PROBLEMS ARE ALSO
KNOW AS JOB SECURITY.
The practical know-it-all
04/20/2018 - STOP THE WRONG
101. 04/20/2018 - STOP THE WRONG
ACCESS
▸ Developer - only in their local
environment, never production
102. 04/20/2018 - STOP THE WRONG
ACCESS
▸ Developer - only in their local
environment, never production
▸ Ops - Thinking about production,
never about the development
environment.
103. 04/20/2018 - STOP THE WRONG
ACCESS
▸ Developer - only in their local
environment, never production
▸ Ops - Thinking about production,
never about the development
environment.
▸ Environment parity is a key success
metric.
104. PRODUCTION CANNOT PRODUCE
MORE MONEY, IF DEVELOPERS
CANNOT EFFECTIVELY DELIVER NEW
FEATURES TO MARKET.
DevOps
04/20/2018 - STOP THE WRONG
105. 04/20/2018 - STOP THE WRONG
A TEAM IS A COLLECTION OF SKILLS
▸ In soccer there are goalies,
defenders, mid fielders and
strikers. The are on the same field
at the same time with responsibility
for the same outcome.
106. 04/20/2018 - STOP THE WRONG
A TECH TEAM IS A COLLECTION OF SKILLS
▸ In soccer there are goalies,
defenders, mid fielders and
strikers. The are on the same field
at the same time with responsibility
for the same outcome.
▸ In tech there are multiple teams on
the same field with multiple
orthogonal outcomes.
107. 04/20/2018 - STOP THE WRONG
A TEAM IS A COLLECTION OF SKILLS
▸ In soccer there are goalies,
defenders, mid fielders and
strikers. The are on the same field
at the same time with responsibility
for the same outcome.
▸ In tech there are multiple teams on
the same field with multiple
orthogonal outcomes.
▸ Which scenario makes more
sense?
108. 04/20/2018 - STOP THE WRONG
A TEAM IS A COLLECTION OF SKILLS
▸ In soccer there are goalies, defenders,
mid fielders and strikers. The are on
the same field at the same time with
responsibility for the same outcome.
▸ In tech there are multiple teams on the
same field with multiple orthogonal
outcomes.
▸ Which scenario makes more sense?
▸ Note that is not the same as, “Which is
easier, more convenient or
comfortable?” - That is what PTO is for.
109. ANY ORG THAT DESIGNS A SYSTEM
WILL PRODUCE A DESIGN WHOSE
STRUCTURE IS A COPY OF THE ORGS
COMMUNICATION STRUCTURE.
Conways Law
04/20/2018 - STOP THE WRONG
110. 04/20/2018 - STOP THE WRONG
ENGINEERS HAVE PERSONALITIES
▸ Makers - engineers with a
penchant for creating features for
the system.
111. 04/20/2018 - STOP THE WRONG
ENGINEERS HAVE PERSONALITIES
▸ Makers - engineers with a
penchant for creating features for
the system.
▸ Fixers - engineers with a penchant
for finding flaws in the system and
correcting them.
112. 04/20/2018 - STOP THE WRONG
ENGINEERS HAVE PERSONALITIES
▸ Makers - engineers with a
penchant for creating features for
the system.
▸ Fixers - engineers with a penchant
for finding flaws in the system and
correcting them.
▸ Operators - engineers concerned
with the availability, stability and
performance of the system.
113. 04/20/2018 - STOP THE WRONG
ENGINEERS HAVE PERSONALITIES
▸ Makers - engineers with a penchant
for creating features for the system.
▸ Fixers - engineers with a penchant for
finding flaws in the system and
correcting them.
▸ Operators - engineers concerned with
the availability, stability and
performance of the system.
▸ Penetrators - engineers concerned
with penetrating the system and
plugging its holes.
114. TO BE EFFECTIVE A TEAM MUST
HAVE THE PERSONALITIES, ACCESS
AND MOTIVATION TO DELIVER.
Know-it-all
04/20/2018 - STOP THE WRONG
115. 04/20/2018 - STOP THE WRONG
DOING IT WRONG
▸ DevOps Engineers
▸ Tool driven implementations
▸ Scrum is Agile … SRE is
DevOps
▸ Failing at knowing everything,
hoarding knowledge.
▸ DevOps Department
▸ Teams separated by skill set.
▸ Philosophy in practice
▸ Values driven implementations
▸ Assessing desired outcomes and
building a practice based on
organizational culture.
▸ Building the need to learn into
everything you do
▸ Culture of share responsibility.
▸ Teams separated by system
boundaries.
DEVOPS