But the social network can be open. My current idea is precisely to build this like communick (replacing Mastodon with Takahe) and make it on top of the activitypub-enabled services that can interop with other networks, except that to get accounts at the instances people need to pay the monthly subscription.

Oh, wow, talk about timing.

Last week, I wrote a post asking for feedback for an idea to fund musicians. While the feedback was mostly positive, I realized that what I was proposing wasn’t necessarily restricted to musicians, and could be used as a model for all types of creative work. So I decided to take this whole thing and make a prototype for a “paid social media network where people and companies can contribute to anyone working in a creative project”

I’ve been doing for months already and have not been banned/shadowbanned.

PS: please stop with the stalking. You have been downvoting every comment and post of mine for the past days, even when not involved in the conversation. If you continue with this, you will be reported and perhaps you will understand that is not the Lemmy-linking that getting you banned from reddit, but just your obnoxious behavior.

You being shadowbanned and a site-wide censorship of links to Lemmy are two distinct things.

That is absolutely not the case. I have posted many links to lemmy there. The only thing I still do on Reddit is discussion related to Lemmy and fediverser, there is nothing being blocked and I afaict am not being blocked.

Organizations that feel that they desperately need to take that risk, are doing it because they disrespect their team’s time.

Or they are aware they are not in a position to block deployments for 60 hours every week? I’ve felt more discouraged working at companies that blocked Friday deployments because “it could wait until Monday”, and then when Monday came half of the team was blocked or waiting for some new data report that could have been running during the weekend.

It can be the smallest risk in the world, but it’s still a risk.

And it’s up to the Engineering manager (or at least the Release Manager in places where that role still exists) to evaluate what would be the trade-off. If you say that a bug coming from a Thursday deployment could’ve waited until Monday, why can’t a bug that has come from a Friday deployment?

I guess my issue is not in saying “Some things should not be deployed on a Friday”, but with the generalization. Of course there are things that should be okay to deploy on a Friday, or a Thursday night, or when the manager is on vacation… Being strict about it seems anything but “respect for the team”, but a general distrust of the people and the process.

Every change that isn’t already an active disaster recovery can wait for Monday.

I honestly fail to see the difference between “don’t deploy on Friday if this can wait until Monday” and “don’t deploy on the evening if it can wait until the next morning”.

The idea of CD is that changes are small and cheap. No one is saying “it’s okay to push huge PRs with huge database migrations on a Friday”, what is being said is “if your team is used to ship frequently and incrementally, it won’t matter when you ship and your risk will always be small.”

Again: if the changes are small enough and you have automated checks in place, they should not require manual intervention.

Plus, what happens if a deploy on Thursday has a bug which only is manifested on a Saturday?

How is that not easily reversible?

possible new ways

Name two, please.

The author ended up creating a strawman. Allen’s argument was pretty clear: if your deltas are small and your deploy system is fully automated, then no one should be afraid of the risk of deploying.

Given that, if I deploy on a Monday morning and there is a bug on the new release, you revert, reproduce the issue in staging and push only new code when it is fixed. Same thing if I were deploying on a Thursday afternoon or a Friday at 7PM.

Right, but just like in the dating sites, those that come with a huge list of absurd requirements quickly change their tune once they face reality.

If a employer answers the quiz with high expectations and marking all questions as mandatory, they will find out that the only candidates that can satisfy the criteria are likely to be unavailable or out of their price range, and then will adjust accordingly.

That as well! :)

The questions I am giving as an example are already there. What I am asking is to people to sign up, go through these questions and provide some feedback.