February Meeting

Creighton Kirkendall will present:

Building with Legos – The Joys and Struggles of Architecting in Clojure


January Meeting

We are having a hack night with Data Science. We’ll break into groups and look at Wine Quality Data and analyze it with your choice or R, Python, or Clojure.

Then we’ll participate in a mini-Kaggle and compare our results

December Meeting

Chris Hodapp will present

Introduction to R

An introduction to the R language, ecosystem, and some of its quintessential libraries (like ggplot2 and dplyr). If time permits,  an entry into some basic machine learning in R.

November Meeting

Join us for Nick Howard’s talk Fun with F# and Type Providers

October Meeting

Carin Meier will talk about


Clojure.spec allows us to generate test data based on our specifications. But what about generating a clojure.spec program based off of data? With genetic programming, we’ll explore creating clojure.spec creatures that consume data for food. Then, we’ll breed, mutate, and evolve them until we have a perfect fitting spec for our data. Finally, we’ll take a step back and think about how clojure.spec gives us the ability to have our programs describe themselves and what that means to AI and self-repairing code.

September Meeting

We have Joe Smith, a developer from Cognitect, giving our first “remote” talk on

A Short, Painful Introduction to Function-Level Programming with J

August Meeting

Kat Tornwall will present:

Painless Test Driven Development with Elixir and Phoenix

Test driven development is a core part of our process at Gaslight, and for our first couple of Elixir applications, we struggled adjusting to writing tests in our Phoenix application after years of working with RSpec and Rails. Luckily, we’ve come up with several conventions, tips, and tricks to help developers write simple, easy to understand unit and feature tests. In this talk I’ll describe how we structure tests, test setup, and helper objects to make TDD as painless as possible. Specific topics I’ll cover are:

  • Naming conventions for organizing tests
  • Using factories and helpers to clean up your setup
  • Splitting tests into files to group them by context
  • Keeping your feature in order with page modules and Hound
  • Writing assertions to generate useful failure messages