Suggestions
Jeffery Campbell
Senior Site Reliability Engineer | Learning From Incidents
Jeffery Campbell is a Senior Site Reliability Engineer at HashiCorp with extensive experience in DevOps and resilience engineering.1 Some key details about Jeffery Campbell include:
Professional Background
- Currently works as a Senior Site Reliability Engineer at HashiCorp1
- Has 15 years of experience as a DevOps/Resilience Engineer, working both on-premises and in cloud environments1
- Previously joined HashiCorp's incident management and learning from incidents team in 20202
Skills and Expertise
While specific details about Jeffery's skills are limited in the provided information, as a Senior Site Reliability Engineer, he likely possesses expertise in:
- Cloud infrastructure and platforms
- Automation and infrastructure as code
- Monitoring and observability
- Incident response and management
- DevOps practices and tools
Education
Jeffery Campbell attended university, though the specific institution is not mentioned in the available information.1
Career Path
Given his current senior role and extensive experience, Jeffery has likely progressed through various technical positions in his 15-year career before reaching his current position at HashiCorp.
Without more detailed information, it's difficult to provide a comprehensive profile of Jeffery Campbell. However, his long-standing experience in DevOps and resilience engineering, coupled with his senior role at a prominent company like HashiCorp, suggests he is a skilled and respected professional in the field of site reliability engineering.
Highlights
I’m happy to share that I’m joining the new incident management/learning from incidents team at HashiCorp!
"Hiroki Sato, a former air-traffic controller who is now vice president of the transportation-industry labor union, said he found the warning signified by the yellow screen often turned out to be mistaken or unnecessary, and controllers didn’t give it priority."
We get them every day: the "disk is almost full" log entry, the console warning, the "your package is out of date" email. Every complex system is in a constant degraded state. It is easy to become desensitized to alerts you see every day (also known as "Alert Fatigue"). There's no shame in it. If everyone took the time to fix every single alert as soon as it appeared then nothing would ever get done!
I challenge you to post this article in your team's Slack this week and ask the question: "What is one warning or alert that you have deprioritized recently?" The goal is not to fix everything, you just want to start the conversation and see what surfaces. Even a small incremental change now could save you from a huge headache in the future.
