I worked on a blog project called “Incident vs Bug: A Complete Guide for DevOps Engineers and SREs.” The goal was to clear up confusion between incidents, bugs, issues, problems, and errors.

The piece was written in a conversational style, almost like explaining it to a teammate over coffee. Instead of dry textbook definitions, I used real examples (like the Optus outage in 2025), simple comparison tables, and quick checklists so readers could instantly see the difference.

The final blog came out to around 1,450 words. It’s structured, easy to scan, and SEO-friendly, with natural keyword placement. Alongside the blog, I also prepared short 30-word explanations for related terms (bug vs issue, incident vs problem, incident vs error, etc.) to make the content even more practical and shareable.

Overall, this project shows how I can take a technical topic, strip away the jargon, and turn it into something that’s clear, useful, and engaging for DevOps engineers, SREs, and IT teams.