A failed test is a clue. Follow the evidence.
A practical way to move from a red CI job to a defensible root cause: separate observations, hypotheses, and proof.
FIELD NOTES FROM THE WORKBENCH
Engineering,
with curiosity.
Storage systems. Reliable tests. AI that holds up.
A notebook for making complex engineering
a little clearer.
SystemsIntelligenceCode
A GOOD PLACE TO STARTFEATURED NOTE
A failed test is a clue.
Follow the evidence.
A practical way to move from a red CI job to a defensible root cause: separate observations, hypotheses, and proof.
Read the noteTHE NOTEBOOK
All notes.
Practical notes. Three areas of engineering to explore.
理解递归：从函数调用到逐层返回
通过阶乘、调用栈交互与实际日志，理解每次调用独立的局部状态、返回后如何继续，以及多层递归调用如何共存。
Test the recovery, not just the interruption.
Fault injection gets interesting after the fault. Define what recovery means from the host, data, and system perspectives.
One lucky run is not an agent evaluation.
Turn an impressive demo into a repeatable evaluation with explicit outcomes, multiple trials, and readable traces.
Treat a prompt change like a release.
Version the behavior you expect, compare it against a baseline, and keep enough evidence to understand regressions.
Python 的 while 与 for：三个循环示例
从动态步长、条件终止到用户交互，理解 while 与 for 的控制机制，以及两者的适用场景。
A lock protects an invariant, not a variable.
Think about the state that must stay consistent, then make the whole read–check–write operation participate in the same protocol.
⌕
No notes found.
Try another phrase or explore all topics.
— You’re all caught up. There’s always more to understand. —
THE COMMON THREAD
Good engineering starts
with a better question.
Observe carefully.
Make the idea testable.
Let the evidence lead.