I am an infrastructure engineer currently focusing on making systems observable the SRE way. This improves reliability by helping you infer the internal behaviour of a system from its external output. This article is a good long-form explanation of how this can benefit an engineering organisation.
My experience with observability is mainly in the AWS, Linux, NodeJS and PHP space. I’m familiar with Datadog, New Relic, Cloudwatch, Splunk and the ELK stack. My current focus is on digging into the Linux kernel to understand the performance of NodeJS applications and find room for optimisation.
In the past, I’ve been a full-stack engineer focused on building and scaling systems - sometimes of a distributed nature. In an alternate timeline, I’ve also been a graphic designer expressing myself in minimalist styles.
I am interested in:
- Observability - Distributed Tracing, APM, eBPF, perf, Network (TCP, UDP, DNS), Linux systems (CPU, Memory, Disk), Dashboards, Synthetics
- Programming Languages - NodeJS, Python, Golang, PHP, Bash, HCL (Terraform)
- Advanced Linux Troubleshooting - CPU/Memory/Disk Profiling, Network Performance, Debugging Techniques
- System Stuff - Docker, Kubernetes, ECS, Linux Kernel
- Distributed Systems - Distributed Consensus, Architecture, Protocols
- Cloud Platforms - AWS, GCP, Digital Ocean, Heroku
If you're interested in stuff like that, read my blog.
- Currently: Doing SRE at Cloudflare - helping to build a better internet.
- Earlier: Did observability at an amazing company called Paystack - helping to build systems that power payments across Africa.
- Even earlier: Built several full-stack stuff at a design agency called Check DC.
- Before that: Worked with some amazing engineers at Konga.
I enjoy making little tools/products for fun. It's a huge part of why I became interested in building software. You can see most of these projects here.
The best place to reach me is @Ope__O on Twitter.