Fear and Loathing in Systems Administration
•
0 likes•58 views
This document summarizes a presentation titled "Overcome DevOps Fear and Loathing". The presentation was given by Harold Grunenwald, an independent consultant. It aimed to address fears around DevOps implementation. Some key points discussed included clarifying roles between systems engineers and operations teams, speaking each other's languages, properly scoping projects based on staffing and priorities, and how an organization's structure can influence its system designs according to Conway's Law. The presentation also touched on common disconnects that occur and ways to overcome fears through improved communication and collaboration between teams.
Report
Share
Report
Share
Download to read offline
Recommended
The Business of Agile: Better, Faster, Cheaper
Ryan Ripley relates that during his last agile transformation project, a key stakeholder asked, “Why are we adopting agile?” Ryan talked about increasing quality, delivering software sooner, and fostering a more collaborative relationship with business partners. After a few moments, the stakeholder raised his hand and said, “I get all that. But how is all of this agile stuff any better, faster, or cheaper than what we do today?” Ryan says that leaders must answer the better, faster, cheaper question if they want their agile transformation and associated projects to move forward. To prepare for this critical question, Ryan explores how better, faster, cheaper translates in an agile organization. Take away experiments to use with your agile teams to define better in your organization, an understanding of how agile helps teams deliver value faster to their stakeholders, and how working in an agile way can make business costs cheaper by reducing team turnover, enhancing learning through pairing, and reducing overall costs of product ownership.
DevOps Is More than Dev and Ops: It’s about Tearing Down Walls
The word DevOps is quickly becoming the new Agile—an overused word that has lost its meaning. Cutting through the jargon, Lee Eason gets to the heart of what DevOps means, where it came from, and why it is crucial for your company to embrace it. If you want to deliver on the promise of agile—to improve quality and reduce time to market—you must understand and implement DevOps. Lee shares three mechanisms of change—enablement, mentoring, and coaching—you can use to drive the transformation, as well as key performance indicators to measure your progress along the way. Learn where the big technical roadblocks lie, why they exist in your company, and how to navigate them successfully. Finally, Lee shares key benefits you can expect with your shift to DevOps—the effect on consumers’ loyalty, developer satisfaction, systems uptime, and software quality.
Five XP Practices for Agile Development
David Bernstein says that the core of Extreme Programming (XP) is comprised of five development practices: automating the build for continuously integrating software as it is written, collaborating with team members through pair programming, practicing agile design skills that enable testability, using test-first development to drive design, and refactoring code to reduce technical debt. Together, these five technical practices are essential for sustained success with XP and for many of the best agile teams. However, quite a few agile teams haven’t been exposed to some or all of these practices. David explores these XP practices, discusses how to use them to reduce risk, and explains how to build quality in at every level of the development process. He makes the business case for these technical practices by showing how they address the inherent risks and challenges in building software. David then looks at how practices from XP address the core issues of software development by helping us “build the right thing” and “build the thing right.”
Build Adaptable Teams: The Marine Corps Way
Shrinking budgets, increased workloads, and ever-changing demands challenge today’s product teams to adapt and learn to do more with less. Since its birth in 1775, the United States Marine Corps has faced similar trials. The key to the Corps’ survival—not unlike that of a product team—has been its ability to adapt to change. Anne Steiner uses the Corps’ leadership philosophy and its training techniques and her experience as a Marine Corps non-commissioned officer as a framework for understanding how Marines adapt, decentralize decision making, and build leaders at all levels. Through stories and examples, Anne draws parallels between Marine Corps techniques and how we work in the software industry. Learn to apply Marine Corps concepts like commander’s intent to enhance our traditional idea of product ownership and small unit leadership in lieu of centralized management. Whether your team is agile or not, you’ll leave with a new perspective on planning, empowerment, and team dynamics—a perspective that can help people at all levels lead and excel through change.
Transform Organizational Culture for DevOps Success
An organization’s ability to adopt a DevOps approach for software delivery often hinges on a cultural transformation that may be more difficult than technology issues. The keys to success are change supported from the top down, combined with people on the front line who are willing to experiment, fail fast, continuously learn, and openly collaborate in a blameless and fun working environment. When done right, the result is a renewed level of trust between the people involved and the organization they work for. Join Al Wagner as he shares how teams can increase the level of trust across people, process, and tools. Learn how to improve with DevOps while executing in a fun work environment. Hear about high-performing organizations who have embraced culture change as well as the impact on people in organizations who haven’t. If you are thinking about embarking on your own DevOps journey, remember—culture is key. And learning the best practices from others will help you start off right.
Your Agile Team Needs a Therapist
Imagine you’re on an agile development team—and something feels weird. People disagree constantly, and when they finally do agree, no one commits to deliver the solution. Vocal team members dominate the conversation. You don’t trust your teammates. They don’t trust you. This isn’t a team. It’s just a group of people. Does this sound familiar? Because people are people—not interchangeable robots—building high-performing, self-organizing teams takes specific skills and a lot of work. In his experience working with agile teams, Robb Pieper has often taken on the role of therapist—or even an organizational marriage counselor—to break through the people problems that prevent teams from being successful. He discusses specific ideas and techniques for building trust, team building, trust issue debugging, and conflict mining to create and sustain high-performance teams. Robb believes every team needs someone to fill the role of helping coach people through the complicated issues that prevent teams from delivering more effectively together than separately. Can you be that person?
Agile Snafus: When Good Teams Go Bad
Agile done well can lead to great successes—rapid delivery of business and user value, high product quality, fast time to market, and engineering productivity. Agile done poorly leads to skepticism of the methodologies, distrust of the principles, and failure to deliver—in essence, a snafu [sna-foo]: a badly confused or ridiculous muddled situation. James Waletzky has gathered a set of snafus (anti-patterns) that pose challenges for organizations adopting agile. Set yourself up for success by understanding where teams go wrong with agile, complete with tips on how to avoid or fix the issues. James starts with a backlog of agile anti-patterns. Like any backlog, external inputs factor into the ranking of the items within it. We first vote on which topics are most interesting. James then proceeds through each topic in the backlog—until we run out of time. Some examples of items in the backlog may include lack of management commitment, no “done” definitions, and poor development practices to support agile. Discover how to deal with these problems so they don’t “snafu” you.
Recommended
The Business of Agile: Better, Faster, Cheaper
Ryan Ripley relates that during his last agile transformation project, a key stakeholder asked, “Why are we adopting agile?” Ryan talked about increasing quality, delivering software sooner, and fostering a more collaborative relationship with business partners. After a few moments, the stakeholder raised his hand and said, “I get all that. But how is all of this agile stuff any better, faster, or cheaper than what we do today?” Ryan says that leaders must answer the better, faster, cheaper question if they want their agile transformation and associated projects to move forward. To prepare for this critical question, Ryan explores how better, faster, cheaper translates in an agile organization. Take away experiments to use with your agile teams to define better in your organization, an understanding of how agile helps teams deliver value faster to their stakeholders, and how working in an agile way can make business costs cheaper by reducing team turnover, enhancing learning through pairing, and reducing overall costs of product ownership.
DevOps Is More than Dev and Ops: It’s about Tearing Down Walls
The word DevOps is quickly becoming the new Agile—an overused word that has lost its meaning. Cutting through the jargon, Lee Eason gets to the heart of what DevOps means, where it came from, and why it is crucial for your company to embrace it. If you want to deliver on the promise of agile—to improve quality and reduce time to market—you must understand and implement DevOps. Lee shares three mechanisms of change—enablement, mentoring, and coaching—you can use to drive the transformation, as well as key performance indicators to measure your progress along the way. Learn where the big technical roadblocks lie, why they exist in your company, and how to navigate them successfully. Finally, Lee shares key benefits you can expect with your shift to DevOps—the effect on consumers’ loyalty, developer satisfaction, systems uptime, and software quality.
Five XP Practices for Agile Development
David Bernstein says that the core of Extreme Programming (XP) is comprised of five development practices: automating the build for continuously integrating software as it is written, collaborating with team members through pair programming, practicing agile design skills that enable testability, using test-first development to drive design, and refactoring code to reduce technical debt. Together, these five technical practices are essential for sustained success with XP and for many of the best agile teams. However, quite a few agile teams haven’t been exposed to some or all of these practices. David explores these XP practices, discusses how to use them to reduce risk, and explains how to build quality in at every level of the development process. He makes the business case for these technical practices by showing how they address the inherent risks and challenges in building software. David then looks at how practices from XP address the core issues of software development by helping us “build the right thing” and “build the thing right.”
Build Adaptable Teams: The Marine Corps Way
Shrinking budgets, increased workloads, and ever-changing demands challenge today’s product teams to adapt and learn to do more with less. Since its birth in 1775, the United States Marine Corps has faced similar trials. The key to the Corps’ survival—not unlike that of a product team—has been its ability to adapt to change. Anne Steiner uses the Corps’ leadership philosophy and its training techniques and her experience as a Marine Corps non-commissioned officer as a framework for understanding how Marines adapt, decentralize decision making, and build leaders at all levels. Through stories and examples, Anne draws parallels between Marine Corps techniques and how we work in the software industry. Learn to apply Marine Corps concepts like commander’s intent to enhance our traditional idea of product ownership and small unit leadership in lieu of centralized management. Whether your team is agile or not, you’ll leave with a new perspective on planning, empowerment, and team dynamics—a perspective that can help people at all levels lead and excel through change.
Transform Organizational Culture for DevOps Success
An organization’s ability to adopt a DevOps approach for software delivery often hinges on a cultural transformation that may be more difficult than technology issues. The keys to success are change supported from the top down, combined with people on the front line who are willing to experiment, fail fast, continuously learn, and openly collaborate in a blameless and fun working environment. When done right, the result is a renewed level of trust between the people involved and the organization they work for. Join Al Wagner as he shares how teams can increase the level of trust across people, process, and tools. Learn how to improve with DevOps while executing in a fun work environment. Hear about high-performing organizations who have embraced culture change as well as the impact on people in organizations who haven’t. If you are thinking about embarking on your own DevOps journey, remember—culture is key. And learning the best practices from others will help you start off right.
Your Agile Team Needs a Therapist
Imagine you’re on an agile development team—and something feels weird. People disagree constantly, and when they finally do agree, no one commits to deliver the solution. Vocal team members dominate the conversation. You don’t trust your teammates. They don’t trust you. This isn’t a team. It’s just a group of people. Does this sound familiar? Because people are people—not interchangeable robots—building high-performing, self-organizing teams takes specific skills and a lot of work. In his experience working with agile teams, Robb Pieper has often taken on the role of therapist—or even an organizational marriage counselor—to break through the people problems that prevent teams from being successful. He discusses specific ideas and techniques for building trust, team building, trust issue debugging, and conflict mining to create and sustain high-performance teams. Robb believes every team needs someone to fill the role of helping coach people through the complicated issues that prevent teams from delivering more effectively together than separately. Can you be that person?
Agile Snafus: When Good Teams Go Bad
Agile done well can lead to great successes—rapid delivery of business and user value, high product quality, fast time to market, and engineering productivity. Agile done poorly leads to skepticism of the methodologies, distrust of the principles, and failure to deliver—in essence, a snafu [sna-foo]: a badly confused or ridiculous muddled situation. James Waletzky has gathered a set of snafus (anti-patterns) that pose challenges for organizations adopting agile. Set yourself up for success by understanding where teams go wrong with agile, complete with tips on how to avoid or fix the issues. James starts with a backlog of agile anti-patterns. Like any backlog, external inputs factor into the ranking of the items within it. We first vote on which topics are most interesting. James then proceeds through each topic in the backlog—until we run out of time. Some examples of items in the backlog may include lack of management commitment, no “done” definitions, and poor development practices to support agile. Discover how to deal with these problems so they don’t “snafu” you.
Step-by-Step Guide to Leading a Large-Scale Agile Transformation
A few years ago everyone wanted to know how to convince their executives to go agile. Today, executives are asking their teams how they'll make the transformation. We have made significant progress changing the hearts and minds of senior leadership, but executives now demand a greater level of assurance that the plan is actually going to work. Executives are tired of being told to trust the team and that everything will be okay. Executives want to know how agile is going to help make things better. Mike Cottmeyer begins by discussing the elements of an agile transformation business case and how to identify a meaningful value proposition for change. Next, he considers how to assess the organization and build an agile transformation strategy and roadmap that encourage an iterative and incremental approach to change. Finally, Mike explores the metrics and controls that help you know if you're on the right track. Explore the change management and engagement techniques necessary to make sure you are building meaningful organizational support as you engage the enterprise.
Testing and Measurement in DevOps: Find Solutions—Not More Problems
The promise of DevOps is to deliver new features faster following today’s best practices. However, blindly automating the delivery pipeline by installing Jenkins, Chef, and Docker without adapting test approaches will cause a great number of deployments to fail. While the tester’s role and testing are critical for the success of DevOps, the tester’s objective changes—from finding more defects to understanding the patterns that make deployments fail. Then, the job is to automate the detection of these patterns through quality gates into the pipeline. Using examples from Capital One, Verizon, and others, Andreas Grabner explains which technical metrics—# of SQLs, # Memory Allocations, # of Service Calls—to capture while testing in order to identify bad coding and architectural patterns earlier. In the DevOps world, you are no longer measured by number of tests created, executed, and problems reported; you are measured by your collaboration with development and operations, and the success rate of your team’s deliverables.
Agile Requirements—From Breadth to Depth
Requirements elicitation and documentation can be frustrating in an agile process. Some interpret the Agile Manifesto statement “working software over comprehensive documentation” to mean that no requirements documentation is warranted because the code documents the requirements. Others are concerned that if details of requirements are not treated equal to code, they are lost for future program modifications. Ken Pugh does not find this an either-or situation and describes ways to create requirements that are a balance between these two extremes. He shows how to develop requirements from epics that describe requirements broadly to developable units (stories), which are releasable units (minimum business increments/minimum viable features). With a brief introduction to acceptance tests, Ken explains how they can be used to capture the details of requirements. He demonstrates lightweight use cases as both a story exploration technique and an organizing mechanism for scenarios. Ken also illustrates the dependencies between individual requirements using the story map technique. Leave with practical approaches for developing your agile requirements from breadth-first to depth-last.
Testing Transformation in the IoT Era
In the next few years, when more than 20 billion devices will be connected to the Internet, many of us will be IoT testers—in one way or another. Jennifer Bonine explores new areas you will need to address in your testing, new testing skills for the IoT era, and how to innovate your technology strategies and processes to account for new vulnerabilities. Jennifer addresses current IoT trends that are taking shape and what you need to do to enhance your testing skills—and even your career. She explores the real “game changers”—data security, “things” test labs, open APIs, device types, and more—that IoT brings with it and how testing must adapt and progress to meet these challenges. Innovative technologies, test strategies, and QA processes are critical to IoT now and in the future. Join Jennifer to start your IoT testing transformation now.
Enable Your Workers … You’ll Be Amazed What They Can Do
It’s as true today as it was in 1986 when W. Edwards Deming published Out of the Crisis and wrote, “Remove barriers that rob people … of their right to pride of workmanship.” Companies everywhere implement processes, hire staff, and install tools to help them meet their business objectives. Many organizations strive to have engaged workers, efficient processes, and effective tools. However, Bob Jarvis says that, rather than doing the real work they were hired to perform, workers often end up spending too much time each day fighting obstacles related to those very processes, people, and tools. We recognize these organizations when we hear people say, “It’s hard to get things done around here.”Join Bob as he shares a framework to identify the real symptoms, an approach to presenting the results to management so they “get it,” and an implementation cycle to fix the root causes. Learn how to solve this problem and leave knowing how to become an expert in the framework and improve organizational outcomes.
The Lean Agile Portfolio
Agile practices continue to improve as organizations move forward with adoption and adaption. However, as they move forward, they often run into daunting challenges—coordinating projects with highly complex requirements and interdependencies; navigating highly political environments; and finding ways to fund, report, and integrate agile project work into existing organizational processes. Jamie Mades has found that the Lean Agile Portfolio bridges these gaps, applying lean product development flow principles to identify high-value initiatives and speed completion of work. It reduces risk and uncertainty using agile development practices to realize those initiatives. Jamie discusses how to break down silos across all areas, reduce the divide between agile practices and senior executive requirements, and improve collaboration. Using a $500M portfolio at a Fortune 100 company as an example, he reviews how they seamlessly integrated agile planning into the annual funding cycle and coordinated highly complex work across the organization. Join Jamie to learn where you need to drive changes and where you can adapt agile practices to meet organizational needs.
The Past, Present, and Future of Scrum
In the past two decades, Scrum has become the standard for agile development, used in some form today by 90 percent of agile teams. As Scrum starts its third decade, it’s not the fresh-faced process framework it once was. Yes, it has met—and dealt with—commercial, technical, philosophical, and practical challenges. Dave West discusses the past, present, and future of Scrum, using real data from more than 200,000 open assessments and 50,000 professional assessments to describe its challenges and evolution. Learn how to: (1) add the development infrastructure for continuous delivery; (2) define the systems engineering to manage the operational requirements from the start; and (3) create architectures to simplify the challenges of large-scale development. Learn how, in an industry that survives on the bleeding edge, there will continue to be a role for Scrum with its events, artifacts, and roles and how Scrum can continue to evolve.
Them’s the Rules: Using a Rules Engine to Wrangle Complexity
When dealing with complicated and ever-growing program conditions brought on by new business requirements, it's easy for what was once a small conditional block of code to grow to evaluating hundreds of unique conditions. Unfortunately, much like kudzu, that bad practice begins to creep into other areas of code. Micah Breedlove says that incorporating a rules engine to handle the conditional logic is a great way to reduce the code smells wafting from a multi-hundred line conditional. Converting the conditional into one small block of code which can retrieve and interpret a rule from another source—a database, XML, YAML, or some other repository—alleviates unnecessary logic. Micah presents different approaches to implementing a rules engine including event-driven and direct injection to give a better appreciation for its ability to simplify the growing complexity of conditional statements. Cleaning up conditional logic is an important gateway to writing more concise code which leads to an easier-to-maintain application.
Teamwork Tools: Movement Games for Collaboration and Creativity
Are you looking for new ways to invigorate your teams? Do retrospectives seem stale? Do story breakdown meetings feel flat? On the other hand, maybe your teams are humming and you’re looking for additional variety. The research is clear—movement matters, and play stimulates creativity. Join Andrew Smith as he takes you through a series of movement games that are lively and fun, while exploring how these practices can be applied to promote collaboration and creativity within teams. Discover how to use play to shift perspectives and enable new insights within your team. Learn about the importance of creating safety and trust—essential for getting all ideas and viewpoints out on the table. Additionally, see how to use these games for reflection and learning—as tools to understand your own style of collaboration and leadership. Leave with an experience of several movement games and a guide for putting them into practice with your teams.
Scaling Agile: Remembering Tolstoy’s Unhappy Family Analogy
While Agile has become mainstream at the team level with much research and practical experience, scaling agile to the enterprise is a topic of increasing interest and practice—with some successes and some spectacular failures. As Tolstoy wrote, “Happy families are all alike; each unhappy family is unhappy in its own way.” Mariya Breyter shares anti-patterns for scaling agile that you need to recognize quickly and change right away. Most agile scaling frameworks address agile processes and organizational structures. However, Mariya thinks it is time to look at agile scaling from the perspective of individual team members: developers, architects, testers, or any member of a cross-functional agile team. Using examples from multiple companies that she transitioned to agile at scale, Mariya describes how you can enhance your agile implementation at the enterprise level and avoid the pitfalls that can sink an enterprise agile program.
The Three Pillars Approach to an Agile Testing Strategy
Far too often, organizations focus solely on the development teams and their technical practices as their agile adoption strategy. And then there’s the near constant focus on acquiring development tools. Often the testing activity and the testing teams are left behind in agile adoption, or even worse, they’re simply along for the ride. This is not an effective transformation strategy. Join experienced agile coach Bob Galen as he shares the Three Pillars framework for establishing a balanced strategic plan for quality and testing. The Three Pillars focus on development and test automation, testing practices, and collaboration activities that ensure you have a balanced approach to agile testing. Specifically, Bob explores risk-based testing, exploratory testing, paired collaboration around agile requirements, agile test design, and TDD-BDD-functional testing automation as tactics within a balanced framework. Leave with ideas to immediately initiate or re-tool a much more effective and balanced agile testing strategy.
Conquer the Murky Waters of Test Automation
A solid test automation implementation is key to any foray into continuous delivery. Although the test automation waters may look peaceful and pristine, anyone who has jumped in to automate testing complex systems has found the waters to be troubled and murky. Tests take too long to run, they periodically break for mysterious reasons, or they fail to catch business critical problems. Over time this leads to automated tests becoming outdated and irrelevant. Brian Saylor has studied a number of test automation projects—and far too many lines of test code—to identify the fundamental concepts that are frequently missing. The test automation quagmire can be conquered by applying specific concepts. Brian uses a complex large scale website as an example and walks through identifying automated test goals, what tests should be automated and more importantly which should not, how to prioritize a test backlog, and how to identify good test code. Come away with practical fundamentals and coding guidelines to keep your own test automation project from sinking beneath the murky waters.
Build Fail-Proof Tests in Any Browser with Selenium
What happens when you have thousands of tests that run beautifully in Chrome but many of them fail in Internet Explorer? Unfortunately, this scenario is all too common for testers and remains a major sore point for teams tasked with getting software to work in any browser. Kevin Berg highlights how access to cloud-based Selenium Grids makes it easier than ever to run functional test suites in every imaginable operating system and browser combination. The result is less time and hassle adapting testing suites to each individual browser. Join Kevin as he shares hands-on insight on ways to optimize your tests for cross browser functional testing. Learn why cross browser testing is important, why some browsers behave differently from others, implicit vs. explicit waits, error handling, and using page objects to write more consistent tests.
Removing the Silos: When Agile, Lean, and DevOps Aren’t Enough
Your organization has adopted some combination of agile, lean, and DevOps practices, yet you have a sinking feeling that it’s not working the way everyone hoped it would. You’re wondering if it’s because you work for a very large organization and all this talk about small, cross-functional teams seems to conflict with your organizational charts. Your IT department is organized around functional disciplines such as the PMO, business analysis, Test Center of Excellence, and DevOps engineering. Do we need to blow up these structures in order to have successful agile/lean/DevOps transformations? Betty Zakheim says no. The trick is to remove the barriers to effective teamwork that these functional silos create. To understand where the barriers exist, Betty uses a combination of value stream mapping and an examination of the tools and techniques the functional disciplines employ. Using these techniques, she locates the inefficiencies in the handoffs among disciplines and introduces cross-lifecycle metrics that provide a better understanding of how effective your SDLC really is.
Data Warehouse Fundamento Para La Estrategia De Business Intelligence
Data Warehouse, Fundamento Para La Estrategia De Business Intelligence
Thierry de Pauw - Feature Branching considered Evil - Codemotion Milan 2018
With DVCSs branch creation became very easy, but it comes at a certain cost. Long living branches break the flow of the software delivery process, impacting stability and throughput. The session explores why teams are using feature branches, what problems are introduced by using them and what techniques exist to avoid them altogether. It explores exactly what's evil about feature branches, which is not necessarily the problems they introduce - but rather, the real reasons why teams are using them. After the session, you'll understand a different branching strategy and how it relates to CI/CD.
OSDC 2019 | Feature Branching considered Evil by Thierry de Pauw
With DVCSs, branch creation became very easy, but it comes at a certain cost. Long living branches break the flow of the software delivery process, impacting stability and throughput. The session explores why teams are using feature branches, what problems are introduced by using them and what techniques exist to avoid them altogether. It explores exactly what’s evil about feature branches, which is not necessarily the problems they introduce – but rather, the real reasons why teams are using them. After the session, you’ll understand a different branching strategy and how it relates to CI/CD.
Many to many: no man is an island
One of my sessions at Better Software 2011, held in Florence, Italy.
I meant to stress the relevance of social skills in deplying technical skills, as a company or as an individual.
More Related Content
Viewers also liked
Step-by-Step Guide to Leading a Large-Scale Agile Transformation
A few years ago everyone wanted to know how to convince their executives to go agile. Today, executives are asking their teams how they'll make the transformation. We have made significant progress changing the hearts and minds of senior leadership, but executives now demand a greater level of assurance that the plan is actually going to work. Executives are tired of being told to trust the team and that everything will be okay. Executives want to know how agile is going to help make things better. Mike Cottmeyer begins by discussing the elements of an agile transformation business case and how to identify a meaningful value proposition for change. Next, he considers how to assess the organization and build an agile transformation strategy and roadmap that encourage an iterative and incremental approach to change. Finally, Mike explores the metrics and controls that help you know if you're on the right track. Explore the change management and engagement techniques necessary to make sure you are building meaningful organizational support as you engage the enterprise.
Testing and Measurement in DevOps: Find Solutions—Not More Problems
The promise of DevOps is to deliver new features faster following today’s best practices. However, blindly automating the delivery pipeline by installing Jenkins, Chef, and Docker without adapting test approaches will cause a great number of deployments to fail. While the tester’s role and testing are critical for the success of DevOps, the tester’s objective changes—from finding more defects to understanding the patterns that make deployments fail. Then, the job is to automate the detection of these patterns through quality gates into the pipeline. Using examples from Capital One, Verizon, and others, Andreas Grabner explains which technical metrics—# of SQLs, # Memory Allocations, # of Service Calls—to capture while testing in order to identify bad coding and architectural patterns earlier. In the DevOps world, you are no longer measured by number of tests created, executed, and problems reported; you are measured by your collaboration with development and operations, and the success rate of your team’s deliverables.
Agile Requirements—From Breadth to Depth
Requirements elicitation and documentation can be frustrating in an agile process. Some interpret the Agile Manifesto statement “working software over comprehensive documentation” to mean that no requirements documentation is warranted because the code documents the requirements. Others are concerned that if details of requirements are not treated equal to code, they are lost for future program modifications. Ken Pugh does not find this an either-or situation and describes ways to create requirements that are a balance between these two extremes. He shows how to develop requirements from epics that describe requirements broadly to developable units (stories), which are releasable units (minimum business increments/minimum viable features). With a brief introduction to acceptance tests, Ken explains how they can be used to capture the details of requirements. He demonstrates lightweight use cases as both a story exploration technique and an organizing mechanism for scenarios. Ken also illustrates the dependencies between individual requirements using the story map technique. Leave with practical approaches for developing your agile requirements from breadth-first to depth-last.
Testing Transformation in the IoT Era
In the next few years, when more than 20 billion devices will be connected to the Internet, many of us will be IoT testers—in one way or another. Jennifer Bonine explores new areas you will need to address in your testing, new testing skills for the IoT era, and how to innovate your technology strategies and processes to account for new vulnerabilities. Jennifer addresses current IoT trends that are taking shape and what you need to do to enhance your testing skills—and even your career. She explores the real “game changers”—data security, “things” test labs, open APIs, device types, and more—that IoT brings with it and how testing must adapt and progress to meet these challenges. Innovative technologies, test strategies, and QA processes are critical to IoT now and in the future. Join Jennifer to start your IoT testing transformation now.
Enable Your Workers … You’ll Be Amazed What They Can Do
It’s as true today as it was in 1986 when W. Edwards Deming published Out of the Crisis and wrote, “Remove barriers that rob people … of their right to pride of workmanship.” Companies everywhere implement processes, hire staff, and install tools to help them meet their business objectives. Many organizations strive to have engaged workers, efficient processes, and effective tools. However, Bob Jarvis says that, rather than doing the real work they were hired to perform, workers often end up spending too much time each day fighting obstacles related to those very processes, people, and tools. We recognize these organizations when we hear people say, “It’s hard to get things done around here.”Join Bob as he shares a framework to identify the real symptoms, an approach to presenting the results to management so they “get it,” and an implementation cycle to fix the root causes. Learn how to solve this problem and leave knowing how to become an expert in the framework and improve organizational outcomes.
The Lean Agile Portfolio
Agile practices continue to improve as organizations move forward with adoption and adaption. However, as they move forward, they often run into daunting challenges—coordinating projects with highly complex requirements and interdependencies; navigating highly political environments; and finding ways to fund, report, and integrate agile project work into existing organizational processes. Jamie Mades has found that the Lean Agile Portfolio bridges these gaps, applying lean product development flow principles to identify high-value initiatives and speed completion of work. It reduces risk and uncertainty using agile development practices to realize those initiatives. Jamie discusses how to break down silos across all areas, reduce the divide between agile practices and senior executive requirements, and improve collaboration. Using a $500M portfolio at a Fortune 100 company as an example, he reviews how they seamlessly integrated agile planning into the annual funding cycle and coordinated highly complex work across the organization. Join Jamie to learn where you need to drive changes and where you can adapt agile practices to meet organizational needs.
The Past, Present, and Future of Scrum
In the past two decades, Scrum has become the standard for agile development, used in some form today by 90 percent of agile teams. As Scrum starts its third decade, it’s not the fresh-faced process framework it once was. Yes, it has met—and dealt with—commercial, technical, philosophical, and practical challenges. Dave West discusses the past, present, and future of Scrum, using real data from more than 200,000 open assessments and 50,000 professional assessments to describe its challenges and evolution. Learn how to: (1) add the development infrastructure for continuous delivery; (2) define the systems engineering to manage the operational requirements from the start; and (3) create architectures to simplify the challenges of large-scale development. Learn how, in an industry that survives on the bleeding edge, there will continue to be a role for Scrum with its events, artifacts, and roles and how Scrum can continue to evolve.
Them’s the Rules: Using a Rules Engine to Wrangle Complexity
When dealing with complicated and ever-growing program conditions brought on by new business requirements, it's easy for what was once a small conditional block of code to grow to evaluating hundreds of unique conditions. Unfortunately, much like kudzu, that bad practice begins to creep into other areas of code. Micah Breedlove says that incorporating a rules engine to handle the conditional logic is a great way to reduce the code smells wafting from a multi-hundred line conditional. Converting the conditional into one small block of code which can retrieve and interpret a rule from another source—a database, XML, YAML, or some other repository—alleviates unnecessary logic. Micah presents different approaches to implementing a rules engine including event-driven and direct injection to give a better appreciation for its ability to simplify the growing complexity of conditional statements. Cleaning up conditional logic is an important gateway to writing more concise code which leads to an easier-to-maintain application.
Teamwork Tools: Movement Games for Collaboration and Creativity
Are you looking for new ways to invigorate your teams? Do retrospectives seem stale? Do story breakdown meetings feel flat? On the other hand, maybe your teams are humming and you’re looking for additional variety. The research is clear—movement matters, and play stimulates creativity. Join Andrew Smith as he takes you through a series of movement games that are lively and fun, while exploring how these practices can be applied to promote collaboration and creativity within teams. Discover how to use play to shift perspectives and enable new insights within your team. Learn about the importance of creating safety and trust—essential for getting all ideas and viewpoints out on the table. Additionally, see how to use these games for reflection and learning—as tools to understand your own style of collaboration and leadership. Leave with an experience of several movement games and a guide for putting them into practice with your teams.
Scaling Agile: Remembering Tolstoy’s Unhappy Family Analogy
While Agile has become mainstream at the team level with much research and practical experience, scaling agile to the enterprise is a topic of increasing interest and practice—with some successes and some spectacular failures. As Tolstoy wrote, “Happy families are all alike; each unhappy family is unhappy in its own way.” Mariya Breyter shares anti-patterns for scaling agile that you need to recognize quickly and change right away. Most agile scaling frameworks address agile processes and organizational structures. However, Mariya thinks it is time to look at agile scaling from the perspective of individual team members: developers, architects, testers, or any member of a cross-functional agile team. Using examples from multiple companies that she transitioned to agile at scale, Mariya describes how you can enhance your agile implementation at the enterprise level and avoid the pitfalls that can sink an enterprise agile program.
The Three Pillars Approach to an Agile Testing Strategy
Far too often, organizations focus solely on the development teams and their technical practices as their agile adoption strategy. And then there’s the near constant focus on acquiring development tools. Often the testing activity and the testing teams are left behind in agile adoption, or even worse, they’re simply along for the ride. This is not an effective transformation strategy. Join experienced agile coach Bob Galen as he shares the Three Pillars framework for establishing a balanced strategic plan for quality and testing. The Three Pillars focus on development and test automation, testing practices, and collaboration activities that ensure you have a balanced approach to agile testing. Specifically, Bob explores risk-based testing, exploratory testing, paired collaboration around agile requirements, agile test design, and TDD-BDD-functional testing automation as tactics within a balanced framework. Leave with ideas to immediately initiate or re-tool a much more effective and balanced agile testing strategy.
Conquer the Murky Waters of Test Automation
A solid test automation implementation is key to any foray into continuous delivery. Although the test automation waters may look peaceful and pristine, anyone who has jumped in to automate testing complex systems has found the waters to be troubled and murky. Tests take too long to run, they periodically break for mysterious reasons, or they fail to catch business critical problems. Over time this leads to automated tests becoming outdated and irrelevant. Brian Saylor has studied a number of test automation projects—and far too many lines of test code—to identify the fundamental concepts that are frequently missing. The test automation quagmire can be conquered by applying specific concepts. Brian uses a complex large scale website as an example and walks through identifying automated test goals, what tests should be automated and more importantly which should not, how to prioritize a test backlog, and how to identify good test code. Come away with practical fundamentals and coding guidelines to keep your own test automation project from sinking beneath the murky waters.
Build Fail-Proof Tests in Any Browser with Selenium
What happens when you have thousands of tests that run beautifully in Chrome but many of them fail in Internet Explorer? Unfortunately, this scenario is all too common for testers and remains a major sore point for teams tasked with getting software to work in any browser. Kevin Berg highlights how access to cloud-based Selenium Grids makes it easier than ever to run functional test suites in every imaginable operating system and browser combination. The result is less time and hassle adapting testing suites to each individual browser. Join Kevin as he shares hands-on insight on ways to optimize your tests for cross browser functional testing. Learn why cross browser testing is important, why some browsers behave differently from others, implicit vs. explicit waits, error handling, and using page objects to write more consistent tests.
Removing the Silos: When Agile, Lean, and DevOps Aren’t Enough
Your organization has adopted some combination of agile, lean, and DevOps practices, yet you have a sinking feeling that it’s not working the way everyone hoped it would. You’re wondering if it’s because you work for a very large organization and all this talk about small, cross-functional teams seems to conflict with your organizational charts. Your IT department is organized around functional disciplines such as the PMO, business analysis, Test Center of Excellence, and DevOps engineering. Do we need to blow up these structures in order to have successful agile/lean/DevOps transformations? Betty Zakheim says no. The trick is to remove the barriers to effective teamwork that these functional silos create. To understand where the barriers exist, Betty uses a combination of value stream mapping and an examination of the tools and techniques the functional disciplines employ. Using these techniques, she locates the inefficiencies in the handoffs among disciplines and introduces cross-lifecycle metrics that provide a better understanding of how effective your SDLC really is.
Data Warehouse Fundamento Para La Estrategia De Business Intelligence
Data Warehouse, Fundamento Para La Estrategia De Business Intelligence
Viewers also liked (19)
Step-by-Step Guide to Leading a Large-Scale Agile Transformation
Step-by-Step Guide to Leading a Large-Scale Agile Transformation
Testing and Measurement in DevOps: Find Solutions—Not More Problems
Testing and Measurement in DevOps: Find Solutions—Not More Problems
Enable Your Workers … You’ll Be Amazed What They Can Do
Enable Your Workers … You’ll Be Amazed What They Can Do
Them’s the Rules: Using a Rules Engine to Wrangle Complexity
Them’s the Rules: Using a Rules Engine to Wrangle Complexity
Teamwork Tools: Movement Games for Collaboration and Creativity
Teamwork Tools: Movement Games for Collaboration and Creativity
Scaling Agile: Remembering Tolstoy’s Unhappy Family Analogy
Scaling Agile: Remembering Tolstoy’s Unhappy Family Analogy
The Three Pillars Approach to an Agile Testing Strategy
The Three Pillars Approach to an Agile Testing Strategy
Build Fail-Proof Tests in Any Browser with Selenium
Build Fail-Proof Tests in Any Browser with Selenium
Removing the Silos: When Agile, Lean, and DevOps Aren’t Enough
Removing the Silos: When Agile, Lean, and DevOps Aren’t Enough
Data Warehouse Fundamento Para La Estrategia De Business Intelligence
Data Warehouse Fundamento Para La Estrategia De Business Intelligence
Similar to Fear and Loathing in Systems Administration
Thierry de Pauw - Feature Branching considered Evil - Codemotion Milan 2018
With DVCSs branch creation became very easy, but it comes at a certain cost. Long living branches break the flow of the software delivery process, impacting stability and throughput. The session explores why teams are using feature branches, what problems are introduced by using them and what techniques exist to avoid them altogether. It explores exactly what's evil about feature branches, which is not necessarily the problems they introduce - but rather, the real reasons why teams are using them. After the session, you'll understand a different branching strategy and how it relates to CI/CD.
OSDC 2019 | Feature Branching considered Evil by Thierry de Pauw
With DVCSs, branch creation became very easy, but it comes at a certain cost. Long living branches break the flow of the software delivery process, impacting stability and throughput. The session explores why teams are using feature branches, what problems are introduced by using them and what techniques exist to avoid them altogether. It explores exactly what’s evil about feature branches, which is not necessarily the problems they introduce – but rather, the real reasons why teams are using them. After the session, you’ll understand a different branching strategy and how it relates to CI/CD.
Many to many: no man is an island
One of my sessions at Better Software 2011, held in Florence, Italy.
I meant to stress the relevance of social skills in deplying technical skills, as a company or as an individual.
Reasons to be cheerful - Fronteers 2010
My closing talk for this year's Fronteers conference in Amsterdam, the Netherlands about just how cool it is to be someone who builds things for the web.
Many to many: no man is an island
Every problem in software development will need a good interaction among people to bring about a solution. Where there is excellent software we will find a team able to communicate proficiently. Social intelligence, communities of expertise, user groups and open source projects are the real engine powering our growth as developers day by day.
Leverage your best: the others.
Many to many: no man is an island
Every problem in software development will need a good interaction among people to bring about a solution. Where there is excellent software we will find a team able to communicate proficiently. Social intelligence, communities of expertise, user groups and open source projects are the real engine powering our growth as developers day by day.
Leverage your best: the others.
Feedback loops between tooling and culture
Discussion of how tools technologists create impact culture, and how culture impacts those tools. Not really a standalone presentation but hopefully useful.
Co powinieneś wiedzieć na temat devops?f
What you should know about devops? Slides from presentation I gave during 10th J-Labs Academy meetup.
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...South Tyrol Free Software Conference
What makes an open-source project successful? How hard is it to add external people to an open project?
We at Nethesis have open source in our core with more than 400 public repositories that hold all of our company code. With the upcoming release of NethServer, we’re facing the excruciating question: how do we make it more appealing for developers?
Follow me in the changes we want to make to our processes to ease development and contributions, using big projects as examples and how even you can make a difference in the smallest of all codebases.From DevOps to NoOps how not to get Equifaxed Apidays
From DevOps to NoOps how not to get Equifaxed ApiDays Global Paris.
On the virtues of immutable infrastructure.
Open source and then some: An Introduction
Powerpoint presentation shown during GDG Surat's introductory session for Open Source.
Venue: NIT Surat
Dated: 08/10/2015
From 🤦 to 🐿️
Slides from my DevOpsExpo London talk "From oops to NoOps".
They tell you in these conferences that DevOps is not about tools, but about culture. And they are partially right. I am going to tell you that it’s not only about culture or tools but also abstractions.
It is a lot about how you see software and its value. About our mental model of what software is: how it runs, evolves, and interacts with the other facets of an enterprise.
We used to view software as code. As a state of code. Now we think about software as change, as a flow. A dynamic system where people, machines, and processes interact continuously.
At Platform.sh we spend a bunch of time asking ourselves not “How do you build?” - or even “How do you build consistently?” - but rather “What does it mean to consistently build in a world where change is good?” A world that lets you push security fixes into production as soon as they’re available because you don’t want to be an Equifax but you do want stability.
In this presentation, I will go over what we think software is and why having the right ideas about software will help you get your culture right and your tooling aligned, as well as gain in productivity, and general happiness and well-being.
Driven to distraction: Giles Colborne
The interfaces we're building need to work in distracting environments. And we need to figure out how to cope with users' tendency to get distracted. This presentation looks at how we might achieve that. And why, I think, it's the most serious problem facing interaction designers today.
LeadDev NYC 2022: Calling Out a Terrible On-call System
Molly Struve knew the system had to change if we wanted to continue growing and not lose our developer talent, but the question was how?
Corporate Open Source Anti-patterns
Talk originally given at FISL 2012 in Porto Alegre, Brazil. Video was on YouTube but regrettably taken down. Fortunately, I gave a slightly updated (and frankly, tighter and better produced) version of this at the Liferay Symposium in the fall of 2012: https://www.youtube.com/watch?v=Pm8P4oCIY3g
Software Development in a Funky Manner to meet client requirements best
Too often software development projects don't meet the client expectations.
What's causing this? How can we make that both the client (business side) and the developers communicate in such a way that both sides know what can be expected? Are new development practices the solution to realize top results?
See my blog post for more information: http://ow.ly/1rPaa
Many to many: no man is an island
My keynote at phpDay 2011 in Verona, Italy.
I meant to stress the relevance of social skills in deplying technical skills, as a company or as an individual.
This session was the most rated, with an average rating of 5 on 5:
http://joind.in/talk/view/2998
Similar to Fear and Loathing in Systems Administration (20)
Thierry de Pauw - Feature Branching considered Evil - Codemotion Milan 2018
Thierry de Pauw - Feature Branching considered Evil - Codemotion Milan 2018
OSDC 2019 | Feature Branching considered Evil by Thierry de Pauw
OSDC 2019 | Feature Branching considered Evil by Thierry de Pauw
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...
SFSCON23 - Tommaso Bailetti - Improving developer experience in Open Source P...
From DevOps to NoOps how not to get Equifaxed Apidays
From DevOps to NoOps how not to get Equifaxed Apidays
LeadDev NYC 2022: Calling Out a Terrible On-call System
LeadDev NYC 2022: Calling Out a Terrible On-call System
Software Development in a Funky Manner to meet client requirements best
Software Development in a Funky Manner to meet client requirements best
More from TechWell
Failing and Recovering
Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.
Instill a DevOps Testing Culture in Your Team and Organization
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build Architecture
Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.
System-Level Test Automation: Ensuring a Good Start
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test Strategy
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for Success
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
Implement BDD with Cucumber and SpecFlow
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your Sanity
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
Ma 15
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps Strategy
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOps
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—Leadership
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile Teams
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile Game
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps Implementation
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery Process
DevOps is transforming software development with many organizations adopting lean development practices, implementing continuous integration (CI), and performing regular continuous deployment (CD) to their production environments. However, the database is largely ignored and often seen as a bottleneck in the DevOps process. Steve Jones discusses the challenges of database development and why many developers find the database to be an impediment to the CD process. Steve shares the techniques you can use to fit a database into the DevOps process. Learn how to store database code in a version control system, and the differences between that and application code. Steve demonstrates a CI process with SQL code and uses automated testing frameworks to check the code. Steve then shows how automated releases with manual gates can reduce the stress and risk of database deployments while ensuring consistent, reliable, repeatable releases to QA, UAT, and production.
Mobile Testing: What—and What Not—to Automate
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for Success
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile Transformation
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
More from TechWell (20)
Instill a DevOps Testing Culture in Your Team and Organization
Instill a DevOps Testing Culture in Your Team and Organization
Test Design for Fully Automated Build Architecture
Test Design for Fully Automated Build Architecture
System-Level Test Automation: Ensuring a Good Start
System-Level Test Automation: Ensuring a Good Start
Testing Transformation: The Art and Science for Success
Testing Transformation: The Art and Science for Success
Develop WebDriver Automated Tests—and Keep Your Sanity
Develop WebDriver Automated Tests—and Keep Your Sanity
Eliminate Cloud Waste with a Holistic DevOps Strategy
Eliminate Cloud Waste with a Holistic DevOps Strategy
Transform Test Organizations for the New World of DevOps
Transform Test Organizations for the New World of DevOps
The Fourth Constraint in Project Delivery—Leadership
The Fourth Constraint in Project Delivery—Leadership
Resolve the Contradiction of Specialists within Agile Teams
Resolve the Contradiction of Specialists within Agile Teams
Pin the Tail on the Metric: A Field-Tested Agile Game
Pin the Tail on the Metric: A Field-Tested Agile Game
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
A Business-First Approach to DevOps Implementation
A Business-First Approach to DevOps Implementation
Databases in a Continuous Integration/Delivery Process
Databases in a Continuous Integration/Delivery Process
Turn the Lights On: A Power Utility Company's Agile Transformation
Turn the Lights On: A Power Utility Company's Agile Transformation
Recently uploaded
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR
Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.
Vitthal Shirke Microservices Resume Montevideo
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Cyaniclab : Software Development Agency Portfolio.pdf
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoam
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
Webinar: Salesforce Document Management 2.0 - Smarter, Faster, Better
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Globus Connect Server Deep Dive - GlobusWorld 2024
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
SOCRadar Research Team: Latest Activities of IntelBroker
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
Explore Modern SharePoint Templates for 2024
Modern design is crucial in today's digital environment, and this is especially true for SharePoint intranets. The design of these digital hubs is critical to user engagement and productivity enhancement. They are the cornerstone of internal collaboration and interaction within enterprises.
How to Position Your Globus Data Portal for Success Ten Good Practices
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Understanding Globus Data Transfers with NetSage
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Lecture 1 Introduction to games development
Software engineering
Game Development
unity Game Development
GlobusWorld 2024 Opening Keynote session
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...informapgpstrackings
Keep tabs on your field staff effortlessly with Informap Technology Centre LLC. Real-time tracking, task assignment, and smart features for efficient management. Request a live demo today!
For more details, visit us : https://informapuae.com/field-staff-tracking/Into the Box 2024 - Keynote Day 2 Slides.pdf
Into the Box Keynote Day 2: Unveiling amazing updates and announcements for modern CFML developers! Get ready for exciting releases and updates on Ortus tools and products. Stay tuned for cutting-edge innovations designed to boost your productivity.
A Comprehensive Look at Generative AI in Retail App Testing.pdf
Traditional software testing methods are being challenged in retail, where customer expectations and technological advancements continually shape the landscape. Enter generative AI—a transformative subset of artificial intelligence technologies poised to revolutionize software testing.
Visitor Management System in India- Vizman.app
Your Digital Assistant.
Making complex approach simple. Straightforward process saves time. No more waiting to connect with people that matter to you. Safety first is not a cliché - Securely protect information in cloud storage to prevent any third party from accessing data.
Would you rather make your visitors feel burdened by making them wait? Or choose VizMan for a stress-free experience? VizMan is an automated visitor management system that works for any industries not limited to factories, societies, government institutes, and warehouses. A new age contactless way of logging information of visitors, employees, packages, and vehicles. VizMan is a digital logbook so it deters unnecessary use of paper or space since there is no requirement of bundles of registers that is left to collect dust in a corner of a room. Visitor’s essential details, helps in scheduling meetings for visitors and employees, and assists in supervising the attendance of the employees. With VizMan, visitors don’t need to wait for hours in long queues. VizMan handles visitors with the value they deserve because we know time is important to you.
Feasible Features
One Subscription, Four Modules – Admin, Employee, Receptionist, and Gatekeeper ensures confidentiality and prevents data from being manipulated
User Friendly – can be easily used on Android, iOS, and Web Interface
Multiple Accessibility – Log in through any device from any place at any time
One app for all industries – a Visitor Management System that works for any organisation.
Stress-free Sign-up
Visitor is registered and checked-in by the Receptionist
Host gets a notification, where they opt to Approve the meeting
Host notifies the Receptionist of the end of the meeting
Visitor is checked-out by the Receptionist
Host enters notes and remarks of the meeting
Customizable Components
Scheduling Meetings – Host can invite visitors for meetings and also approve, reject and reschedule meetings
Single/Bulk invites – Invitations can be sent individually to a visitor or collectively to many visitors
VIP Visitors – Additional security of data for VIP visitors to avoid misuse of information
Courier Management – Keeps a check on deliveries like commodities being delivered in and out of establishments
Alerts & Notifications – Get notified on SMS, email, and application
Parking Management – Manage availability of parking space
Individual log-in – Every user has their own log-in id
Visitor/Meeting Analytics – Evaluate notes and remarks of the meeting stored in the system
Visitor Management System is a secure and user friendly database manager that records, filters, tracks the visitors to your organization.
"Secure Your Premises with VizMan (VMS) – Get It Now"
Accelerate Enterprise Software Engineering with Platformless
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
Recently uploaded (20)
Cyaniclab : Software Development Agency Portfolio.pdf
Cyaniclab : Software Development Agency Portfolio.pdf
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoam
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoam
Webinar: Salesforce Document Management 2.0 - Smarter, Faster, Better
Webinar: Salesforce Document Management 2.0 - Smarter, Faster, Better
Globus Connect Server Deep Dive - GlobusWorld 2024
Globus Connect Server Deep Dive - GlobusWorld 2024
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...
SOCRadar Research Team: Latest Activities of IntelBroker
SOCRadar Research Team: Latest Activities of IntelBroker
How to Position Your Globus Data Portal for Success Ten Good Practices
How to Position Your Globus Data Portal for Success Ten Good Practices
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...
A Comprehensive Look at Generative AI in Retail App Testing.pdf
A Comprehensive Look at Generative AI in Retail App Testing.pdf
Accelerate Enterprise Software Engineering with Platformless
Accelerate Enterprise Software Engineering with Platformless
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
Fear and Loathing in Systems Administration
- 1. DW2 DevOps Implementation 11/16/2016 11:30:00 AM Overcome DevOps Fear and Loathing Presented by: Harold Grunenwald Independent Consultant Brought to you by: 350 Corporate Way, Suite 400, Orange Park, FL 32073 888--‐268--‐8770 ·∙ 904--‐278--‐0524 - info@techwell.com - http://www.stareast.techwell.com/
- 2. Harold Grunenwald Independent Consultant Harold “Waldo” Grunenwald is a geek, and if you find him a bit odd, there are plenty of things on which to place blame. He's a long-time systems engineer, enjoys leading teams, and is active in the DevOps community. Waldo may or may not be Batman as no one has ever seen them in the same place at the same time. He is pretty keen on insight tooling—trending/monitoring/alerting—and automation in general. Waldo actually enjoys public speaking, hates writing about himself in the third person, and aspires to one day be a better bio writer.
- 4. @gwaldo
- 6. @gwaldo
- 7. The views expressed in this presentations are solely those of the presenter and do not necessarily reflect those of any company that he may or may not currently or previously work for, giving any and all said companies, hypothetical or otherwise, and we do hereforwithorwithnot give any and all ability for said hypothetical or otherwise corporate lawyers and public-relations personnel any all ability, room, and leverage needed to say whatever they need to disavow whatever this guy is going to say, because who can even tell what’ll causea stir these days, so let’s call this a big ‘ol legal YOLO, and let’s see what kind of run-on sentence we can make of this, because when we’ve gone on this long, it seems kind of a shame to quit now, even though I’m starting to get a little bored with this idea, and nobody is ever really going to read the stupid thing, so at this point all it’s doing is irritating my elementary school english teachers in my head… Disclaimer
- 16. @gwaldo
- 23. @gwaldo
- 34. @gwaldo
- 35. @gwaldo
- 42. @gwaldo
- 52. @gwaldo
- 59. Scope, Staffing, and Priorities @gwaldo
- 68. @gwaldo
- 77. Conway’s Law @gwaldo “Organizations which design systems… are constrained to produce designs which are copies of the communication structures of these organizations.” —Melvin Conway, 1968
- 79. Conway’s Law “Organizations which design systems… are constrained to produce designs which are copies of the communication structures of these organizations.” —Melvin Conway, 1968
- 81. @gwaldo
- 91. @gwaldo
- 99. @gwaldo
- 100. @gwaldo
- 104. @gwaldo
- 107. @gwaldo
- 111. @gwaldo
- 114. @gwaldo
- 124. @gwaldo
- 128. All rights reserved by original owners: “Fear and Loathing in Las Vegas” “The Thing” and “Fantastic Four” owned by Marvel / Disney “The Thing” and “The Addams Family” owned by ____ “The Thing”, Illustration by Wayne Barlowe “Star Wars” owned by Lucasarts / Disney “A League of Their Own” owned by ____ “Pink Floyd”, obviously, themselves “The Dark Knight”, owned by _____ Please don’t sue me.
- 133. Devs just trying to get access to do whatever they want
- 134. The disconnect