Same for me, I'll notice my computer is a bit loud, realise I forgot to close postman and it's just sitting there, doing nothing, minimised, and my 12 core CPU is sat at 20%.
I close postman, within seconds the fans spin down.
I've tried a few alternatives but the rest of the team use postman and we've got shared collections and pretty extensive pre-request scripts and nothing else I've tried really fits the bill.
That's a cool idea for an automated offline backup. My equivalent is an external hard drive connected to a mechanical timer plug. Every day it turns on for 30 minutes, that triggers a script that mounts the drive, syncs my files, then unmounts the drive. Then the plug turns off the drive until tomorrow.
I like this better though. I've got an old pi1 somewhere, might have to try it.
I really hate the projects I work on where they've overtested to the point of meaninglessness. Like every single class has a full suite of tests mocking every single dependency and it's impossible to look at it without breaking 50 test cases.
Similarly I hate the projects with no tests because I can't change anything and be sure I've not broken some use-case I didn't think about.
Much prefer the middle ground with modular, loosely coupled code and just enough tests to cover all the use cases without needing to mock every single little thing. It should be possible to refactor without breaking tests.
"How many Transporter accidents have there been in the last tens years, Reg? Two... three? What about the millions of people who transport every day without a problem" - Geordi - TNG Realm of Fear S6E2