2 ms·
I liked the section on testing[0]. I tend to write far more testing code, than the CuT, itself. Many of my various widgets have test harnesses that are, in and
by ChrisMarshallNY 4y ago
I liked the section on testing[0].
I tend to write far more testing code, than the CuT, itself. Many of my various widgets have test harnesses that are, in and of themselves, full-fat, App Store-ready apps.
I find test harnesses are generally better (for me), than unit tests[1].
I was just thinking about this, this morning.
I'm what people refer to as a "crusty oldtimer." I wrote my first program (Machine Code) in 1983, so I've seen some changes in the landscape.
These days, the general posture of many shops seems to be "Our programmers suck, and can't be trusted to write code güt." Sadly, this is not necessarily an inaccurate stance.
It tends to result in highly defensive IT infrastructure and process, though, with heavy reliance on languages and strict, rote methodologies.
I used to write a lot of code in C++. Nowadays, people seem to freak out, at the thought of writing in C++. It's entirely possible to write safe, performant code, in C++, but it isn't enforced by the language. The same for PHP, which I've used a lot.
It's also quite possible for bad programmers to write truly nightmarish code in both languages. I know of which I speak, having written quite a bit of said "nightmarish" code. That's one of the reasons I write fairly good code, these days.
The conventional wisdom seems to be that we need to rely on the tools (languages, IDEs, VCS, CI/D, etc.), to assure good code.
That's fine, but it seems to stem from an unwillingness to invest in the most expensive component in a cubicle; the software engineer.
This is a long, tiresome discussion, with no one willing to change their minds, so I'm not going to follow up on it.
I did notice that this posture seemed to start in the mid-1990s. Before that, companies put ridiculous amounts of trust and investment in us.
[0] https://yoyo-code.com/programming-breakthroughs-we-need/#testing-and-correctness https://yoyo-code.com/programming-breakthroughs-we-need/#tes...
[1] https://littlegreenviper.com/miscellany/testing-harness-vs-unit/ https://littlegreenviper.com/miscellany/testing-harness-vs-u...