I had a job interview a few weeks ago where the lead developer straight-up said that he doesn’t have any tests in the codebase because “it’s just writing your code twice”. I thought he was joking. Unfortunately he was not.
I didn’t end up getting the job, perhaps because I made it clear that I thought he was very wrong. I think I dodged a bullet.
I once had a startup founder tell me that “tests are a lack of confidence.” I later did a security review against their company as part of an acquisition. It did not go well…
I had a job interview a few weeks ago where the lead developer straight-up said that he doesn’t have any tests in the codebase because “it’s just writing your code twice”. I thought he was joking. Unfortunately he was not.
I didn’t end up getting the job, perhaps because I made it clear that I thought he was very wrong. I think I dodged a bullet.
I mean there is arguments against creating test for everything but that definitely isn’t a good one…
I once had a startup founder tell me that “tests are a lack of confidence.” I later did a security review against their company as part of an acquisition. It did not go well…
I bet you could no show at that job for 6 months before they fired you. It’s free money.