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

@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 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.

I disagree. You should code in a way where you would see ASAP if something doesn't work. This is why we write tests for big projects that take a long time to compile, because it is faster to run them.

@topsecret230 wait a min, lemme get my unit test barf bag… what were you saying again?