If it doesn't work, it doesn't matter how fast it doesn't work.

Are you talking about my superfast regex application with a few bugs? 😁

Someone's never spent an hour waiting for an error message

That’s right. And nobody cares about speed. Speed is just a welcome side effect.
What we care about is correctness. And if it doesn’t work, at least it tells you that it doesn’t work (very fast). Instead of silently failing and pretending to be working.

Well, does it at least fail fast?

Yeah exactly. When your stuff takes an hour to compile and 30 minutes to test, you are waaaaay less efficient at debuging

I mean if I delete it all I'll beat your time and still get your metrics so I'd win, so yes

@Lensflare idk sometimes you might want fast and a little less correct

you could spend forever just building correctness and not having ran anything. just because it's correct, if it's not done / compilable / usable, have you really won anything?

I do believe the triangle was time (fast), quality, cost
you're thinking if you focus on quality you'll be good
but instead you end up with a lot of opportunity cost

@jestdotty if you believe that in order to be correct you need to sacrifice dev speed, then you are already too far damaged by prototyping clown languages to make any judgement on this topic.

@Lensflare it is wisdom of the ancients

and evidently doesn't have a page on https://wiki.c2.com/

and is now considered project management instead of software development wisdom

oh well

times were less toxic and more fruitful once

@Lensflare what about when "correct" is impossible/undefinable? See basically most AI, but also some dsp/signal analysis

Don't understand your rant OP.

Early feedback is always a good thing no?

@atheist yeah, what about it? Correctness in this context is not mathematical correctness or something. It’s just whatever you define it to be. In most cases it can be a list of things that you want to be true and are able to test.