Going "outside the pure engineering requirement" to deliver notifcations, monitoring and recording into Google Apps so that Technical Operations staff as well as People Ops can not only record, monitor and observe utlisation and requests, but can update in their natural (Workspace) systems to trigger appropriate actions within the technology environment - situations such as onboarding and offboarding, for example.

Automation using a combination of Github invoked actions and terrafrom managed API calls to replace some of the simple funcionality for non technical staff since the EA Mamanegent Portal was End-of-Life

Designed and created a YAML config file definition and processing automation that allows insertion of new and un-planned terraform modules into a landing zone type configuration where an engineer can assign a new config section that when ingested into terraform triggers parsing and invocation of a new module - allowing engineering teams to drop in new features with minimal effort and zero ammendments to the actual workflow

Workflows to take simple "feature definitons" to integrate new options into an existing Landing Zone - delivering backend state management, secret management, workflow templates and auto-generated webUI pages and Slack Apps

This content will be updated shortly.

If you take a look at my various profiles, you'll see my passion for tech; and for those with a keen eye that have browsed my repo list, you'll see I'm a problem solver - an innovator - failing fast with all our options so I can deliver an matrix oif solutions tiered in the way that the business can understand.... a solution might be high medium or low risk; it can be delivered in a week, a month ore a year; it can be delivered for a range of costs. we can deliver a solution that allow the business to asses and guide at a high level without being bogged down by technical detail

I pride myself on options options options... with a few caveats

• we deliver to meet a requirement - whether defined together or by the customer - but we always involve the end user
• we deliver secure... even if we do a POC that bypasses security best practice, we must never allow a solution to impede any security protocols
• we have fun... well I always have fun
• we trust and we build on mistakes... we grow talent and loyalty through failing fast.... but lets keep that between us and development only...
• because production is God. production is our Queen, the Pharaoh... if you will, my precious ;)

I'm a huge believer in re-using the best examples out there, if available... If we can understand it, maintain it or contribute to an open source lets do it
I firmly believe that we deliver internally how we deliver for clients... If we are carrying out repetitive or manual processes, examine how we can automate or provide self-service for it.... and can we use that solution either with clients as an accelerator or as a blog post