Baruch Sadogursky (@jbaruch) did Java before it had generics, DevOps before there was Docker, and DevRel before it had a name. He started DevRel at JFrog when it was ten people and took it all the way to a successful $6B IPO by helping engineers solve problems. Now Baruch keeps helping engineers solve problems but also 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.
"DevOps" is the operations people’s crafty plan to make Java 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 Java 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 Java 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 Java developers to deploy better code to production more often or if it is just another scam made up by marketing and evangelists.
Searching for speaker images...