If you're a "software engineer" with 10+ years of experience, but you've never written a unit test.... you're just a script kiddie with no right to call yourself a "software engineer".

Testing is important and I can’t imagine writing software without it, but I can see many engineers in long-held positions working on legacy code where the managers don’t even know, let alone prioritize, software testing, and the engineer is just like “meh it seems to work” and really only comes for the paycheque.

Ok retard buddy retard

@ganjaman REEEEEEEEE

That's a harsh statement you made there. There are many programmers like my father when they learned programming oop was the new shiny thing and nobody even heard of unit tests. He still doesnt write unit tests because he never learnt to do it(and has no interest in doing so) but his code is way better than the code of many of the people on this platform.

@EdoPhoenix I see unit tests and BVTs as bare minimum best practices, on par with a SCM, for working within complex codebases.

In contrast, I see OOP as a non-essential, but useful tool for software construction.

To my defense, there is no credit for unit tests in avionics software. There are partition tests and integration tests only. If I was avionics sw developer for 25 years and not a curious person, I would not write them once.

@aviophile You don't write unit tests in embedded anyway, just static asserts.

Don't agree. Although I'm not a programmer with 10+ years professional experience (I've for zero professional experience and I'm a Linux engineer professionally), I have nearly 9 years of 'amature' experience.

I've written many systems and libraries which work well and look good. I've never written a unit test, though.

I know people who write hardware code and build the hardware. Not arduino or so, real hardware developer. It's hard to unit test that code. They do integration tests tho. They still write impressive software.

I've wrote alot unit tests and know what you mean.