Spyke

Replies

Comment on

Dealing with YOLO Vibelord colleagues

Explain to your manager that if an employee can merge code without reviews, he should expect breakages on regular basis.

Propose that your team can meet to talk about how to make the process better, so no breakages occur.

Mention personal responsibility and knowledge - it’s a good practice that a person who wrote the latest code changes either helps either is responsible for making the service working again, if there are issues - specifically because they might have some idea what’s broken.

If your manager will ignore it, I’d start looking.

Comment on

The Lack of Compensation in Open Source Software is Unsustainable

OP wanted a fun child project, but it's not fun anymore, just responsibilities.

The problem I see is just a difference between expectations and reality.

Expectations were: it would be fun to give people something for free, create open source, be part of some community. Maybe even get some recognition, maybe better job offers.

Reality is: noone cares about your open source project enough to pay for it.

And such is life. Noone stops you from just stopping working on it, and that's an adult option. All open source licences have a clause like "I don't own you nothing", and maybe that's the moment to use it.