"Finally, while our findings do NOT support the existence of a pink tax as conceived by regulators, a more expansive definition of the pink tax could include differences in markups across men’s and women’s products."
"...our finding that women’s personal care products are not systematically more expensive than substantially similar men’s products calls into question the role of government intervention to reduce the pink tax."
1. Add a staging environment.
2. Add a CICD.
3. Add tests. Start by easy ones (new features) to get team used to writing them. Then important flows. If your team doesn’t have the bandwidth hire a contractor. Ex: https://avantsoft.com.br
4. Choose a part of the code the warrants being the first to refactor. Balance easiness with importance.
5. Define a better structure/architecture for it.
6. Refactor.
7. Repeat from 4 as many times as needed.
Also, consider micro-services on new features… may be an alternative to full rewrite.
Should it be done by the ISP? By the IaaS? By the software provider? By developers?
Ideally, moderation would occur at just one level. That way, there are less avenues for abuse to occur. Leaving moderation rules vague may lead to some services that could be beneficial (whistleblowers, etc) to be easily taken down.
It turned out he had set another setting incorrectly which was causing the appointment never to be valid.
But the rarity of the date let me wonder in the wrong direction for a while...