JDD 2014: Michael Hunger

### Overview In this interview at the JDD 2014 conference, Michael Hunger discusses his background with Neo Technology, the neo4j graph database, and his conference session focused on analyzing source code structure using neo4j. The conversation covers the core capabilities of graph databases for interconnected data, practical applications in software development, the pre-conference hackathon, and his impressions of the JDD event.

### Key Topics - **neo4j and Graph Databases**: Designed specifically for storing and quickly querying connected data where traditional databases struggle with rich connections. - **Analyzing Source Code**: Using a simple source code scanner to import software structural elements into neo4j, enabling developers to query the codebase using the Cypher query language. - **JDD Hackathon**: A pre-conference coding challenge organized by Jarek at SmartRecruiters focused on implementing a source code management (SCM) and version control system with neo4j. - **Conference Atmosphere**: Reflections on the developer-centric community spirit, organization, and networking value of the JDD conference.

### Technical Details - **Data Ingestion**: Developers can scan source code to import entities such as classes, types, interfaces, inheritance relationships, composition, fields, and methods into neo4j. - **Querying Code with Patterns**: Using simple graph patterns in the query language (referred to in the transcript as Cypher/server), developers can query the graph once to discover code smells and extract software metrics. - **Graph Enhancement & CI Integration**: Teams can enrich the graph model with custom concepts and constraints, allowing the entire analysis workflow to be integrated directly into automated build processes. - **SCM Implementation Challenge**: During the hackathon, participants tackled building a version control system on top of a graph database following an introductory session on neo4j and graph concepts.

### Takeaways - Graph databases provide a low-risk, fast-value entry point for developers looking to understand and enforce rules across complex, interconnected software codebases. - Integrating graph-based code analysis into continuous build processes helps detect code smells and monitor architectural constraints automatically. - JDD is recommended for developers looking to move beyond their comfort zone, learn new paradigms, and approach software problems differently.