Let integer \(a,b \in \mathbb{Z}\), where \(b \neq 0\). We say \(b\) divides \(a\) (i.e. \(b|a\)) if there’s some \(m \in \mathbb{Z}\) such that \(a = bm\).

additional information

division algorithm

Let \(a,b \in \mathbb{Z}\), \(b > 0\). Then, there exists, uniquely, some \(q,r \in \mathbb{Z}\) such that \(a = bq + r\) with \(0 \leq r <b\).

“division with remainder”

You will note that, if \(a < b\), we can just say \(q = 0\).

Divide by \(2\pi\), or, how I learned to start worrying and hate Fourier Transforms.

Hello all. Good news first: our frequency theory is now correctly validated by data.

If you want a band-aid for the answer, here it is: divide everything we get out of the cantilever equations by \(2\pi\); then, use the correct linear mass density: our Google sheets was off by a factor of almost \(4\) because of later-corrected apparent measurement error.

Dopamine optical sensor. When dopamine is bound, it floreses and can detect micromolar changes and dopamine concentration.

See also Software Development Methodologies

documentation

• Comments
• Readme
• Wiki

specification

• UX
• UI
• High-Level Architecture (libraries, external APIs)
• Low-Level Architecture (modules, functions, internal APIs)

commenting

• Almost anything hardcoded (constants, strings, etc.)
• Anything confusing, tricky, nonstandard
• Historical notes: if something is added/removed, write it down
• TODO for bugs or hacks

README Files

• Best used as a quick-start guide
• What are key pieces of info they will pieces of info they will need?
  • What is your code supposed to do?
  • How does someone run your code?
  • How does a new engineer get set up?
• General overview of how things are laid out, with links to wiki pages with details

Wiki

• In-depth explanation of subsystems and modules
• Separate pages for each subsystem
• Include decisions of their design decisions
• Discussions of why systems are not designed differently

UI/UX Spec

• How do we know what the software is supposed to do?
• Varying levels of resolution
  • User stories
  • All the way up to granular details of UI elements

Don’t forgot to document defaults!