Paul King
V.P. And Chair Of Groovy PMC at The Apache Software Foundation
Brisbane City, Queensland, Australia
Summary
🤩
Rockstar🎓
Top School
Top expert inJava Enterprise Development and Integration Technologies
Paul King is a veteran software engineer and open-source leader with nearly two decades of experience spanning telecommunications, enterprise Java, and agile delivery, currently serving as V.P. and Chair of the Apache Groovy PMC. He combines deep technical chops—Ph.D.-level formal methods, Java/Groovy backend development and hands-on refactoring work on flagship projects like Grails and Apache Groovy—with strategic roles guiding standards, training and technology adoption. An advocate for code quality and maintainability, his contributions include bug fixes, compiler work and cross-platform test hardening that improved stability for widely used JVM frameworks. A frequent international speaker, author and contributor since the early 2000s, he uniquely bridges rigorous research, practical engineering and community stewardship from Brisbane.
19 years of coding experience
20 years of employment as a software developer
Marist AshgrovePh.D., Formal Specification of Communication Protocols, Ph.D., Formal Specification of Communication Protocols at The University of Queensland
Stackoverflow
952reputation
69kreached
39answers
0questions
groovy
top-5%
Github Skills (20)
back-end-development10
go-gorm10
grails10
groovy10
testing10
java10
javas10
orm10
refactoring10
hibernate9
sql8
performance-optimization7
xml6
soapui6
imperative-programming6
Programming languages (13)
Github contributions (5)
apache/groovy
Apr 2015 - Jan 2023
Apache Groovy: A powerful multi-faceted programming language for the JVM platform
Role in this project:
Back-end Developer
Back-end DeveloperContributions:95 reviews, 4985 commits, 691 PRs in 7 years 10 months
Contributions summary:Paul contributed to the Groovy project by addressing a ConcurrentModificationException related to processing ModuleNode imports, specifically improving backwards compatibility. They also made changes to remove a dependency on a GroovyDoc JANSI library and refactored to avoid division-by-zero errors with empty GString strings. Their work involved modifying Java code within the core Groovy project, suggesting a focus on backend code and performance. They also contributed to improve tests.
static-typinggroovyfunctional-programmingapachemetaprogramming
groovy/groovy-core
Oct 2006 - Apr 2015
former home of the groovy programming language, moved to https://github.com/apache/groovy
Role in this project:Back-end Developer
Back-end DeveloperContributions:4444 commits, 41 PRs, 41 pushes in 8 years 7 months
Contributions summary:Paul primarily worked on improvements to Groovy code used for building and maintaining Java API Documentation. They added functionality for adding or removing the text in the text fields of an XML format for the documentation. These changes involved modifying and extending existing Groovy utility methods.
groovyapachecompilerprogramming-languageinterpreter
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.