souperk

As always I would say there is a huge "it depends".

For context, I am part of a small team of engineers, working on a relatively new product, we have continuous deployment setup for our release branches. We prefer many small PRs, think at least a PR a day per engineer.

I am responsible for setting up a new e2e test suite right now, so it's possible I reconsider later on. But, there are a couple lessons learned from our previous iteration.

1. Our pipeline was slow (20-30 mins), flakiness was a no go. Decreasing pipeline time increased tolerance for flakiness.
2. Flakiness on the pipeline translated to flakiness on the production instances. When we started caring for those our sentry got much more happy.
3. We didn't have the time to go back and fix issues, so we stopped having nightlies. If it's important enough we should block merging on main and fix it.

it hurts to not think that way, sometimes a lot.

That almost made me cry.

I don't want to find a balance though, I want to find people who care.

I need a community to tag when I encounter a wild greek involved in software development.

Wondering if there is a P2P distributed storage solution we could be using?

I am trying to get started on a treatment at the moment. This made me anxious.

I had to reread the whole thing 5 times to make sure there water isn't one of the labels.

I am going back to work from a week of vacation, somehow I really needed to hear this.

Good luck to you too!

I think I am always right!

Using a VPN resolved the issue, I am going to send a complaint to my ISP just because fuck them.

Is ethical analytical a term? I will lookup Matomo, thanks awesome stranger!!

I cannot upvote enough, I just heard distance is a problem and I needed a kind stranger (like you) to explain why that's not a problem.

Got any references for me to read? I would like to learn more

PS fuck capitalism

My fucking drunk self, highly agrees with you.