You're viewing a single thread.
It would be nice if it was possible to describe perfectly what a program is supposed to do.
Yeah but that's a lot of writing. Much less effort to get the plagiarism machine to write it instead.
Someone should invent some kind of database of syntax, like a... code
But it would need to be reliable with a syntax, like some kind of grammar.
That's great, but then how do we know that the grammar matches what we want to do - with some sort of test?
How to we know what to test? Maybe with some kind of specification?
People could give things a name and write down what type of thing it is.
A codegrammar?
We don't want anything amateur. It has to be a professional codegrammar.
What, like some kind of design requirements?
Heresy!
Design requirements are too ambiguous.
I'm a systems analyst, or in agile terminology "a designer" as I'm responsible for "design artifacts"
Our designs are usually unambiguous
Design requirements are what it should do, not how it does it.
That's why you must negotiate or clarify what is being asked. Once it has been accepted, it is not ambiguous anymore as long as you respect it.
What did you said?
This still isn't specific enough to specify exactly what the computer will do. There are an infinite number of python programs that could print Hello World in the terminal.
I knew it, i should've asked for assembly
I think our man meant in terms of real-world situations
And NOT yet another front page written in ReactJS.
Oh, well, that's good, because I have a ton of people who work with Angular and not React.
Ha
None of us would have jobs
I think the joke is that that is literally what coding, is.