recap and references

You have reached the end of week 4. During this week, you learned about

• best practices for coding,
• Fortran coding idioms and coding style,
• error handling in Fortran,
• best practices for writing documentation,
• the doxygen document generator,
• how to use a profiler to identify performance bottlenecks,
• hardware features such as vector instructions and caches, and how to exploit those to get optimal performance,
• how to do I/O efficiently.

References

Although a few of the books listed here are fairly old, they are still quite relevant, you could call them timeless classics.

Books

• Modern Fortran: style and usage, Norman S. Clerman and Walter Spector, Cambridge University Press, 2012
• The practice of programming, Brian W. Kernighan and Rob Pike Addison-Wesley, 1999
• Clean code: a handbook of agile software craftsmanship, Robert C. Martin, Prentice Hall, 2008
• Write clean code and get rid of code smells with real life examples
• Design patterns: elements of reusable object-oriented software, Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, Addison-Wesley, 1994
• Refactoring: improving the design of existing code, Martin Fowler, Addison-Wesley, 1999

Articles

• Exception handling in Fortran, Arjen Markus, Newsletter ACM SIGPLAN Fortran Forum, volume 32, issue 2, p. 7‒13, 2013

Online resources

• Fortran best practices at fortran.org

Software stack

• Doxygen manual ## Humor
• Fortran coding style for the modern programmer (Remember, this is the humor section!)
• The evolution of programming languages
• (in 1980) Q: What will the scientific programming language of the year 2000 look like? A: Nobody knows, but its name will be FORTRAN.