During my time at Lyft, I was responsible for defining team direction, priority, and scope with the goal of improving developer productivity. I have been primarily focused on gathering and distilling customer feedback down for product teams, and ensuring adoption of new features and products.
As part of this role I was responsible for launching internal developer marketing communications at Lyft, ensuring that we brought Lyft‘s personality and excitement with our customers back to our own employees to raise awareness and drive adoption.
In addition, I was responsible for driving down cloud developer environment costs and helping to migrate developers from a bespoke development environment to one built on common best practices and open tooling for Python and Golang.
As a Developer Evangelist at Akamai, I have been tasked with educating customers and potential customers about our APIs, and how to integrate Akamai products at even level of the stack — from devops, to frontend.
During my time there I have focused heavily on HTTP/2 and new web architectures, including contributing better HTTP/2 support to both the PHP curl extension, and Ruby Curb gem, as well as contributions to Python’s Hyper H2 project.
To help bring Akamai automation into the existing workflows of developers (“to meeting them where they live”), I lead the effort to build multiple third-party integrations, including Terraform, and WordPress.
In addition I envisioned, architected, built, and lead the efforts around Akamai CLI which brings a consistent developer and user experience to Akamai’s products via the command-line.
As a community engineer for Engine Yard, I have been involved in many aspects of our marketing and product initiatives including helping develop ROI metrics for developer relations, and go to market strategy based on community feedback and observation. I have been involved in producing marketing messaging and materials for both the PHP community and the general tech community.
My primary role has been representing Engine Yard at conferences by informing potential customers about our products, as well as speaking at most. In addition, I am responsible for in-depth and blog technical content, podcasts and organizing the Engine Yard developer conference, Distill.
Additionally, I have been active in numerous open source projects as well as participating in our social media initiatives.
As an engineer for Engine Yard, I was responsible for creating and maintaining public and internal APIs, orchestrating Amazon AWS infrastructure and managing PHP-based systems. Additionally, I was involved in maintaining the Orchestra PHP Cloud application management web console and creating new features for the platform, such as SSL and support for PHP 5.4.
In addition to my engineering duties, I wrote documentation, blog posts and have represented Engine Yard by speaking at conferences all over the globe.
Due to the contractual nature of the academic catalog, we face many data integrity challenges; needing to ensure accurate “creation-to-user” processes; which feature revision and rich text change tracking abilities.
From advising the CTO on the direction of the product to working with systems administration staff on implementation of environment. I am primarily responsible for creating both usable intuitive user interfaces and designing the back-end architecture and database structures to power them with an emphasis on ease of use for further new development, maintenance and exposing as web services.
Upgrading to PHP 7 is a comprehensive guide on changes to PHP in PHP 7, published by O’Reilly Media, Inc.
This 70 page book covers everything you need to know to migrate your legacy code to PHP 7, and to get started using all the new features.
The Zend PHP Certification Study Guide (3rd Edition), edited and produced by the publishers of php[architect], provides the most comprehensive and thorough preparation tool for developers who wish to take the exam. This book provides complete coverage of every topic that is part of the exam, including: