Skip to main content

Andy Palmer

Andy Palmer

Andy Palmer has sixteen years of experience, twelve in agile and lean methods. He has experience across multiple sectors, including telecommunications, investment banking, retail, and media. In addition to his experience in company-wide agile transformations, agile coaching, process reengineering, and software development, Andy specializes in effective communication and team psychology, which means he is as comfortable advising C-level executives as he is mentoring technical teams.

Speaker Presentations
Monday, June 8, 2015 - 8:30am
Full-day Tutorials
Explore Big Data with Graph Databases: A Hands-On Practicum

SQL and MapReduce databases are great—when your data is well-partitioned and the same queries are run regularly. What happens when we don't know what we will want to know in the future? Graph databases are used in everything from Facebook to business intelligence apps. With nodes, edges, and properties to represent and store data, graph databases give us the opportunity to define the landscape as we learn more about our data. Using graph databases we can start at a location and ask for a description of where we are. This allows us to discover pathways and interesting data points that we might not otherwise have been aware of. Andy Palmer explains how you can discover the data landscape and bend it to your will with exploratory reports. Starting with the fundamentals of graph databases—using Neo4J as the tool—your skills with graph databases will increase through the day until you are able to explore and discover new gems of information for yourself.

Bring your laptop and try a big data tool.

Wednesday, June 10, 2015 - 1:30pm
Personal Excellence
What’s In a Name? The Metaphorical Power in Our Ideas

Why is naming things so difficult? Look in any reasonably sized code base, and you’ll see—in abundance!— crimes against naming. The Spring framework has a class AbstractSingletonProxyFactoryBean—and there are many worse examples. We in the computer industry tend to name things by what they do, rather than why they do it, and thus rob ourselves of the opportunity to tell an interesting and intriguing story. Andy Palmer says it hasn’t always been this way. In the early days of computing, names were rich with metaphor. Names, that today are synonymous with the concepts, were once compelling and novel stories. Terms such as Desktop, File, and Folder all had analogues in the physical world, and this helped people come to grips with the new concepts. Andy gives some examples of metaphors from the early days of computing, discusses some more modern examples, gives reasons why we might choose to program in this way, and suggests some ways in which we can improve our ability to tell a story through our code.