Devoxx Belgium 2018
from Monday 12 November to Friday 16 November 2018.
Holly Cummins is the worldwide development discipline lead for the IBM Cloud Garage, and a developer in the London Cloud Garage. Holly is also a Java Champion and JavaOne Rock Star. Before joining the Cloud Garage, she was Delivery Lead for the WebSphere Liberty Profile (now Open Liberty). Holly co-authored Manning’s Enterprise OSGi in Action. She is an active speaker and has spoken at JavaOne, Devoxx, JavaZone, JFokus, The ServerSide Java Symposium, JAX London, QCon, GeeCon, and the Great Indian Developer Summit, as well as a number of user groups. Before joining IBM, Holly completed a DPhil in Quantum Computation.
See also https://www.ibm.com/cloud/garage/
An in-depth look at what makes software development a roller coaster where the highs of 0 compiler warnings are quickly cancelled out by the pain of long hours, bad requirements, endless configuration, clueless managers and a plethora of other issues which make death by a thousand cuts seem like a good idea…. They will answer questions such as: “Why is programming often called an art despite having its underpinnings in formal logic?” “How can I rediscover the delight I felt when I first started coding?” “What’s that rush I feel when my test passes? Am I addicted to TDD?”
Combining Psychology, Philosophy and Computer Science, Dr Holly Cummins will present a series of practical tips to help you rediscover the euphoria that you felt the very first time a metal box in front of you came to life and cried out “Hello World”
As a developer in IBM's Cloud Garage, I work with customers who are trying to get to cloud so everything becomes better. What's getting in their way isn't the technology - wrapping something in a docker container (usually) isn't that hard. Instead, it's the structures that have been put in place to manage risk and the relationships between teams that trip companies up. In this talk, I'll share some stories of customers struggling to get cloud native, and how we applied our methodology to turn things around. I'll cover the ideal team size, the ideal microservice size, what skills a team needs, the role of architects, how to know if something is ready to ship, and whose fault everything really is.