Praised — and pulled in

Urgent disclosure can produce the best short-term outcome and the worst long-term boundary outcome simultaneously. The bug fix is real, but so is the precedent. The cost of 'one time' Sundays compounds across years if you don't actively re-set the boundary later. The bug is killed before any customer sees it You're visibly the kind of engineer who cares — and that compounds in your reputation The precedent of 'reachable Sunday night' is now established and hard to walk back You're tired going into a hard week

The disclosure that respects both sides

Most 'I have to escalate right now' impulses are signals about your own anxiety, not the system's risk. A clean Monday-morning disclosure preserves the company AND the boundary — and trains the org that you can be trusted with both at once. Boundaried diligence is a senior signal. The bug is killed on the same release cadence — disclosure-now wouldn't have changed the ship date Your boundary holds and the trust holds simultaneously — the org learns you can do both Your manager notices the discipline and starts asking for your judgment on bigger things You internalize the rule: 'urgent feeling' ≠ 'urgent reality' for most non-on-call findings

Six weeks later — it surfaced in a customer call

Boundaries are a strength when they protect rest. They become a tax when they protect avoidance. The distinction is often visible only afterward — but the version of you that knows the difference can usually feel it in real time. Trust the discomfort, not the rationalization. The bug becomes a customer-facing incident instead of a quiet patch Your self-trust takes a small but real hit — you knew, and you chose not to The 'not my area' frame starts to soften into 'not my problem' more broadly You learn — but the lesson is more expensive than it needed to be

A sentence to sit with

Write the bug report tonight if you found one — and schedule it to send at 8:55 Monday. Close the laptop. Both versions of you keep their word.

Ethical Dilemmas

You Found a Bug After Hours — Disclose or Stay Silent?

Sunday night, scrolling your own company's product, you find a quiet but real bug. Customers haven't noticed yet. You weren't on-call. Disclosing means an interrupted week. Staying silent means the next person who finds it isn't a sympathetic one.

🐞 Mid-level engineer who stumbled on a quiet but real production bug at 11pm Sunday 5 min

A guided self-diagnosis — no signup, nothing leaves your device.

Loading Psychology Insights...

Preparing your mental wellness content