I live in Israel. Some days the work gets cut by a siren, a quick move to the stairwell, and the long effort afterward of finding the thread again. This is not a piece about bravery. It is a short note about what repeated interruption does to attention, judgment, and the small habits that start mattering once disruption becomes background.
Stress changes the shape of work before the schedule
From the outside, a workday under threat can look almost normal. The calendar is still there. The laptop still opens. Messages arrive with the same cheerful confidence they had yesterday. The change shows up somewhere less visible first.
Attention fragments faster. Working memory gets shallower. Sleep degrades, which makes patience thinner and context switching more expensive. WHO's current guidance on mental health in emergencies is useful partly because it is plain. Anxiety, sleep problems, fatigue, irritability, and difficulty concentrating are common. That alone is enough to rearrange a day, before anyone starts speaking in clinical language.
The cost of interruption is not the siren itself. The cost is the ruined cognitive thread afterward.
What teams misread
A few things are easy to misread when people are working under repeated alarms.
None of this is uniquely Israeli. The local version has its own texture. There is a particular absurdity to discussing rollout sequencing and telemetry five minutes after checking whether the stairwell is clear.
The main mistake is not emotional. It is operational. Teams keep pretending the old work shape is intact and then wonder why judgment becomes erratic.
What actually helps
The solutions are not glamorous. They are structural. Smaller units of work. Explicit handoff state. Written decisions. Resumable tasks. Fewer invisible dependencies. Less shame around broken concentration than people think.
The habits I trust:
- leave a clean written state before stepping away
- keep the next action obvious enough that you can restart half a day later
- prefer narrow scopes to heroic multitasking
- record decisions while they are still fresh, do not trust memory
- make it cheap to ask "where were we?"
Nothing romantic about any of it. That is part of the point.
Why engineering habits matter here
Good engineering habits are not therapy. They still help under strain.
Observability reduces speculation. Checklists lower the memory tax. Narrow scopes give the nervous system fewer open fronts to hold alive. Rollback paths make mistakes less existential. Clear ownership helps because vague accountability becomes unbearable under strain.
When the day keeps breaking apart, resumability stops being a convenience. It becomes a requirement.
For colleagues outside Israel
If you work with colleagues here, the helpful part is not usually grand language.
Most people do not need speeches about resilience. They need cleaner priorities, less noise, explicit sequencing, fewer demands disguised as flexibility. They need other people to understand that interruptions have a tail.
A siren lasts a short time. The attention debt after it does not.
Remote teams can do real damage without meaning to. When the local reality is unstable, vague requests, shifting priorities, and sloppy follow-up stop being ordinary annoyances. They turn into avoidable stress multipliers.
Clarity travels well.
What I trust
Smaller promises. Cleaner notes. Systems that are easy to resume. Teams that do not turn ordinary stress into a performance problem.
Good work under pressure looks narrower and quieter than people expect. That is often the start of better judgment, not weakness.
Related reading
- Getting AI-assisted development to green without breaking the code
- Building agentic AI systems that hold up