TLDR:
"In April 23, 2021, ACI initiated more than 1.4 million erroneous ACH
Entries that were not approved by consumers. These 1,431,377 debit
entries and 1,444 credit entries transmitted electronic mortgage payment
instructions totaling over $2.3 billion to the bank accounts of 478,568
Mortgage Company’s borrowers. As a result, many of these borrowers
unknowingly had multiple debits for monthly mortgage payments
scheduled to hit their bank account on a single day
....
This incident resulted from ACI’s lack of Reasonable Security sufficient
to, among other things: (1) securely segregate Speedpay’s testing
environment (where ACI maintains databases which contain data for use in
testing and development of software before it is used in a production
environment); (2) detect and prevent the transmission of ACH test files
containing SCFI to an ACI contractor; (3) detect and prevent an ACI
contractor from improperly creating ACH test files using SCFI; and (4)
detect and prevent the transmission of those ACH files into the ACH
Network.
On or about April 23, 2021, ACI contractors conducted performance tests
on ACI’s Speedpay platform that involved simulating actual ACH Entry
processing. ACI contractors handling the testing project did not use
“dummy” consumer data (i.e., data that do not contain SCFI) or ensure that
any consumer data in the data files used for testing were scrubbed of SCFI,
contrary to ACI policy."
Like others said - find a therapist. See if your work has a mental health plan, like modernhealth or it's ilk.
It takes some time to find the right therapist and it can be hard to make time in the routine to see one. The good thing is that therapy can be done online. (it's not idea, but during the pandemic it became clear that it can be effective).
Don't wait, start somewhere.
The therapist can help you distill what changes you can make in your life to get to a better place.
I looked briefly (and I could have sworn I posted our "nine rules" on HN years ago, but I couldn't find it in a quick search).
I'll look again later tonight more thoroughly to see if I've posted the mechanisms and restrictions publicly anywhere before. If I haven't, I'll try to dig it out of our old dev doc system and post them here, but I can't make any promises as the docs I recall are now over a decade old, so I'm not fully sure they exist any more. :)
The internal docs for this are not on any of our documentation systems that we've moved to zero-trust (as they're 12 years old and unchanged for 5+ years). I will probably be able to retrieve them when we're back in the offices; shoot me an email (in my profile) and I'll find a way to get something over to you with some significant delay.
in my experience, most service API grow by accretion and need to break backward compatibility very very rarely. Naturally, clients should always be Tolerant Readers.
So in many case, you will have only a single version per service.
Moreover, imo, when we are talking about internal apis, there should be nothing preventing the service owner from updating the consumers if he wishes to converge more quickly after breaking compatibility - just like he would when refactoring a monolith. The culture should allow and encourage this kind of collaboration.
In contrast to conventional internet where classical 1s and 0s are transmitted via some medium like copper or fiber optics or radio waves, qbit states are far too fragile to survive such transportation and so would be transmitted via the quantum teleportation protocol.
Physical networking infrastructure will still be necessary; teleporting a qbit requires a pre-existing entangled qbit pair in addition to two bits of classical information, so you'll need some method of sending one half of an entangled qbit pair to the recipient. It's okay if this process is lossy, because you can easily generate & re-send an entangled qbit if it gets lost. Once you successfully manage to get the entangled qbit through, you can use it to teleport the qbit you actually want to send (whose state is presumably the product of some long, expensive computation and therefore far too valuable to risk sending via such a lossy channel).
TLDR: "In April 23, 2021, ACI initiated more than 1.4 million erroneous ACH Entries that were not approved by consumers. These 1,431,377 debit entries and 1,444 credit entries transmitted electronic mortgage payment instructions totaling over $2.3 billion to the bank accounts of 478,568 Mortgage Company’s borrowers. As a result, many of these borrowers unknowingly had multiple debits for monthly mortgage payments scheduled to hit their bank account on a single day
....
This incident resulted from ACI’s lack of Reasonable Security sufficient to, among other things: (1) securely segregate Speedpay’s testing environment (where ACI maintains databases which contain data for use in testing and development of software before it is used in a production environment); (2) detect and prevent the transmission of ACH test files containing SCFI to an ACI contractor; (3) detect and prevent an ACI contractor from improperly creating ACH test files using SCFI; and (4) detect and prevent the transmission of those ACH files into the ACH Network.
On or about April 23, 2021, ACI contractors conducted performance tests on ACI’s Speedpay platform that involved simulating actual ACH Entry processing. ACI contractors handling the testing project did not use “dummy” consumer data (i.e., data that do not contain SCFI) or ensure that any consumer data in the data files used for testing were scrubbed of SCFI, contrary to ACI policy."