Software developer for PayPal's Java core framework, which provides the core for much of PayPal's SOA system. Primary role involves being a liaison between PayPal application teams and the core set of open source libraries it depends on. I help find and fix bugs in the open source. We also work with the open source community on identifying new features. Beyond that, I contribute to a fairly large code base that ties open source libraries to PayPal's internal systems.Throughout all of my years at PayPal, I have been active in the Austin site's continuing education group, which coordinates hackathons, 'Nerd lunches', and code jams.

My first 4 years were spent working on PayPal's Platform-as-a-Service team, where I spent a large amount of time developing infrastructure, services, and tooling to support PayPal's API-first initiative. I developed a decent portion of the team's agile development practices. My last 3 years were spent on PayPal's JVM framework team. I initially joined to work on the PayPal's open source Squbs framework (https://github.com/paypal/squbs/), which adds enterprise features to the Akka framework. In addition to that, I played a decent role in a major version release of a more traditional JAX-RS, batch, and messaging framework. The primary aspect of this release involved integrating and promoting non-blocking APIs and libraries for PayPal teams while still supporting PayPal's application teams that wanted to continue developing using blocking APIs.

My primary responsibilities revolve around progressing an integration-in-the-cloud architecture, mentoring, and establishing developer practices.

More or less the same thing I was doing at the time of acquisition.

My primary efforts revolve around finding ways to produce cost effective, quality code and passing those ways along to other developers. For the former, I strive to produce less code using OOP (death to if-else!), TDD, Java, Scala, and smart use of tooling (e.g. Sonar, Maven reporting, Git). For the latter, I serve as scrum master, resident wiki editor, and opponent to the solo project expert. My largest projects revolve around creating server-side functionality with RESTful interfaces. For these projects, I have extensively used Fuse/ServiceMix, OSGi, Camel, ActiveMQ, and Jackrabbit. I have done many projects that create JDBC-like interfaces for data backends. Most of the backends have been fronted by SOAP based web services; however, they've also included things like Excel spreadsheets. In this 'integration' capacity, my primary impact has been the development of an easier-to-implement set of interfaces.

Web application development in a startup environment. The primary tools were Java, Struts, JSP, Tomcat, and Ant. Dabbled in Python to automate some build processes.