James Cullimore

Waiting on builds and pipelines wastes time and kills flow. In this talk, I’ll show how I cut both Gradle build times and CI pipeline durations by 50% on a production Android app, all without introducing new tools or rewriting existing code. We’ll start with Gradle: I’ll break down which gradle.properties changes actually moved the needle, how updating to newer Java and Kotlin versions improved performance, and how a comparison between Groovy and Kotlin DSL surfaced potential future wins. You’ll get a practical look at what worked, what didn’t, and how to measure impact in your own project. Then we’ll move to the CI pipeline: I’ll walk through how I restructured steps to increase parallel execution and reduce total pipeline time, not by adding complexity, but by thinking strategically about the build graph. These weren’t sweeping changes, just focused tweaks with big results. If you’re looking for real-world ways to reduce build and pipeline friction, this talk will give you a toolkit of practical optimizations you can apply immediately. Key Takeaways / Learning Points: - Which gradle.properties settings directly impact build performance and why. - How upgrading Java and Kotlin versions can unlock performance improvements with minimal effort. - A comparison of Kotlin vs Groovy DSL for build scripts — and how Groovy may still offer speed advantages in some cases. - How to redesign your CI pipeline to better utilize parallelism and minimize sequential slowdowns. - A strategy for measuring and iterating on build/pipeline performance using simple metrics and real impact.

Maintaining a healthy work-life balance can feel like a juggling act, between code, clients, kids, partners, pets, and even the occasional whisky break. This roundtable discussion brings together personal experiences and practical insights on navigating the shift from full-time work to freelance, while keeping life and career in harmony. We'll explore how prioritising relationships, health, and personal time has not only improved productivity but also fuelled meaningful contributions to the Android community. From time management systems to the importance of community engagement, this discussion offers real talk and real tactics for developers seeking balance in both code and life. Let's talk about: How can developers successfully transition from full-time employment to freelance without losing work-life balance? What role does personal well-being play in staying productive and focused in Android development? In what ways can sharing knowledge and contributing to the Android community enhance both career growth and personal fulfilment? What time management systems have worked and failed for developers, and how can they be adapted to reduce stress and promote sustainability? How do breaks, hobbies, and family time actually make us better developers?