<img src="https://certify.alexametrics.com/atrk.gif?account=Zpb+p1uhUo20dG" style="display:none" height="1" width="1" alt="">
Why DevOps Tools Do Not Speak Developer Language (And How to Overcome This)

Webinar

Think About Your Audience Before Choosing a Webinar Title


Sponsored by KOMODOR


Tuesday, October 5, 2021
11 a.m. ET

The rise of DevOps and Agile over the past few years has led to a shift in responsibilities. Gone are the days when troubleshooting Kubernetes issues rested solely in the hands of DevOps teams. Today, developers are expected to own their code and will find themselves on-call to troubleshoot their apps if an issue arises.

This poses a question, however: Are developers equipped with the right tools to effectively manage the troubleshooting process? After all, many of the tools they rely on to figure out root causes were initially built with DevOps teams in mind.

Join Baruch Sadogursky, head of DevOps advocacy at JFrog and Itiel Shwartz, CTO and co-founder at Komodor as they discuss:

  • The gap between DevOps teams and developers when it comes to troubleshooting K8s issues
  • Why current DevOps tools do not speak “developer's language"
  • Best practices and recommended tools to empower dev teams to troubleshoot independently
Baruch Sadogursky
Head of DevOps Advocacy - JFrog
Baruch Sadogursky (@jbaruch) did Java before it had generics, DevOps before there was Docker, and DevRel before it had a name. Now Baruch helps engineers solve problems and helps companies help engineers solve problems. He is a co-author of the "Liquid Software" and "DevOps Tools for Java Developers" books, serves on multiple conference program committees, and regularly speaks at numerous most prestigious industry conferences, including Kubecon, JavaOne (RIP), Devoxx, QCon, DevRelCon, DevOpsDays (all over), DevOops (not a typo) and others.
Itiel Shwartz
CTO & Co-founder - Komodor
Itiel started out at eBay [Forter], then went on to become the first developer at Rookout. He is a backend and infra developer turned “DevOps” and an avid public speaker that loves to talk about things like: infrastructure, Kubernetes, Python observability and R&D culture.

REGISTER NOW:

What You’ll Learn in This Webinar

You’ve probably written a hundred abstracts in your day, but have you come up with a template that really seems to resonate? Go back through your past webinar inventory and see what events produced the most registrants. Sure – this will vary by topic but what got their attention initially was the description you wrote.

Paint a mental image of the benefits of attending your webinar. Often times this can be summarized in the title of your event. Your prospects may not even make it to the body of the message, so get your point across immediately.  Capture their attention, pique their interest, and push them towards the desired action (i.e. signing up for your event). You have to make them focus and you have to do it fast. Using an active voice and bullet points is great way to do this.

Always add key takeaways. Something like this....In this session, you’ll learn about:

  • You know you’ve cringed at misspellings and improper grammar before, so don’t get caught making the same mistake.
  • Get a second or even third set of eyes to review your work.
  • It reflects on your professionalism even if it has nothing to do with your event.