I don't just mean partial solutions. I mean code with bugs.
Show this thread
In principle programmers are supposed to write correct code. But I wonder if in practice it's possible to solve really hard problems without incorrect code as an intermediate step.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
(applies not only to programming)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
At least in their heads incorrect code should exist as an intermediate step.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Almost correct code in the final version? Previous ones will have to be tested and debugged. And still, updates may continue.
-
Okay, I was thinking mainly of apps.
End of conversation
New conversation -
-
-
If a novelist can't write a book without a draft that requires editing, why shouldn't a programmer be allowed to write a draft too. The only problem is when a programmer says it's final and there's more bugs than a summer picnic.
-
Never thought of code as "draft" before – and this meaning is distinctly different from a prototype! Will try working with this kind of mindset, thanks for the idea
- Show replies
New conversation -
-
-
Most code doesn't test edge cases and many programmers do not write in function error checking, just assume all functions return properly. Ask around and find rudiments are not really adhered to.
-
Sometimes I wonder whether edge cases are just a by-product of inefficient design. The flows should be simple and at a minimum with the least amount of complexities involved.
End of conversation
New conversation -
-
-
Possible? yes, but statistically the vast majority of possible paths to correct code will contain bugs.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.