beginning changes

Author: jerdog

slides.md

@@ -1,19 +1,19 @@
 ---
 titleTemplate: "%s - Slidev"
-title: "Developer Experience is Central to DevOps Success"
+title: "Developer Experience is Central to Enterprise Success"
 theme: slidev-theme-the-unnamed
 info: |
-  ## Developer Experience is Central to DevOps Success
+  ## Developer Experience is Central to _Enterprise_ Success
 
   ## Abstract
   Developer Experience (DevEx) encompasses every aspect of the experience that your developers (both internal and external) have with your product, tooling, systems, etc. While platform engineering aims to reduce developer toil, DevEx goes beyond that. It covers deployment pipelines, Infrastructure as Code (IaC) practices, developer efficiencies, productivity, UI/UX, and APIs. In this presentation, we will focus on some of the principles of DevOps (collaboration, communication, shared responsibility), go into the history of DevEx and how it's changed over the years (remember Vim? CFEngine?), and how a strong DevEx mindset can bring together development and operations teams.
 author: Jeremy Meiss
-conference: "devfest KC 2024"
+conference: "KCJUG"
 socialimg: '../images/bluesky-jerdog-white.png'
 keywords: devex,developer experience,devops
 presenter: true
 download: true
-exportFilename: devfestKC24_devex-central-devops-success
+exportFilename: KCJUG_devex-central-enterprise-success
 export:
   format: pdf
   timeout: 30000
@@ -39,7 +39,7 @@ layout: cover
 
 # Developer Experience...
 
-## Central to DevOps Success
+## Central to _Enterprise_ Success
 
 <!-- A quick note that most of the images have been autogenerated by AI - which would explain some of the weird shapes and colors in the images. -->
 
@@ -48,9 +48,9 @@ layout: cover
 # What is "Developer Experience" (DevEx)?
 
 <!--
-We've all had that experience using a tool or service that was a disaster. It could be the worst deployment process you've ever seen, or the most painful codebase you've ever had to work with, or documentation that's so confusing it makes your head spin. Or maybe a combination of them… Who here knows what I’m talking about? 
+We've all had that experience using a tool or service that was a disaster. It could be the worst deployment process you've ever seen, or the most painful codebase you've ever had to work with, or documentation that's so confusing it makes your head spin. Or maybe a combination of them… Who here knows what I’m talking about?
 
-We’ve all seen examples of epicly bad websites, right? 
+We’ve all seen examples of epicly bad websites, right?
 -->
 
 ---
@@ -72,7 +72,7 @@ git push heroku main
 ![Heroku deploy button](/images/slides/heroku-deploy-button.png)
 
 <!--
-Heroku was long considered the gold standard for developer experience with a simple set of tools and a command-line interface that allowed developers to focus on building applications and delivering them to users. And that was it. Now of course, Heroku is still around (albeit not nearly as developer-centric as they formerly were, but that is changing), but it's not the only game in town. Anyone used Netlify, Vercel, etc.? 
+Heroku was long considered the gold standard for developer experience with a simple set of tools and a command-line interface that allowed developers to focus on building applications and delivering them to users. And that was it. Now of course, Heroku is still around (albeit not nearly as developer-centric as they formerly were, but that is changing), but it's not the only game in town. Anyone used Netlify, Vercel, etc.?
 -->
 
 ---
@@ -151,8 +151,8 @@ transition: slide-down
 ---
 
 ## A working definition of DevEx
-  
->_"...the **journey** of developers as they learn and deploy technology, which if successful, focuses on eliminating obstacles that hinder a developer or practitioner from achieving success in their endeavors."  
+
+>_"...the **journey** of developers as they learn and deploy technology, which if successful, focuses on eliminating obstacles that hinder a developer or practitioner from achieving success in their endeavors."
 
 -**Jessica West**, _Co-Founder, DevEx Institute_
 
@@ -294,7 +294,7 @@ class: my-cool-content-on-the-right
 ### HP Softbench
 
 <!--
-and was extensively talked about in the June 1990 edition of the HP Journal. 
+and was extensively talked about in the June 1990 edition of the HP Journal.
 -->
 
 ---
@@ -660,8 +660,8 @@ layout: default
 
 
 
-<!-- 
-**Collaboration** in DevOps **is about creating an environment where silos are broken down, and cross-functional teams are empowered to work as a single unit**. It's people first, and 
+<!--
+**Collaboration** in DevOps **is about creating an environment where silos are broken down, and cross-functional teams are empowered to work as a single unit**. It's people first, and
 -->
 
 ---
@@ -674,7 +674,7 @@ layout: default
 - Enhanced collaboration _**via tools and processes**_
 
 
-<!-- 
+<!--
 ...tools second. When DevOps and DevEx are aligned, we enhace collaboration through tools and processes that **reduce friction and barriers in the development process, enabling teams to focus more on solving business problems together, leading to innovative solutions and a more harmonious working environment.**
 -->
 
@@ -690,8 +690,8 @@ layout: default
 - Communication
 
 
-<!-- 
-The backbone of DevOps is effective **communication**, which ensures all members of the development, operations, and broader organizational team are on the same page. With 
+<!--
+The backbone of DevOps is effective **communication**, which ensures all members of the development, operations, and broader organizational team are on the same page. With
 -->
 
 ---
@@ -705,7 +705,7 @@ layout: default
 
 - Improving communication **_via streamlined info sharing and feedback_**
 
-<!-- 
+<!--
 When we are **improving Communication** , we start to utilize platforms and tools that streamline information sharing and feedback across teams. That includes your CI/CD pipelines, shared dashboards, and automated alerting systems ensure all team members have visibility into the development process, can easily share updates, and quickly address issues.
 -->
 
@@ -722,7 +722,7 @@ layout: default
 
 - Shared Responsibility
 
-<!-- 
+<!--
 **Shared Responsibility** in DevOps means there is **collective accountability for the software's quality and reliability, blurring the lines between roles traditionally separated by development and operations.** It's about **moving away from a "not my job" mentality to a "we're in this together" mindset, where success and failures are shared equally**.
 -->
 
@@ -739,7 +739,7 @@ layout: default
 
 - Shared responsibility **_by empowering all teams with access and information_**
 
-<!-- 
+<!--
 That **Shared Responsibility** brings empowerment to all team members with access to the tools and information they need to contribute across the entire software lifecycle. **By democratizing access to tools and information, DevEx encourages a culture where everyone feels ownership of the product and is motivated to contribute to its success.**
 -->
 
@@ -753,7 +753,7 @@ backgroundSize: contain
 
 
 
-<!-- 
+<!--
 Organizations seeking to build more cohesive, agile, and effective teams who are better equipped to meet the demands of modern software development, have to ensure that they don't stop at just these core DevOps principles - but that they ensure an emphasis on DevEx in the implementation of the tooling. If it's a poor experience, you aren't going to see the results you want.
 -->
 
@@ -775,7 +775,7 @@ transition: fade
 
 </v-clicks>
 
-<!-- 
+<!--
 [click]A good DevEx facilitates **smoother transitions between your dev and ops teams**, helps [click]**minimize bottlenecks and enhances collaboration**. Proper [click]**feedback loops are part of both DevEx & DevOps**, and with them in place you have a positive DevEx that **ensures those loops are efficient and productive**, all of which which [click]**helps DevOps principles** to take firm hold within an organization. There's no better example than what we've seen with Platform Engineering the last few years.
 -->
 
@@ -799,7 +799,7 @@ class: my-cool-content-on-the-left
 
 </v-clicks>
 
-<!-- 
+<!--
 The rise of platform engineering represents a paradigm shift [click]**towards creating comprehensive, integrated environments that cater specifically to the needs of developers**. Focusing on [click]**abstracting away the complexities of infrastructure and backend services**, allows developers to concentrate on writing code and creating value. [click]Platform engineering embodies the principles of DevEx by **ensuring that developers have access to robust, scalable, and easy-to-use platforms**. [click]which **streamline development processes, reduce setup time**, and allow for a focus on innovation rather than maintenance, removing a lot of developer toil.
 -->
 
@@ -821,7 +821,7 @@ class: my-cool-content-on-the-left
 
 </v-clicks>
 
-<!-- 
+<!--
 Self-service platforms embody the evolution of DevEx by [click]**empowering developers** to independently provision resources, deploy applications, and manage their lifecycles without waiting for operational support. [click]These platforms **leverage automation, templates, and predefined policies** to ensure compliance and governance, while offering the agility needed for rapid development cycles. By providing developers with the tools to perform tasks that were traditionally in the domain of IT operations, [click]self-service platforms **accelerate development, enhance productivity, and foster a culture of autonomy and innovation**.
 -->
 
@@ -831,7 +831,7 @@ image: /images/slides/42-devex-devops-convergence.jpg
 backgroundSize: contain
 ---
 
-<!-- 
+<!--
 ### Bringing DevOps and DevEx Together
 When organizations prioritize DevEx, they ensure that devs have access to tools and processes that not only streamline their workflow but also facilitate a smoother transition of code from development to production. This alignment encourages both teams to work closely from the outset of projects, sharing insights, feedback, and responsibilities, which enhances the efficiency of the development lifecycle and leads to higher quality outcomes. Which strenghtens the implementation of DevOps culture and practices.
 -->
@@ -859,7 +859,7 @@ backgroundSize: contain
 
 </v-clicks>
 
-<!-- 
+<!--
 Some of the better practices to keep in mind when leveling up with DevEx are: [click]**Equip teams** with integrated, user-friendly tools that support automation, collaboration, and real-time communication. Choose the tools which align with both Dev and Ops needs. Get their input in the decision. Just because your buddy's IT startup says they offer 10x developer productivity doesn't mean it works for your teams, much less that it works at all. [click]**Put in place cross-functional teams** that include roles with diverse expertise (e.g., development, operations, quality assurance) to foster a shared understanding and responsibility from project inception through to deployment and maintenance. [click]**Establishing robust feedback mechanisms** allow for continuous learning and improvement. Conduct regular retrospectives, incorporate user feedback into development cycles, and use monitoring tools to gather insights on performance and user experience. [click]Reduce toil and free up team members to focus on more strategic activities by **automating repetitive and manual tasks wherever possible.** This includes automating testing, deployments, and infrastructure provisioning. Paige Bailey at Google even wrote a post about how she automated away the boring parts of her job. [click]**Ensure that team members have opportunities to learn and grow** their skills in both development and operations domains. This helps in building empathy between teams and equips individuals with the knowledge to understand and contribute to different stages of the development lifecycle.
 -->
 
@@ -879,7 +879,7 @@ You may be in a position where you want to help drive the changes needed to impr
 
 <Tweet id="1750563607266410692" />
 
-<!-- 
+<!--
 The level of investment that a company invests in DevEx can be a reflection of a company's values towards its employees, especially its developers. A strong focus on DevEx shows a commitment to employee well-being and efficiency. And prioritizing DevEx helps foster a culture of excellence and innovation. When developers are provided with the right tools, support, and environment, they are more likely to produce high-quality work and push the boundaries of what's possible.
 -->
 
@@ -1001,7 +1001,7 @@ Streamlining the Development Workflow
 This approach focuses on making the development process itself smoother and more efficient. Here are some key strategies:
 Focus on tools and automation: Explore options for code editors, version control systems, CI/CD pipelines etc. to automate repetitive tasks and improve development efficiency.
 
---> 
+-->
 
 ---
 layout: image-left
@@ -1038,7 +1038,7 @@ class: my-cool-content-on-the-right
 <!--
 Standardize development environment setup: Use configuration management tools and streamline onboarding processes to ensure a consistent and efficient development environment for all team members.
 Some examples: JFrog’s Artifactory provides that centralized repo for all artifact types, making it easy for deves to find the resources they need; JFrog’s Pipelines provides a CI/CD platform for automating the build, test, deployment process. There’s also JFrog’s new collaboration with GitHub announced today. Atlassian provides a suite of tools which integration collaboration, communication, and knowledge sharing. GitHub and Gitlab provide version control and collaboration. Ansible helps to quickly and consistently set up development environments, saving time and reducing the risk of configuration errors.
---> 
+-->
 
 ---
 layout: statement
@@ -1049,7 +1049,7 @@ layout: statement
 >### "ruthlessly eliminating barriers (and blockers) that keep your practitioners from being successful"
 
 
-<!-- 
+<!--
 I'll leave you with this, that DevEx is ruthlessly eliminating barriers (and blockers) that keep your practitioners from being successful.
 -->
 
@@ -1074,7 +1074,7 @@ layout: two-cols
 <p><img src="/images/www.png" style="vertical-align: middle; display: inline; margin: 5px; max-height:50px;">jmeiss.me</p>
 
 
-<!-- 
+<!--
 
 -->
 
@@ -1083,7 +1083,7 @@ layout: end
 ---
 
 
-<!-- 
+<!--
 
 -->