Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate at JFrog. For a living he hangs out with JFrog’s tech leaders, writes code around the JFrog Platform and its ecosystem, and then speaks and blogs about it all. He has been doing this for the last dozen years or so, and enjoys every minute of it.
Baruch is @jbaruch on twitter and mostly blogs on http://www.jfrog.com/blog/ and http://blog.bintray.com.
He is a professional conference speaker on DevOps, Java and Groovy topics, and is a regular at the industry’s most prestigious events including JavaOne (where he was awarded a Rock Star award), DockerCon, Devoxx, DevOps Days, OSCON, Qcon and many others. His full speaker history is available on Lanyrd: http://lanyrd.com/profile/jbaruch/sessions/
Almost every major version of Spring framework introduced a new way to configure the context: XML, Annotations, Java Config, Groovy… What’s next, and, more important - why so many?! And how to know what to use and when? In this session Baruch, Viktor and Yakov will try to find the silver bullet, and you will have a chance to vote for the best feature implementations or even make a bet of the winner!
More strange, more bizarre, more fun! The Groovy Puzzlers hits with its second season in which we implemented the lesson learned from the first one - do more of the same (always as a duet)! Expect even more “NO WAY!”, “WHOA!”, “WTF!”, O_o and prizes flying around, and expect to learn more about Groovy’s darkest secrets! As usual, the traps we fell into here in JFrog and contributions from top-notch Groovy authors and users!
Using software modules today is the default way of working for most systems and frameworks. With the advent of many software languages and OSS frameworks, new module systems are constantly created and new module ecosystems start to prevail. This trend is horizontal and covers operating system packages, language libraries and application modules (plugins).
But while some module systems are nicer to use, others are repeating past mistakes and are a daily source for developer agony and pain.
In this keynote I will present the “lessons learned” at JFrog, where we make software for managing software libraries and deal with many types of module systems. This talk will show what works and what doesn’t work in a module system; what features can make a module ecosystem thrive or fail; and why, despite all downsides, modules are here to stay and conquer more space as the Cloud continues to grow.
