Twelve principles. “When X · Do Y.”

How one engineer operates so the work can be trusted — the reasoning shown, the record real, the call owned. Engineers in the program internalize each in their own words; their takes and open questions gather below.

When you don't know — Say so. Name what you do know, and what you need to find out.

2 internalized · 2 open doubts

prachi: Clear communication is very important in any setting. It is important to ask for help. The long-term effects of not speaking up can add up over time.Roshini: I learned that it is okay to say “I don’t know” when I really don’t know something Open doubt — While trying to understand more about the predictive engine, I’ve been stuck, as it has been more of a black-box problem answer →

When you see a problem — Flag it before it ships — before someone else finds it.

3 internalized · 2 open doubts

Shruthiha: I see a problem, I should tell someone early instead of ignoring it. This can help prevent bigger problems.prachi: It is important to flag problems because if the foundation is problematic, the entire structure built on top of it can collapse. So, it is almost always better Open doubt — How can I tell someone about a problem without making them feel bad? answer →

When you make a decision — Record why. The code is the what; the reasoning is the why.

3 internalized

Shruthiha: whenever I make a decision, I should record what I decided and why I decided it. This helps me to understand later Roshini: While making decisions we should record it for future case and decisions should be clear. By recording it we can understand what is what ,why is this happening

When you estimate — Name what you know and what you don't. A number without its unknowns is a guess.

2 internalized

Roshini: Before going into a decision,I should know "What i know,what i don't know".This clear identification avoid wrong conclusion or assumptions and can make better d Shruthiha: I should be clear about what I know and what I am unsure about. This helps, avoid making guesses and make better decisions.

When something is taking longer — Say so before the deadline. Name the reason, and name when you knew.

2 internalized

prachi: Oftentimes, it feels embarrassing to admit that I might need help or more time; I guess sometimes we just have to swallow the guilt and be upfront about things Shruthiha: I learned that if my work is taking longer than expected, I should inform others before the deadline and explain the reason honestly.

When you disagree — Say so. A no with a reason starts a better conversation than a yes that leads nowhere.

2 internalized · 1 open doubt

prachi: don’t agree just to avoid friction. Be honest about disagreement and explain why.Shruthiha: I learned that it is okay to disagree with someone. I should share my opinion politely and give a clear reason.Open doubt — Sometimes I feel nervous to share my opinion because others may not agree with me. answer →

When something goes wrong — Record what happened and what you learned. A clean delivery that buries the incident is waste.

2 internalized

prachi: If something is broken, it should be brought up truthfully. Ownership also means owning mistakes and taking action to address them.Shruthiha: I learned that when something goes wrong, I should understand the mistake and learn from it and try not to repeat the same mistake.

Before you start — Confirm what good looks like. Silence is not alignment.

2 internalized · 1 open doubt

prachi: overcommunicate if you must, but ensure both the parties have clear understanding of the scope before touching the project.Shruthiha: I learned that before starting any task, I should clearly understand what is expected, Asking questions is first can help me avoid mistakes.Open doubt — I may hesitate to ask questions, but I should ask when I am not clear about the task. answer →

When you write the record — Write what actually happened — not what you wish had happened.

2 internalized

prachi: Tho It’s easy to get deluded; writing what actually happened is important for future context and mapping your journey.Shruthiha: I learned that when writing a record, I should write the facts as they really happened, not change them to make them look better.

When you have a question — Ask it in the room. Questions kept for the DM create private knowledge.

2 internalized · 1 open doubt

prachi: Questions should be asked and resolved as soon as they arise. Asking questions showcases your interest in the topic and that you have been actively listening.Shruthiha: I learned that if I have a question, I should ask it openly instead of keeping it on myself. Asking questions helps everyone learn and understand better.Open doubt — Sometimes I scared to ask questions in front of others, but I should be confident and ask when I don't understand. answer →

When you claim something — Show the work. Claims without evidence are opinions.

2 internalized

prachi: Claims should be defendable by actions Shruthiha: I learned that when I make a claim, I should support it with evidence. I should not make statements without proof because evidence makes my work more trust.

When you challenge — Challenge the work, not the person.

2 internalized

prachi: question someone’s work without making it a judgment of them as a person Shruthiha: I should focus on improving the work, not the person.I should give feedback respectfully.

“We agree that the work done here will be seen.”

Log against these on Proof →

Proof · Zero Maintenance Engineer · 12 principles