I'm not sure why anyone has been downvoting; I think this is a valid question, even if it seems absurd or the answer is obvious to everyone else.
If there is a language with a compiler that has no error/syntax reporting, the programmer can implement their own error reporting with basic tests and their program has to meet those expectations when they run they run the test program; when all the expectations in the test are met, the program has no known errors. If a part of the test doesn't receive the expected value from the program, then the programmer can know where something went wrong. There might not be error reporting per se, but this would definitely allow for large applications to be written with a stupid compiler or interpreter. This, of course, is under the assumption that we are dealing with languages that have construct which would allow interaction with specific components(functions/methods/classes/modules/libraries/etc.). Even without that, one could write a test routine that would go to a specific line of code and test whatever value gets returned.
Today, what I described is Behavior Driven Development(aka BDD).
Even without such tests, people have written applications with huge code bases without much useful feedback. Depending on what form of assembly language one writes in, you may get no feedback except unexpected behavior. Many C compilers don't have much useful feedback; not like that of modern interpreted languages. Chris Sawyer wrote the original Roller Coaster Tycoon in mostly assembly and some C, which was definitely larger than 10 lines and I'm willing to bet that much of his development was based upon seeing whether or not he was getting the expected behavior from his code.
EDIT: Better yet, it just so happens that I had an experience about 5 days ago where I wrote 126 lines of Python code and it worked the first time I ran it. That doesn't happen too often, but it shows that even a mediocre programmer such as myself can write more than 10 lines of useful code without error checking. It just takes a lot of thought and planning.
Let's also not forget that before QWERTY keyboards and modern file systems, people wrote programs and even simple games by punching holes in cards and the programs were stored on big stacks of punched cards that were inserted into a giant computer; the program either worked or it didn't, and it was simply not practical to rely on feedback from the computer. Using a computer was also a privilege for most, as not everyone had ownership or access to one on a regular basis. The equivalent of 10+ lines of working code was written this way.