Posts with an asterisk after their title are part of my series of critiques of published code.
- 27 Aug 2025: One year later
- 16 Aug 2025: Tell me how to install this*
- 9 Aug 2025: Include sources in error messages
- 2 Aug 2025: Developing a testing script
- 25 Jul 2025: Simplicity does not excuse bad comments*
- 14 Jul 2025: Automated tests
- 28 Jun 2025: Updating explanations of meaning
- 19 Jun 2025: Provide context for code*
- 7 Jun 2025: Using simple structs
- 24 May 2025: Double-check your comments*
- 17 May 2025: Parameters implying other parameters
- 3 May 2025: Documenting options
- 26 Apr 2025: Format your code*
- 19 Apr 2025: Directory READMEs
- 5 Apr 2025: Magic numbers in plotting
- 20 Mar 2025: A pretty good README*
- 14 Mar 2025: Don’t Repeat Yourself
- 2 Mar 2025: The art of toy data
- 15 Feb 2025: Use data files*
- 31 Jan 2025: Help others help you*
- 25 Jan 2025: Reproduce your work
- 10 Jan 2025: Useful error messages
- 4 Jan 2025: In praise of writing documentation
- 23 Dec 2024: Do a final cleanup*
- 7 Dec 2024: Explain your science
- 23 Nov 2024: Keeping a “dry lab” lab notebook
- 16 Nov 2024: Organizing files for code
- 4 Nov 2024: Crediting sources in your code
- 26 Oct 2024: Using keyword arguments
- 14 Oct 2024: Repetitive comments
- 6 Oct 2024: Including version numbers in your code
- 24 Sep 2024: Script docstrings
- 4 Sep 2024: Describing parameters in docstrings
- 27 Aug 2024: How I document code