<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CoreX</title><link>https://corex.co/</link><description>Recent content on CoreX</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 21 Mar 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://corex.co/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloud Platform Engineering</title><link>https://corex.co/services/cloud-platform-engineering/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/services/cloud-platform-engineering/</guid><description>&lt;p&gt;From landing zones and network topology to multi-tenant Kubernetes clusters and compliance guardrails, I design and operate the kind of infrastructure that a growing engineering organisation can actually rely on.&lt;/p&gt;&#10;&lt;p&gt;I&amp;rsquo;ve built platforms on all three major clouds — Azure (where I&amp;rsquo;ve done extensive Landing Zone work with Terraform and Azure Policies), AWS (EKS, networking, IAM), and GCP (GKE, embedding with Google PSO). The result is always the same: a platform your developers can consume confidently, with clear standards for security, observability, and delivery baked in from day one.&lt;/p&gt;</description></item><item><title>Infrastructure as Code</title><link>https://corex.co/services/infrastructure-as-code/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/services/infrastructure-as-code/</guid><description>&lt;p&gt;Manual infrastructure processes are slow, error-prone, and impossible to audit. I replace them with Terraform modules and Ansible playbooks your team can understand, own, and extend without calling me every time something changes.&lt;/p&gt;&#10;&lt;p&gt;Every resource is versioned, every change is reviewed, every environment is reproducible. When something breaks at 2 a.m., your runbook is the code itself — not someone&amp;rsquo;s memory.&lt;/p&gt;</description></item><item><title>CI/CD Pipeline Design</title><link>https://corex.co/services/cicd-pipeline-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/services/cicd-pipeline-design/</guid><description>&lt;p&gt;Most CI/CD problems are not tool problems — they&amp;rsquo;re architecture problems. Each team invents its own pipeline, quality gates are inconsistent, and every microservice has a slightly different way of doing the same thing.&lt;/p&gt;&#10;&lt;p&gt;I design composable pipeline systems where the shared logic lives in templates your teams consume with minimal configuration. Security scans, container builds, environment promotions, rollback logic — all consistent, all auditable, none duplicated. The pattern scales whether you have 5 services or 500.&lt;/p&gt;</description></item><item><title>Technical Leadership &amp; Team Coaching</title><link>https://corex.co/services/technical-leadership/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/services/technical-leadership/</guid><description>&lt;p&gt;Engineering excellence doesn&amp;rsquo;t happen by accident. I work alongside your team rather than above it — conducting architecture reviews, running hands-on workshops,&#10;and building the habits that compound over time.&lt;/p&gt;&#10;&lt;p&gt;I&amp;rsquo;ve led teams of senior engineers through platform migrations, run many learning sessions on Docker, Kubernetes, Terraform, and Azure at meetups, conferences&#10;and on-site at customers&amp;rsquo;.&#10;I have also coached individuals across multiple projects.&#10;The goal is always the same: leave the team stronger than I found it, so they don&amp;rsquo;t need me to stay.&lt;/p&gt;</description></item><item><title>IoT Prototyping</title><link>https://corex.co/services/iot-prototyping/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/services/iot-prototyping/</guid><description>&lt;p&gt;I&amp;rsquo;ve been building IoT projects in my spare time for years — Home Assistant integrations, ESP8266 and ESP32 sensors, MQTT pipelines, Prometheus and Grafana dashboards driven by real physical data.&lt;/p&gt;&#10;&lt;p&gt;At a hackathon, a friend and I built a snow-depth detector using an ultrasonic sensor and an ESP32 shipping metrics over MQTT. The organisers (84codes) hired me to turn this prototype into a hardware demo kit that connected DHT11 sensors to LavinMQ queues, with a Ruby backend forwarding to Grafana — specifically to make conference workshops tangible.&lt;/p&gt;</description></item><item><title>Technology Exploration</title><link>https://corex.co/services/technology-exploration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/services/technology-exploration/</guid><description>&lt;p&gt;Every engineering organisation reaches a point where someone needs to actually try the new thing before the team commits to it. That evaluation takes time and focus your team doesn&amp;rsquo;t have.&lt;/p&gt;&#10;&lt;p&gt;I embed with your team as a technical researcher: I evaluate candidate technologies, build proof-of-concepts, stress-test architectural directions, and produce a clear recommendation backed by real evidence — not vendor slides. The engagement ends with a decision, not a shrug.&lt;/p&gt;</description></item><item><title>Portable Pipelines</title><link>https://corex.co/blog/portable-pipelines/</link><pubDate>Thu, 21 Mar 2019 00:00:00 +0000</pubDate><guid>https://corex.co/blog/portable-pipelines/</guid><description>&lt;p&gt;Every microservices team eventually reinvents the same pipeline. They copy and paste the YAML from the last service they built, change the image name, and call it done. For a while, it works fine.&lt;/p&gt;&#10;&lt;p&gt;Then a security vulnerability surfaces and you need to add a container scan step to every pipeline. Or you want to enforce a consistent artifact naming scheme. Or someone needs to change how environment variables are injected. Suddenly you&amp;rsquo;re touching 30 pipelines individually, hoping you get them all — and hoping they&amp;rsquo;re consistent enough to actually find.&lt;/p&gt;</description></item><item><title>The future is now: join the DevOps revolution!</title><link>https://corex.co/talks/the-future-is-now/</link><pubDate>Wed, 15 Nov 2017 12:00:00 +0200</pubDate><guid>https://corex.co/talks/the-future-is-now/</guid><description>&lt;p&gt;The software industry has been through a lot of change. The way we build, test, and deliver software has evolved dramatically — and it&amp;rsquo;s still evolving.&lt;/p&gt;&#10;&lt;p&gt;In this talk I trace that evolution: where we came from, where we are today, and where the real opportunities are for teams that want to move faster without breaking things. The DevOps revolution isn&amp;rsquo;t about tools — it&amp;rsquo;s about removing the friction between the people who build software and the people who operate it.&lt;/p&gt;</description></item><item><title>Introducción a los Schedulers</title><link>https://corex.co/talks/introduccion-a-los-schedulers/</link><pubDate>Sat, 25 Mar 2017 15:54:45 +0200</pubDate><guid>https://corex.co/talks/introduccion-a-los-schedulers/</guid><description>&lt;p&gt;La coordinación manual de recursos es un proceso lento y propenso a fallos. El mercado ofrece diferentes tecnologías para resolver este problema — pero ¿cuál escoger? ¿por qué?&lt;/p&gt;&#10;&lt;p&gt;En esta charla hago una introducción a los principales sistemas de coordinación de recursos disponibles: &lt;a href="https://kubernetes.io" target="_blank" rel="noopener noreferrer"&gt;Kubernetes&lt;/a&gt;, &lt;a href="https://mesos.apache.org" target="_blank" rel="noopener noreferrer"&gt;Mesos&lt;/a&gt;, &lt;a href="https://docs.docker.com/engine/swarm/" target="_blank" rel="noopener noreferrer"&gt;Docker Swarm&lt;/a&gt; y &lt;a href="https://nomadproject.io" target="_blank" rel="noopener noreferrer"&gt;Nomad&lt;/a&gt;. El objetivo es que el público salga con suficiente contexto para tomar una decisión informada.&lt;/p&gt;</description></item><item><title>From development to production in 5 minutes: is your company ready?</title><link>https://corex.co/talks/from-dev-to-prod-in-5-minutes/</link><pubDate>Thu, 17 Nov 2016 15:31:38 +0200</pubDate><guid>https://corex.co/talks/from-dev-to-prod-in-5-minutes/</guid><description>&lt;p&gt;Companies want change. They say they want to adopt agile methodologies, DevOps, containers, and orchestrators. But wanting change and being ready for it are two different things.&lt;/p&gt;&#10;&lt;p&gt;In this talk, by drawing a parallel with the history of South American independence, I help people at every level of an organisation understand the real challenges — technical and cultural — of driving transformation in large companies. And what actually works.&lt;/p&gt;</description></item><item><title>Microservices infrastructure with Terraform, Consul and Vault</title><link>https://corex.co/talks/microservices-infrastructure-with-terraform-consul-and-vault/</link><pubDate>Thu, 08 Sep 2016 15:31:38 +0200</pubDate><guid>https://corex.co/talks/microservices-infrastructure-with-terraform-consul-and-vault/</guid><description>&lt;p&gt;Together with Container Solutions and Cisco, we built a robust infrastructure specialised in the delivery of microservices. Three key components made it work:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://terraform.io" target="_blank" rel="noopener noreferrer"&gt;Terraform&lt;/a&gt;&lt;/strong&gt; for building and managing the infrastructure&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://consul.io" target="_blank" rel="noopener noreferrer"&gt;Consul&lt;/a&gt;&lt;/strong&gt; for service discovery&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://vaultproject.io" target="_blank" rel="noopener noreferrer"&gt;Vault&lt;/a&gt;&lt;/strong&gt; for secrets management&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;In this talk I walk through the product we built, the decisions we made, and how the three tools glue together into something coherent.&lt;/p&gt;&#10;&lt;div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"&gt;&#10;&#9;&#9;&#9;&lt;iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/XsOt2MAAm3g?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"&gt;&lt;/iframe&gt;&#10;&#9;&#9;&lt;/div&gt;</description></item><item><title>Writing your own Terraform provider</title><link>https://corex.co/talks/writing-your-own-terraform-provider/</link><pubDate>Thu, 07 Apr 2016 15:10:47 +0200</pubDate><guid>https://corex.co/talks/writing-your-own-terraform-provider/</guid><description>&lt;p&gt;While working with a client at Container Solutions, I had the opportunity to introduce Terraform to one of their critical infrastructure processes — turning a deliverable that normally took two weeks into a 30-minute Terraform run. Along the way, I wrote two custom Terraform providers.&lt;/p&gt;&#10;&lt;p&gt;This talk, preceded by a &lt;a href="https://container-solutions.com/write-terraform-provider-part-1/" target="_blank" rel="noopener noreferrer"&gt;blog post&lt;/a&gt;, walks through why you&amp;rsquo;d write your own provider and exactly how to build one: the structure, the SDK, the provider schema, and the resource lifecycle.&lt;/p&gt;</description></item><item><title>Defining your infrastructure with code</title><link>https://corex.co/talks/defining-your-infrastructure-with-code/</link><pubDate>Mon, 11 Jan 2016 15:10:47 +0200</pubDate><guid>https://corex.co/talks/defining-your-infrastructure-with-code/</guid><description>&lt;p&gt;A short introduction to Terraform — what it is, how it works, and why defining your infrastructure as code changes the way you think about operations.&lt;/p&gt;</description></item><item><title>About</title><link>https://corex.co/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/about/</guid><description>&lt;p&gt;I&amp;rsquo;m an independent IT consultant. I&amp;rsquo;ve delivered enterprise systems since 2008. Most of that time has gone into building the things that make other engineers&amp;rsquo; lives easier.&lt;/p&gt;&#10;&lt;p&gt;I started as a web developer in 2009 — ASP.NET, then Ruby on Rails, then the full frontend parade: jQuery, Backbone.js, Ember.js, Angular. After a few years of that, I made the leap to infrastructure and never looked back.&lt;/p&gt;&#10;&lt;h2 id="the-evolution"&gt;The evolution&lt;/h2&gt;&#10;&lt;p&gt;Once I discovered automation, there was no going back. Ansible for configuration management. Terraform for cloud infrastructure. Docker when it was still a curiosity. Kubernetes before it was boring. I&amp;rsquo;ve worked with EKS, AKS, and GKE, and across all three major cloud providers — Azure, AWS, and GCP — as well as smaller ones like DigitalOcean, Scaleway, Linode, and Hetzner.&lt;/p&gt;</description></item><item><title>Contact</title><link>https://corex.co/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/contact/</guid><description>&lt;p&gt;Have a project in mind, or just want to talk through a problem?&lt;/p&gt;&#10;&lt;p&gt;The best way to reach me is by email at &lt;a href="mailto:carlos@corex.co"&gt;carlos@corex.co&lt;/a&gt;, or fill in the form below and I&amp;rsquo;ll get back to you within one business day.&lt;/p&gt;</description></item><item><title>CV</title><link>https://corex.co/cv/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://corex.co/cv/</guid><description>&lt;p&gt;&lt;strong&gt;Tech Lead / Cloud &amp;amp; Platform Engineer&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="mailto:carlos@corex.co"&gt;carlos@corex.co&lt;/a&gt;  ·  &lt;a href="https://linkedin.com/in/mongrelion" target="_blank" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;  ·  &lt;a href="https://github.com/mongrelion" target="_blank" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;  ·  &lt;a href="https://corex.co/talks/"&gt;Talks&lt;/a&gt;&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;&#10;&lt;p&gt;Tech lead since 2008, designing, building, and operating cloud-native platforms and leading engineering teams by example. I specialise in turning manual, error-prone infrastructure processes into fully automated, secure, and compliant systems — from landing zones and reusable CI/CD pipelines to multi-tenant Kubernetes architectures. I teach, coach, and share knowledge as a core part of how I raise the bar for the teams I work with, both internally and through public speaking at conferences and meetups.&lt;/p&gt;</description></item></channel></rss>