Tag Index

 algorithms (1) code-availability (1) comments (8) data (1) debugging (1) deprecated (1) development-process (1) docstrings (3) documentation (19) dry (2) errors (4) examples (4) file-level (5) functional-programming (1) getting-started (1) github (1) gitignore (1) guidelines (1) hardcoding (1) imports (1) installation (1) last-pass (6) logs (1) manpage (1) mentorship (1) meta (3) motivation (1) naming (5) notebook (2) optimization (2) parameters (5) pipeline (2) plots (2) process (6) publications (1) published-code-critique (22) readability (1) readme (6) refactoring (4) runnable (2) science-meaning (2) screed (3) self-documenting (2) software (1) starting-projects (1) style (4) tech-debt (1) testing (4) time-management (1) tutorials (1) usability (2) version-control (2) whitespace (1)

 algorithms (1)

Not every speedup is snazzy

 code-availability (1)

Sharing accessible code

 comments (8)

Your abbreviations are not obvious
Understanding an API
But why?
Simplicity does not excuse bad comments
Double-check your comments
Explain your science
Crediting sources in your code
Repetitive comments

 data (1)

Self-documenting data files

 debugging (1)

How verbose is that log?

 deprecated (1)

Removing deprecated subcommands

 development-process (1)

On quick issues

 docstrings (3)

In praise of writing documentation
Script docstrings
Describing parameters in docstrings

 documentation (19)

The work is not in vain
Thanks for telling me how to contribute
Why even have a manpage?
No one cares about your guts
Give me a roadmap
Finding time for documentation
Sometimes the example should be big(ger)
Understanding an API
Documenting the magic button
Revamping documentation
Documentation and mega-tools
Provide context for code
Documenting options
Directory READMEs
A pretty good README
The art of toy data
Use data files
Help others help you
In praise of writing documentation

 dry (2)

Extracting the core
Don't Repeat Yourself

 errors (4)

Quality of life updates
Include sources in error messages
Parameters implying other parameters
Useful error messages

 examples (4)

Releasing code without data
Sometimes the example should be big(ger)
Examining demo code samples
The art of toy data

 file-level (5)

Filenames matter
Putting scripts under version control
Directory READMEs
Organizing files for code
Script docstrings

 functional-programming (1)

No one cares about your guts

 getting-started (1)

Documentation and mega-tools

 github (1)

On quick issues

 gitignore (1)

Knowing what to leave out

 guidelines (1)

Thanks for telling me how to contribute

 hardcoding (1)

Config files vs. hardcoding

 imports (1)

Including version numbers in your code

 installation (1)

Tell me how to install this

 last-pass (6)

Updating explanations of meaning
Double-check your comments
Don't Repeat Yourself
Reproduce your work
Do a final cleanup
How I document code

 logs (1)

How verbose is that log?

 manpage (1)

Why even have a manpage?

 mentorship (1)

On quick issues

 meta (3)

The work is not in vain
Schedule update
One year later

 motivation (1)

The joy of tidying code

 naming (5)

Your abbreviations are not obvious
Using simple structs
Use data files
Help others help you
Using keyword arguments

 notebook (2)

Keeping track of results by commit
Keeping a "dry lab" lab notebook

 optimization (2)

Not every speedup is snazzy
Optimization vs. readability

 parameters (5)

Config files vs. hardcoding
Parameters implying other parameters
Documenting options
Using keyword arguments
Describing parameters in docstrings

 pipeline (2)

Maybe it should do less
Documenting the magic button

 plots (2)

Config files vs. hardcoding
Magic numbers in plotting

 process (6)

Keeping track of results by commit
Don't Repeat Yourself
Reproduce your work
Keeping a "dry lab" lab notebook
Organizing files for code
How I document code

 publications (1)

Sharing accessible code

 published-code-critique (22)

Knowing what to leave out
Thanks for telling me how to contribute
Magic scripts still need documentation
Filenames matter
Releasing code without data
Code is for running, not just reading
Reading some tests
Your abbreviations are not obvious
Spacing out
Understanding an API
But why?
Examining demo code samples
Documentation and mega-tools
Tell me how to install this
Simplicity does not excuse bad comments
Provide context for code
Double-check your comments
Format your code
A pretty good README
Use data files
Help others help you
Do a final cleanup

 readability (1)

Spacing out

 readme (6)

Magic scripts still need documentation
Documentation and mega-tools
Tell me how to install this
Provide context for code
Directory READMEs
A pretty good README

 refactoring (4)

The joy of tidying code
Revamping documentation
Optimization vs. readability
Extracting the core

 runnable (2)

Releasing code without data
Code is for running, not just reading

 science-meaning (2)

Updating explanations of meaning
Explain your science

 screed (3)

Commit your clunkers
Include sources in error messages
Explain your science

 self-documenting (2)

Self-documenting data files
But why?

 software (1)

Including version numbers in your code

 starting-projects (1)

Give me a roadmap

 style (4)

Things I care about too much
Format your code
Magic numbers in plotting
Don't Repeat Yourself

 tech-debt (1)

Removing deprecated subcommands

 testing (4)

Reading some tests
Developing a testing script
Automated tests
The art of toy data

 time-management (1)

Finding time for documentation

 tutorials (1)

Sometimes the example should be big(ger)

 usability (2)

Maybe it should do less
Quality of life updates

 version-control (2)

Commit your clunkers
Putting scripts under version control

 whitespace (1)

Spacing out