Lessons Learned from our First #RealWorldCode Live Stream
Tags: ruby, learning, devops, rails
Published: 2019-01-14 18:31:21

---
title: Lessons Learned from our First #RealWorldCode Live Stream
published: true
description: Earlier this month, Betsy and I tried to live stream a pairing session and <strong>failed miserably</strong>. But! We had fun, so we had a retro and made a plan for how we can do better.
tags: ruby, learning, devops, rails
canonical_url: https://www.wecohere.com/articles/lessons-learned-from-our-first-real-world-code-live-stream.html
---

Earlier this month, Betsy and I tried to live stream a pairing session and _failed miserably_. But! We had fun, so we spent about 30m performing a [retrospective](http://www.funretrospectives.com/the-retrospective-prime-directive/) on our [_Debugging a Race Condition in Cypress_ event](https://www.wecohere.com/events/january-3rd-2019-livestream-of-debugging-a-race-condition-in-a-cypress-browser-test/?utm_campaign=real-world-code-2019-01-17-lessons-learned). To [expose our ignorance](https://redsquirrel.com/dave/work/a2j/patterns/ExposeYourIgnorance.html) (and therefore, learn more!) we've made our [retro notes](https://drive.google.com/open?id=1CnFlF4UOheK4lnwgOAqJFiz6BKS8RFDG4hzk7YzTv-g) available to you.

The joy of retrospectives is we now have a plan to make the stream flow much more smoothly! The angst of retrospectives is that it can be touch to talk about failure-modes in a positive, proactive way. Thankfully though our years of working together, we've developed [a level of physchological safety](https://hbr.org/2017/08/high-performing-teams-need-psychological-safety-heres-how-to-create-it) that allows us to have healthy, reflective conversations.

#### How We'll Do Better Next Session
The next live-streaming sessions are going to be _longer_! Yes, _Longer_. The main reason for this is we realized that due to A) us having solved the problem before and B) us having logistical difficulties, we didn't get much of an opportunity to enter a state of productive flow.

We know this may be… boringer for you, but we're hoping it will allow us to dive deeper into insights in a more casual manner; so we can pull out the diamonds in the rough out and provide them in more easily accessible chunks.

We're also planning to have someone who is _not_ streaming monitoring the [#RealWorldCode hashtag](https://twitter.com/search?q=%23RealWorldCode&src=typd) and mentions to [Cohere's Twitter account](https://twitter.com/wecohere) to make sure that if logistical issues arise we can resolve them in a timely and inclusive manner.


#### How You Can Attend our Next Livestream
To attend our next livestream, [_Preventing Cascade Failures Caused by Excessive Concurrent Writes_ on January 15th, from 10 AM PT / 1 PM ET to 12 PM PT / 3PM ET](https://www.wecohere.com/events/january-15th-2019-10am-pt-1pm-et-real-world-code-livestream-preventing-cascade-failures-caused-by-excessive-concurrent-writes-in-a-heroku-hosted-amazon-rds-backed-ruby-on-rails-app/?utm_campaign=real-world-code-2019-01-17-lessons-learned), you [may join the stream directly](https://public.aerialspac.es/Pair%20Programming%20Live%20Streams?eventId=d38e706b-9b2c-47fa-a90a-afa5ff1f8724). You may also [RSVP via EventBrite](https://www.eventbrite.com/e/real-world-code-preventing-excessive-concurrent-write-induced-cascade-failures-in-ruby-on-rails-tickets-54729746144?utm_campaign=real-world-code-2019-01-17-lessons-learned) by tomorrow, January 15th at 8 AM PT/ 11AM ET. This _should_ work better than the horrible form I put on the website last time.

Once again, you should be able to [bookmark this link](https://public.aerialspac.es/Pair%20Programming%20Live%20Streams?eventId=d38e706b-9b2c-47fa-a90a-afa5ff1f8724) which will give you a window into the stream when we go live.

We're looking forward to seeing you there! If it doesn't work or you have any questions, reply to this post or tweet at Cohere with the hashtag #RealWorldCode and we'll do our best to get you in quickly <3.


Zee, Betsy and Jackson