You can set it to not show posts you have already seen.
You can set it to not show posts you have already seen.
Kebabpizza
Electric cars don’t have more data collection than other modern cars. They all collect your data, regardless of the energy source.
This needs to be regulated.
You cannot seed files that are altered. It’s not the same files anymore.
So yes, as long as you want to continue sending, you need to keep the original files around.
I agree with this but I suspect that a lot of the backend is dependent on other in-house infrastructure so it’s not as easy as most people think.
We have well established ways to deal with secrets. Also, everyone is responsible enough to not self approve changes where they do things they are uncertain of.
We very seldom resort to self approvals. Everyone in the team see code reviews as important. But also that progress trumps code review.
Who said anything about only requiring 1 reviewer? And no, I did not drop an /s. You should try working for a healthy team where everyone takes collective responsibility and where the teams progress is more important than any one person’s progress.
We decided that everyone in the team is allowed to approve changes. If no one has reviewed your change within 24 hours you are allowed to approve it yourself. It will usually come up in the daily sync that a self approval is imminent, which usually leads to someone taking a look.
Anything remotely resembling a snack will not be left for long so we don’t keep anything.