Our CTO doesn't believe that tests improve code quality. We have no tests on any level, no testers/QA, no code reviews. Nada. I wonder why production keeps breaking 🤔 Guess I'll start looking for another job 🤷‍♂️

"It compiles - Ship it!"
- This CTO

To quote: Everybody has a testing environment. Some people are lucky enough enough to have a totally separate environment to run production in.

Living on the edge ftw!!!

@gathurian Yes. Didn't know it was this bad until we talked about it. I kinda assumed we were missing some stuff because it's a startup and they had to "move quick" or whatever, and that it would eventually get fixed. You know, because we supposedly took the incidents seriously. Fuck, fell for it again.

@ExGetMessage I'll remember that one.

Testing is for noobs.

Write it, zip it, deploy it.
Your customers are now the testers.

I know that feeling...

Introducing something most are unfamiliar with is irritating at best...

But at least people at my company start understanding the value of testing... Slowly... Veeeery slowly...

jesus christ, are 90% of dev jobs shitty?

@erandria probably close to it.

Without testing, you have 2 options

- hire or buy monkeys to do manual testing.
Selling testing monkeys it's a very profitable business for outsourcing software companies.
Monkeys are easy to find, cheap and replaceable.
On the contrary, developers with testing in mind are expensive, difficult to find, with horrible personal traits and ambitious.

- hire a Powerful Key Account Manager that plays golf with other CEOs. So whenever horrible bugs arise or quality is below standards, he can just fix things in business way. It's more expensive, but sometimes more effective

Make your choice

BTW Testing DOESNT improve code quality.
Actually the contrary, you can leave the code quality like shit if tests are working.

You can refactor later if and when necessary, or not.

Testing improve the overall development and deployment process

@deviloper Hm, I guess I wanted to say that testing and other "quality increasing" activities reduce the amount of bugs that make into production.

@erandria Yes, yes they are.

I thought the T in CTO stands for Technology.. Maybe not.

@jurion sadly no. But I was a tester based on my comment 😉

@jurion There's 4 of us right now, will probably expand soon.

@jurion Never mind Netscape, that's how lots (maybe even most, sadly) of companies *still* work.

I'd love a tester for every few devs. However, I could spend my entire working day, every day, making a great case for this, and it'd still never happen. I don't think I'm alone in that situation.

@jurion What makes you think they get devs to do testing? 😉

@jurion That's probably what they *say*. But it's practically impossible to useless for devs to thoroughly test their own stuff, even if they wanted to. Ergo it usually just doesn't get done.

Also you test one thing and the next release you just guess that the feature didn't change because testing the whole system - all features in all different cases - isn't practical. So you make an educated guess based on which parts of the code base was touched. Then you release it and obviously some strand of spaghetti code reached a part of the system in a non-obvious way and now you're fucked. It's the same repeating pattern I've seen in all systems I've worked with.