Anyway, I'm fine. These posts brought to you by the Utter Despair of Other People's Broke Ass Shit.

All is darkness, chaos and the fog of war. Fires burn bright and wane as energy dissipates into entropy. The dark and cold settle in, and the ties that bind fail. And all crumbles. And all is still.

Why did you write code that is hard to test? Why did you choose a system architecture that is hard to test?

Isn't the whole point of doing architecture to make something that is _easy_ to build, _easy_ to test, _easy_ to ship?

Why did you make choices that made it harder?

Also: I don't care if you believe in DI. I don't care about auto wiring or IoC containers.

But if you want to give yourself some self care do this one thing: most functions that need to know what the "current time" is should be getting that current time from their caller.

`new Date()` is a smell.

Plus, I don't know who needs to hear this but: assertions on spies à la `expect(spy).not.toHaveBeenCalled()` are guaranteed fragile unless the spy is a dependency you're injecting.

I'm rejecting PRs that spy on the function that performs the specific side effect you want to assert on from now on.

Run. All. The. Tests. All. The. Time.

If running all your tests is annoying, get mad!

If a test is flaky, delete it! Version control has the history if you want to bring it back.

If your code is hard to test, fix your code!

"Oh, but CI runs the tests much faster"

Make your tests faster.

"Oh but there's fewer flakes in CI"

Make your tests less flaky.

A test suite you can only get to pass by smacking it with the right magic want the right number of times in the right room is a useless test suite.