We Solved DevOps. What’s Next? en

Hear me out: We solved DevOps. I am not saying that everyone is doing it right (or even trying), but we have the solution if you want to do it right. Here is the theory, the technology, the communities, the docs, and the books—go knock yourself out. Do DevOps: empower your teams, make deployments a breeze, build invincible CI/CD pipelines, and create production environments that are secure, stable, and observable. Done.

Now, in perfect alignment with DevOps and the Theory of Constraints, it’s time to turn our gaze to the next bottleneck: the production environments of our production environments. They’re a mess. We accept soul-sucking toil, slow and unstable tests and builds, and constant distractions as the norm, just as we accepted the insufferable, manual “throw garbage between silos” all-night deployments of the pre-DevOps era. But, as with DevOps, we shouldn’t take these for granted. It’s time to rise again and resist our development environments' “Pre-DevOps” state. Let’s engineer better developer productivity for all!

Technical Enshittification: Why Everything in IT is Horrible Right Now and How to Fix It en

Did you notice how everything in IT is crap right now? Services are bloated, slow, and buggy, and the hardware requirements to run even the simplest applications are enormous. It’s not just me, right? Everything is full of bugs, support is clueless, nothing works as described, and don’t even get me started on IoT protocols and the Cloud Native space. Oh, and how about taking half of the world’s air traffic offline because of a null pointer exception pushed to production without verification?

And on top of what’s broken, the pace of innovation has crawled to a stop (except maybe in the AI space). There’s nothing materially new in the last ten versions of Android and iOS or the last hundred versions of Chrome and Firefox. Google spent months hyping a new login screen that ended up being just a rearrangement, and can you name one new exciting feature in any software older than five years (plugging in a ChatGPT bot doesn’t count)? When Facebook was bragging about breaking things, at least it was to move faster. What’s their excuse now?

This talk will dig into the reasons behind this technical decline, which we call “Technical Enshittification.” We’ll explore how technical debt, poor innovation practices, and stagnation in core products are dragging us down.

While this talk probably won’t be able to fix the Googles, the Apples, and the Metas, we will focus on what you can do to prevent this decline in your own projects and companies.

We’ll discuss practical strategies to combat and prevent this mess, focusing on Developer Productivity Engineering (DPE), user-centered design, robust testing, and effective project management. Real-world examples will show how to keep IT services efficient, innovative, and user-friendly.

Join us to learn how to turn things around and ensure long-term success in today’s digital landscape.

Coding Fast and Slow: Applying Kahneman's Insights to Improve Development Practices and Efficiency en

Embark on an exciting journey into the intersection of psychology, software development, and Developer Productivity Engineering (DPE) as we explore how Nobel laureate Daniel Kahneman's groundbreaking work on the psychology of judgment and decision-making can optimize your development practices while conserving cognitive resources. Discover the impact of System 1 and System 2 thinking on the software development process, and learn to strike the perfect balance between "fast" intuitive thinking and "slow" deliberative reasoning.
We'll delve into practical DPE strategies for reducing mental fatigue and minimizing context switches, focusing on techniques like build system performance optimization, test parallelization, AI-powered test selection, and developer productivity observability. By leveraging these best practices, you'll enhance your and your team's productivity and maintain focus on high-value tasks.
Whether you're an experienced developer seeking to boost your performance or a curious newcomer eager to learn about the connections between the human mind, software development, and DPE, this talk is for you. Join us for an exhilarating adventure into the fast and slow worlds of coding, and uncover new ways to maximize your cognitive resources.

Surviving the Techpocalypse: Empowering Survivors with Developer Productivity Engineering en

In these perplexing times, when jobs vanish like ice cream on a hot summer day, tech professionals must find the sweet spot between concern for their affected colleagues and the pressing need to scoop up progress.

Discover Developer Productivity Engineering (DPE), the secret sauce that helps both individuals and companies navigate the labyrinth of layoffs and limited resources with flair. Join us as we trek through a landscape teeming with dispirited engineers and floundering companies, showcasing DPE's power to transform even the most disenchanted developer into a productivity maestro.

By adopting DPE's clever approach, we can face economic instability with unity and a dash of wit, turning sour lemons into a refreshing lemonade of success.

Shifting Left, Shifting Blame: How DPE Levels the DevOps Playing Field en

Ah, developers, the golden children of IT! They're the ones who bring the code to life and make the magic happen. But sometimes, they dodge responsibilities, whether it's security vulnerabilities, usability issues, or integration challenges. "That's for Ops to handle closer to production," they say, crossing these concerns off their "definition of done" list. And when things go wrong? Ops is left holding the bag, cleaning up messes they didn't make.

Enter Developer Productivity Engineering (DPE), the framework that encourages developers to take ownership from the start. DPE fosters faster feedback, ensuring that developers address various issues—security, usability, and even third-party integrations—early on. It's not just about writing code; it's about writing accountable code.

You might be thinking, "Isn't that what DevOps is for?" Absolutely, but DPE takes it a step further. It's like DevOps on steroids, making sure everyone is not just collaborating but also accountable for their part.

And here's the best part: developers actually want this. They take pride in code that compiles and passes unit tests. What they've lacked is a way to take ownership of quality issues that go beyond basic functionality. DPE gives them the tools and the mindset to do just that.

So, if you're tired of the blame game where Ops gets all the flak and developers seem untouchable, come discover how DPE can change the dynamics. It's a win-win for everyone, leveling the playing field and making sure everyone is accountable for delivering quality.

DevOps Reframed: Embracing the Path to Developer Productivity Engineering en

Building on the success of DevOps practices, which already employ the Theory of Constraints to tackle bottlenecks, Developer Productivity Engineering (DPE) emerges as the next natural progression. DPE takes a step further by optimizing workflows, automating tasks, and providing real-time feedback to developers, keeping software delivery nimble and efficient.

In this engaging talk, we'll explore how DPE enhances the DevOps framework, streamlining the development process throughout the software delivery lifecycle. See why mastering DPE is essential for all engineers, including Platform and Site Reliability Engineers, as it aligns with core principles like reducing toil, promoting automation, and implementing observability, all while keeping bottlenecks at bay.

With a touch of wit and insight, learn practical tips to harness DPE's power and elevate your software development game. Join us as we reframe the DevOps landscape, revealing the importance of DPE as the next step in our software development evolution, ensuring continued success and growth by effectively managing constraints and bottlenecks.

DevOps for developers (or maybe against them?!) en ru

"DevOps" is the operations people’s crafty plan to make developers do other people's work, but we are smart enough to see right through this naive rebranding trick!

Baruch suggests you think about it: we, the developers, have written all the code. It passes all the tests; it obviously works, and works well (Are we a little proud? We are!); so we are DONE.

Now, out of the blue, a bunch of "thought leaders" (all with an operations background, mind you!) are trying to tell us that we have to learn YAML, Docker, Kubernetes and Terraform to deploy our software because suddenly it is our concern?!

In this talk, we'll discuss why developers do or don’t need DevOps. We'll consider arguments made by DevOps visionaries and see whether they hold water. Hopefully, by the end of the talk, we'll understand whether DevOps really helps developers to deploy better code to production more often, or if it is just another scam made up by marketing and evangelists.

This is a fun and provocative talk. I am starting by claiming that developers have no incentives to do any DevOps and will work my way to explain why; although there is some truth in that, it doesn't matter. The business must commit to DevOps, and once the business is committed, everyone has to be on board.

DevOps для разработчиков (или против них?!) en ru

DevOps — это заговор сисадминов, чтобы заставить разработчиков делать чужую работу, но мы слишком умны, чтобы попасться на эту элементарную уловку ребрендингом! Посудите сами: мы написали код, он проходит тесты. Он, очевидно, работает и работает хорошо (Мы гордимся собой? Да!). И тут мы закончили.

Но приходят эти «визионеры» (все из operations, прошу заметить!) и рассказывают нам, что теперь надо учить YAML, Docker, Kubernetes и Terraform, потому что внезапно это наша головная боль?!

В этом докладе мы поговорим о том, зачем разработчикам нужен или не нужен DevOps. Мы рассмотрим аргументы, которые приводят идеологи DevOps, и решим, состоятельны они или нет. К концу доклада, будем надеяться, нам станет понятно, действительно ли это способ, который поможет нам (разработчикам) поставлять лучший код в прод чаще, или это, как всегда, разводка маркетологов и евангелистов.

Fast Feedback, Faster Development: An Introduction to Developer Productivity Engineering (DPE) en

Explore Developer Productivity Engineering, a field laser-focused on delivering swift feedback loops while keeping developers in their flow. DPE elevates code quality and developer morale by reducing frustrating hiccups, eliminating toil, and providing better feedback, faster. Ready for a smoother and more efficient dev experience? This talk's your ticket.

Engineering Success: Empowering Developers through Enhanced Productivity en

Developer success encompasses well-being, work-life balance, and workplace culture, but it also hinges on engineering environments and tools. In this talk, we explore how enhancing developer productivity can drive success and satisfaction.

As DevRel team members, we shape the developer experience by collaborating to improve engineering processes and tools. We'll discuss strategies for enhancing tools and adopting new ones that excel in promoting productivity.

In developer relations, our mission includes championing initiatives that benefit developers' productivity and well-being. The concept of "developer productivity engineering" (DPE) unifies our efforts to enhance productivity through engineering practices.

Join us to discover insights and strategies for elevating developer productivity. Whether you're a developer advocate or a DevRel manager, this talk will offer valuable perspectives on fostering a culture that prioritizes developer success. Together, we'll explore how DPE can transform engineering culture, benefiting developers, DevRel teams, and organizations.

If this version meets your needs, I'm glad we could find the right fit! If you have any further requests or need additional assistance, please feel free to let me know.

Influencing DevOps without Authority - how "DevOps engineer" can advance real DevOps en ru

You know about DevOps, you know DevOps is right for your organization, but hey, what can you do? As an individual contributor or a team leader, your authority to transform your organization to DevOps is limited. But your influence is not!
In this talk, Baruch will show how some proven influencing and negotiating techniques can be used to convince critical stakeholders in your organization in the necessity of DevOps.
We look at the arguments, the techniques, and the small tricks, which work in particular situations with particular engineering and business leadership positions and will prepare you to deliver the message of DevOps most convincingly to each.

"Influence without Authority", "Getting to Yes", "Getting past No" and others applied to IT organizations with DevOps message.

Устраиваем DevOps без полномочий: Даже "ДевОпс инженер" может помочь en ru

Казалось бы, доклад про устроение ДевОпса должен быть про настройку Дженкинса, но нет!

Этот доклад для тех, кто понимает, что ДевОпс это история про культуру, коллаборацию и общение, но не очень представляет как будучи скромным исполнителем или тимлидом, повлиять на целый энтерпрайз или галеру, и свдинуть организацию в соторну ДевОпса.
Барух расскажет какими методами можно воспользоваться для влияния на stake–holder-ов, что кому говорить, как мотивировать, и как работать с возражениями.
Пожалуй, за исключением парапсихологических практик и гипноза (которые не стоит раскрывать неокрепшим умам), на этом доладе будет обозрены все способы влиять, не имея полномочий на благо наступления повсеместного ДевОпса в индустрии.