Re: 1980s computer science
@Mage - "Agile promotes bad practices." I would partially disagree. The key concept behind agile development is all the important groups are kept in the loop as the project develops. One idea is to have regular meetings with everyone with relatively short deadlines for completion of project segments. The other concept was flexibility coupled with each problem requires a somewhat different approach. Manage the project appropriately and include all the necessary documentation, testing, etc. So far nothing wrong with the concept. But what has happened is Agile has become ossified by PHBs, PMs, MBAs and assorted other "paint by the numbers" imbeciles. Now you have "scrums" and 2 week sprints, etc. instead of what might be required. Also, the imbeciles tend to be enamored with playing buzzword bingo without ever bothering to understand what they are babbling about.
An example is the belief that Agile eliminates the need for proper documentation and testing. It does not. Both are necessary for one to produce a quality product. However, the one agile idea is the documentation will probably be revised as the project evolves is valid. This is different from having little or no documentation. Testing is critical because a good test program uses people separate from the developers and programmers. Often the worst person to test code is the original programmer because they are too familiar with it.