30
edits
Changes
→Presentations or Workshops
* Development tips from the front-lines: Tips and techniques useful for software development in Libraries. Jon Gorman, University of Illinois (at Urbana-Champaign). Last year's Code4Lib Midwest there was a great amount of interest in improving development skills. Jon doesn't claim to be the best developer, but he's will to share what intimidated him unnecessarily and useful tips & tricks for both improving skills and overview of techniques that make life easier. (Bootstrap, jQuery, Rule engines, templates, Good books to read, etc). (Note: I'm willing to bump this down to a very quick lightning talk if people aren't interested, I just thought the schedule looked like it needed some fleshing out).
* Can you do FOSS at your library if you're a small, one-person shop? How do you figure it out? Megan Kudzia, Albion College Library. I've made plenty of mistakes along the way, and I thought maybe others might find what I've figured out useful. As a community that values free/open source, it can be really difficult to assess if you're starting out in your career and you're pretty much "the technology person" at your library (I suspect there are a lot of us in this boat). In addition to mistakes, I've had some successes too, which I'll also share about - it's not all bad news! (Note: like Joh, I'm willing to bump this down to a lightning talk if folks aren't really interested).
* '''Deploy Code with Confidence (with lots of tests and application monitoring)'''.
** Deploying code into production can be nerve wracking. Or, it can be a non-issue. I'll talk about our current test environment, which allows us to feel reasonably confident our code does what we intend. I'll also discuss our application monitoring, which informs us when even our huge test suite missed a scenario. We often see bugs in our monitor, write tests to demonstrate the bug, fix the bug, and deploy code before a user ever reports a problem.
** Jeremy Prevost, Northwestern University
===Lightning Talks===