Yes, I always review the code, just avoid nitpicking the hell out of it.

Not really, we are a small team and we generally trust each other. Sure there are things that could have been better, but it’s not bad either.

But they are sooo adorable 😍

Sounds fun, mind sharing your field?

Judging on other replies, it seems there are alot of people in IT/software development field that are burnt out by how fast everything is changing. That’s people that understand it, are making an honest effort, but still it’s too much.

Tbh, it makes me dread for my future…

I am definitely guilt for that, but I find this approach really productive. We use small bug fixes as an opportunity to improve the code quality. Bigger PRs often introduce new features and take a lot of time, you know the other person is tired and needs to move on, so we focus on the bigger picture, requesting changes only if there is a bug or an important structural issue.

That sounds a bit misleading, the server implementation is FOSS too, at any time someone could setup their own instance.

There is Alovoa, it’s open source, still has a small user base, but you don’t have anything to lose…

If you don’t mind sailing the high seas, you can download the audiobook from https://rargb.to/ for free.

6=3+3, 7+3=10, 10+3=13

PS I had to edit this post because of typos.