I have read similar thoughts before, and have myself thought similarly many times. Today I came across this write-up by Prof Terence Parr, author of ANTLR and I hope people will pay more attention to the point he puts because of his credentials. I have mostly worked in teams maintaining successful software products and invariably I have seen a huge effort towards preparing sacred 'specifications' which mostly lead to delayed and badly-written code which creates more problems than it solves. I don't know when I will see a shift towards having better-written code as the first priority.
No comments:
Post a Comment