Reducing DevOps toolchain complexity with GitHub

Development teams often lose valuable time switching between tools, working through admin tasks, and battling red tape. In this session, you’ll hear from Bassem Dghaidi, Senior Software Engineer at GitHub, on how to reduce context switching between teams and tools and eliminate costs in your organization. You’ll leave with a better understanding of what’s possible by evaluating your DevOps toolchain and narrowing your tools—giving teams better workflows and streamlined processes.

Stay up-to-date on all things GitHub by subscribing and following us at:

About GitHub

[-assafuser-kmlqiqf]

Hello, שלום!
אסף, יצחק.רוזנקרנץ.
Assaf itzhak, Rosenkrantz!

[danielgilleland]

It's also important to make the distinction between "self-interruption" and "external interruptions".

When we interrupt ourselves, it's not nearly as disruptive to our productivity, because it usually represents a self-regulating energy management. The key here is that with self-interruption, we are in control as the instigator.

When the interruption comes from "outside" of ourselves (other people, the phone, the email "ting" from our computer, etc.), that is disruption. And that is the kind that's very costly.