I’m Panji Gautama. I write about engineering leadership, product, and how I work.
Defect/Bug Management
Bugs are inevitable; treating every one as equally urgent makes them harder to manage. I outline severity levels, response expectations, and backlog allowances, while distinguishing severity from priority. The aim is to give teams a shared way to decide what needs immediate attention, what belongs in a sprint, and what can wait without letting important issues disappear.
On Observability
Monitoring should help a team understand what is happening and respond to problems before customers have to report them. I outline application errors, uptime, infrastructure metrics, traces, performance, and business signals, then discuss health checks and alert design. A recurring concern is signal versus noise: collecting more data only helps when the alerts lead to useful action.
Scrum != Agile
A short introduction to my COMPFEST 13 presentation on agile software development, centered on the distinction between Scrum and Agile. The post links to the slide deck rather than reproducing the talk as an article. Open it to find the presentation and its discussion of two terms that often appear together in conversations about how engineering teams work.
Software Fragmentation - The Golden Path
Engineering autonomy can produce a growing mix of tools and dependencies that becomes expensive to support. I outline a golden path approach: agree on recommended components, invest in supporting them, and plan adoption with team leads. The goal is to balance local technical choices with the wider organization's need to operate, maintain, and improve its services.
Engineering Growth Framework
A growth framework makes career expectations explicit so engineers and managers can have clearer conversations about progress. I share the factors used at Mekari, from impact and delivery to communication, mentorship, and operational excellence. The framework is intended to reduce ambiguity and bias, support growth plans, and help teams make more consistent decisions about hiring and promotion.
Manager Manifesto
A collection of management notes about helping people reach a common goal: difficult conversations, realistic roadmaps, hiring, feedback, communication, and owning team outcomes. The emphasis is on listening, providing useful frameworks, and improving how people work together. I kept these notes as a reference; the original post acknowledges that they were collected from a source I did not record.
Engineering Initiative, where to start?
Finding worthwhile engineering improvements starts with understanding the problem. I use a situation, complication, question, and resolution structure to connect proposed work to evidence, then examine agility, availability, performance, security, and automation. These questions give engineers a starting point for turning operational pain and system metrics into initiatives they can explain and prioritize with their team.
Excerpt on Regulated Data : Amount, Duration Data Holding, and Archiving
These 2021 notes collect an excerpt on personal data retention, deletion, and archiving under the Indonesian regulations discussed at the time. I also record the operational practices I advised, including audit trails, security monitoring, and local replication. The post preserves that historical context and the connection between data handling policies and the systems needed to support them.
On Establishing Technical Documentation at Mekari
Skipping documentation can hide disagreement and leave teams rebuilding things others have already solved. I describe why we introduced RFCs at Mekari, how written designs support review and shared understanding, and why an opinionated template helps. The post also sets boundaries around when a full RFC is worth the effort and when a smaller conversation or document will do.
Incident & Post Mortem Process
Recurring incidents take time away from building useful things for customers. I describe the incident and postmortem process we used at Mekari, including what counts as an incident, when a written review is needed, and what it should record. The purpose is to understand contributing causes and turn that understanding into actions that reduce the chance of recurrence.