Today I read a great article on mutation tests, how to use and why they are important. It looks like a great thing, but...
I have never wrote any unit test in any of my jobs. Nobody in my workplace does that. And now it seems like 100% test coverage is not enough (I remind you, that I have 0%), they all should mutate to check if the quality of unit tests is high.
It seems that I'm left behind. I played with tests in my free time, but it seems the more you write them, the better you get at it, so I should be writing them in my job, where I code most of my time. Not only that, of course, I would also want to ensure that what I'm working on is bug-free.
Still, it will be impossible to introduce unit tests to my project, because they are novelty to the whole team and our deadlines are tight. The other thing is, we are supposed to write minimum viable product, as it is a demo for a client, and every line of code matters. Some might say that we are delusional that after we finish demo we will make things the right way.
Did any one of you have a situation like this? How did you change your boss and team's mind?

Developer creates pull request.

I hold suggesting changes.

Developer creates new branch and new pull request with exactly the same commit.

Another Senior developer approves pull request.

This will be discussed tomorrow morning!

Dear Boss/PM,
If you look over at my desk and I am 'doing nothing', feel free to assume one of the following:
1) I finished what I had to do and am taking a quick break before tackling what's next.
2) I am working on something that is giving me a hard time and am taking a quick pause to refresh.

How many hours of actual productive work do you devs average a day? Honestly, I think I average about 2 hours of honest, good work in my 8 hour day. Between random meaningless meetings that could be emailed out or just daily distractions (coworkers chatting, my phone, etc). Am I alone in this?

Go die in a hole, Eclipse you stupid-ass dumbshit.

Working out how to continue an interview when the interviewee thinks Test Driven Development is fixing bugs raised by the Test Team

When coworkers leave the co. for a better paying job and leave this kind of code after themselves:

int foo = 1;
String.format("blabla %s", Integer.toString(foo));

fml

"We are fairly certain that..."
Don't you just love hearing this from your clients?

PM: 2 months? no thats way too long, do it in 1.

Director: I had a chat with someone else who doesn't work on this team, he says that developer you complained about is a good guy and we should keep him on the team.

Business: No, we don't have time for tech debt, lets build these new features as quick as possible and lets see where we are.

everyone: WHAT DO YOU MEAN IT CRASHED AGAIN??? THIS IS UNACCEPTABLE

always remember, never forget it

🤨🤤🤤
Always