addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartexportfacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Chicago Erlang Users - May 2013

Spring has sprung and Chicago Erlang is back in action! Tell your friends, tell your enemies -- all are welcome!

For building security, we ask that you RSVP to let us know you're coming. We need your full name as it appears on a photo ID. If you're bringing guests, please provide their names as well.

We'll be providing pizza and beverages -- feel free to consider this dinner as well as Erlang awesomeness!


All You Need to Know About Erlang in 40 Minutes

Garrett Smith

If you've curious about Erlang and have 40 minutes to spare, this talk is the place to spend it! will Garrett keep things at just the right level -- not to much detail but still quite technical -- to help you understand Erlang's strengths and weaknesses and give you a solid starting point to learn more!


Deep Dish - Chicago-Style Functional Testing

Evan Miller

Unit testing is easy, especially in a functional language like Erlang that minimizes side effects. But what about applications where you want side effects -- such as delivering information or writing data to disk -- and need to test multi-step workflows effectively? Test code quickly becomes littered with set-up code, teardown routines, and mock objects, and as the application complexity grows, the test suite runs slower, and slower, and slowwwwwer, and…

In this talk Evan will introduce an approach to functional testing that makes the developer's life easier by maintaining a stack of state. Say you have a 10-step workflow and want to test two mutually exclusive options in step 10. Instead of executing steps 1-9 twice, you execute them once, but keep around an "undo button" so that after you've tested the first path in step 10, you can retrace your steps and try another path. The result? Cleaner code, faster tests, and happier developers!


Join or login to comment.

  • Brian C.

    Great talks!

    May 23, 2013

  • A former member
    A former member


    May 23, 2013

  • Karl G.

    Excellent time. Will definitely be back in July.

    May 22, 2013

  • John K.

    Sorry, last minute work

    May 22, 2013

  • Jesse G.

    Garrett was kind enough to squeeze me in here and let me give a quick 10 minute demo of the Erlang date and timezone utility, "qdate." I don't yet know if I'm the opening act, the intermission filler, or bringing up the rear as the caboose. Either way, I'll make it quick so the main acts can get their big shows on.

    May 15, 2013

    • Jesse G.

      As much as it pains me, I'll not be able to make it. My kid developed a fever today, so the daycare won't take him tomorrow, which means I won't have time to make the trek from Milwaukee. The silver lining of this is that the next CEUG meeting, qdate will be more feature-rich, and I can give an even better presentation. Sorry folks, but have fun tomorrow.

      May 21, 2013

  • A former member
    A former member


    May 8, 2013

39 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy