An afternoon of more presentations, which were a bit more technical in terms of data indexing, storage, and use. As a result, there are no detailed posts, but here are a few notes and takeaways.
- Be careful when you try to parse a bunch of files you download from the web. Parse and store, distribute up front, and build a test index first.
- Making Software Work – read it
- The results of one study is not the truth.
- It’s hard to make a study repeatable.
- Does agile work? That’s the wrong questions. Really, when does bug fixing has the highest cost?
- High-risk bugs should be done as early as possible, instead of the easy bugs.
- What language? Depends on the problem.
- Make developer happiness hours. (block off time with no meetings)
- Give people open sight lines instead of high cubicle walls.
- Be as transparent as possible (e.g. JIRA) including progress.
- Put projects into short iteration cycles.
- No code without passing tests!
- Slides (PDF) for the last talk: Practical Agile: What’s Working for Stanford, Blacklight, and Hydra by Naomi Dushay
In-browser Data Storage and Me
by Jason Casden, North Carolina State University
- Suma: data collection application using in-browser storage.
- Indexed database API (aka IndexedDB, WebSimple DB) is where things seem to be going, but limited browser support.
- Web (DOM) Storage is basically universally supported.
- Web SQ DB still viable option.
- lawnchair: object storer, but have adapters for a long list of DBs/APIs.