maxdml

### 0 — Purpose
These rules ensure maintainability, safety, and developer velocity.  
**MUST** rules are enforced by CI/review; **SHOULD** rules are strong recommendations; **CAN** rules are allowed without extra approval.

---

### 1 — Before Coding
- **BP-1 (MUST)** Ask clarifying questions for ambiguous requirements.
- **BP-2 (MUST)** Draft and confirm an approach (API shape, data flow, failure modes) before writing code.
- **BP-3 (SHOULD)** When >2 approaches exist, list pros/cons and rationale.

maxdml

### Keybase proof

I hereby claim:

  * I am maxdml on github.
  * I am maxdml (https://keybase.io/maxdml) on keybase.
  * I have a public key ASD5WjWC5-HBpQNMo2GVDAmg86xN1UO2og_lFtnvOeynngo

To claim this, I am signing this object:

maxdml

#!/usr/bin/bash

#DATE=`date +"%m%d%y_%H:%M:%S"`
DATE=`date`
DIR='[your home directory]/results/'
LOG_FILE="results.log"

echo "[$DATE] New backup starting..." >> $DIR/$LOG_FILE

rsync="/usr/bin/rsync -zavHe ssh --omit-dir-times csstudent@[mother-ip]:/var/results $DIR >> $DIR/$LOG_FILE"