This is my: LeetCode or Explode
Research & Defining
In the research and planning phase, I created a MoSCoW analysis to define priorities, mapped out the tech stack (Go, MySQL, GKE, Terraform, etc.), and researched the tools, frameworks, and APIs needed (Chrome Extension, Discord, Google Sheets API, Kubernetes) to validate feasibility before building.
Diagramming & Layout
In the diagramming stage, I sketched out the full system architecture and designed the database schemas, then mapped how all services would interact across the stack. This included planning the data flows, API endpoints, and deployment topology, which gave me a clear blueprint before attempting deployment on GKE.
Coding & Debugging
During the coding phase, I built both the JavaScript for the Chrome extension and the Go backend, handling challenges like CORS errors, HTTP requests, and numerous database bugs. I often relied on my schema design to trace and debug issues, which helped keep development organized and efficient.
Challenges & Solutions
The biggest challenge was architecting a highly available, fault-tolerant backend under a tight deadline, since I anticipated real users. To address this, I designed the system with self-healing, rolling deployments, and blue-green releases, ensuring bugs could be quickly identified and resolved at launch.
Highlight of the project
he highlight of the project was attracting and retaining real users who actively used and enjoyed the product without encountering bugs, among them engineers from Amazon and Uber.
