Backlog: What Needs To Change, Or We Will All Die

Bugs

While establishing the project, there were a number of occasions where we though to ourselves, “WTF?”, but continued to hack at high speed. This is ok, as long as we gather refactoring records into our backlog.

See Bugs for a number of records from that time.

Refactoring After Featuritis

The first feature that was implemented is UserDB: Alternative Output Format - CSV. Wreaking havoc on the code base, we shoehorned that in, violating nearly every principle that defines our craft (see Design Principles: SOLID). Anyway, this gives us a chance to deliciously and fearlessly clean up the code base after the fact.

• Bugs
  • Existing Files Are Overwritten
  • UserDB::read(): What If Done Twice?
  • UserDB::find() Crashes If User Not Found
• Features
  • UserDB: Alternative Output Format - CSV
  • Search By Other Indexes
• Refactoring
  • UserDB::{read,write}(): bool, Really?
  • UserDB Has Too Many Responsibilities ⟶ BackingStore
  • BackingStore Has Too Many Responsibilities ⟶ Interface
  • Load From BackingStore in Constructor