"We need to reduce the scope of the project, guys... What if we don't make tests? They're taking some time do write, so..."

Yep. Let's compromise the quality and call it scope reduction. It will make wonders to our roadmap 👍

Splendid idea

CTO: No need for tests, comments, or documentation! Just take more time to write good code without bugs!
me: ... But comments help new devs...
CTO: No need for that! Just read the code! It is all there!

He said that unironically. To his defence - he used to refactor random parts of the codebase, so any tests, comments or docs were outdated, or irrelevant very quickly.

Wait, you guys actually have unit tests?!

@galena believe it or not, someone in the past (before I started this job) introduced this testing culture to the company and quality actually improved! Then tests became part of our definition of done and most of the codebase is covered by tests (specially new code).

But now that "doing the right thing" is getting in the way of "finishing this project fast" this manager tried to bypass it. I expressed my concern and then I got backed up by the Engineering Manager. I think we're going to keep the tests for now :)

@tokenguy I dread that the bare metal projects I work on, do not offer any sort of automated testing. Also Git works kinda meh as a lot of it is binary files. So anyone mentioning that tests are important makes me die a little inside of envy.

I miss writing tests and not having to manually test and verify things