Makes sense. IMO contractors are supposed to be companies. Such as https://avantsoft.com.br that you hire for specific things and that can abstract the actual employee management, etc from the company that hires.
It seems the authors did not find evidence of a "pink tax":
"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."
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.
The big question to me is: At what level of the tech stack should moderation happen?
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.
Interesting study. Just reading outputs from GPT3 or other models makes it seem almost lifelike. Sometimes it is easy to forget it is just a well fit function with a lot of parameters.
Slack has an interesting model where the license count charged to the company only includes active users which is a subset of those that are registered.
"Productivity porn is anything that after having been consumed makes you feel like you were productive when in reality you didn’t actually do anything." - Interesting definition.
Are you a very avid adopter of products from early stage startups? Forced updates tend to be more common with small companies that can't devote resources to maintaining backwards compatibility.
Agree. As someone that has had to migrate systems from K8s to Elastic Beanstalks or equivalent, there are definitely situations where K8s is overkill and simpler systems can work better.
Is everyone an employee or are there contractors as well? Are there managers? how large is the team?
For smaller teams (sub 10 people), I find that having 1 daily informal standup and having the leaders make themselves readily available for answering questions is often sufficient. The key is often for leadership not to block development (so no long review cycles for PRs or long time deciding on details that subordinates need to accomplish their work).
I would recommend discussing anything related to compensation before starting at a company (definitely before signing contracts). So would recommend sooner rather than later.
I would recommend talking to a professional. There are psychologists and equivalent professionals that specialize on this and they may be able to provide you some guidance.
Not sure this helps but believe in yourself. The fact that you are even willing to talk about this already shows a level of self realization that few are able to achieve.
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...