[ozim]

Just like all the fitness content.

Get couple shredded guys and gals to show off how fit they are so everyone feels guilty they are snacking past 8PM.

Sell another batch of “how to do pushups” followed by “how to do pushups vol.2” with “pushup pro this time even better”.

Where in the end normal people are not getting paid for getting shredded, they get paid for doing their stuff.

I just constantly feel like I am not a proper dev because I mostly skip unit tests - but on the other hand I built last 15 years couple of systems that worked and were bringing in value.

[qznc]

You could switch into a domain where safety-critical software is developed. Here devs complain about the inverse problem: Why are we required to have 100% test coverage?!

(The answer btw: Because nobody would be able to explain to a jury/judge that 80% or whatever is enough)

[pydry]

Or they complain that they know everything has gone to hell but if they blow the whistle revenge will be taken against them.

Everybody who worked with the 2005 Toyota Camry ETCS would have known what was up when it killed a few people, for example. Nobody can work on spaghetti code of that magnitude and not realize that something is off.

Boeing employees who tried to blow the whistle were similarly ignored or silenced while a few died in mysterious circumstances.

[zoover2020]

Why would you skip unit tests? Especially in the AI age. You can quickly verify your behavior. Also, by not writing them you're also missing out on opportunities to modularize your code.

Obviously, this assumes you write enterprise grade code. YMMV

[ozim]

You can write modular code without writing tests - I write testable code - I don't write tests. When I need I can always add them back, but I tend to skip it as mostly it doesn't make sense.

But still cottage industry of "clean code" is pushing me into self doubts and shame.

[capyba]

I’m a mechanical engineer, not a software person, but I write a lot of (hopefully close to professional quality) code for my work. writing tests while in the beginning/middle of my development cycle has been the best change I’ve made in how I do things in quite a long time. Since I’m a self-taught amateur often working solo, its invaluable for helping me gain confidence that everything I’m doing is working correctly as I learn the language/libraries necessary for me to build each new program.

I’m not saying that you yourself have this attitude - but the “tests are for suckers, I just ship” crowd really grinds my gears because to me it says “ha! Why do you care about getting things right?”

Totally get where you’re coming from though, sometimes the expected behavior is trivial to verify or (in the case of GUIs) can be very difficult and not worth the effort to implement.

[esafak]

If it's testable it's trivial to write tests for! You don't want the next person to introduce a bug, do you?

[ozim]

Read my original post again. We don’t have bugs that all those “do it right way” people claim doing it for 15 years with good track record.

You just contribute to BS scare tactics of people selling “clean code”.

[esafak]

How do you know you don't have bugs? Is everything instrumented (observable)? I could just as easily say you're peddling ignorance as bliss!

[ozim]

You can have a lot of other processes and tests on other levels than unit tests ;)

[sigwinch]

That’s how I do it. 100% test coverage doesn’t make bug reports irrelevant. Every test should have a reason.