loading words...

Jul 06, 2019 23:35:02

Brighton Ruby Summary

by @craigpetterson PATRON | 465 words | 192πŸ”₯ | 193πŸ’Œ

Craig Petterson

Current day streak: 192πŸ”₯
Total posts: 193πŸ’Œ
Total words: 51456 (205 pages πŸ“„)

# IM CHEATING. IM AT 400 WORDS, SO IM POSTING TO KEEP MY STREAKS. IM STILL EDITING! #

Yesterday, I posted about my trip. Today I'm posting about the event and the talks.

There was a total of 12 talks, so the day ended up being quite long. I often get restless - need to stretch my legs, get a drink - but there was nothing I wanted to miss!

This is just going to be a brief summary of the talks and things I remembered.

Setting Up To Fail @vaidehijoshi

A great introduction to Brighton Ruby. A talk about the basics of distributed system and expecting them to fail. It was simply discussed while still acknowledging the difficult of it all. It's easy for people to talk about complex problems and how to solve them, but it's hard to avoid saying thing like just do this incredibly complex thing first.

Why Should You Care About Cultivating Trust? @GarethMarlow

People Debt and Trust are an exceedingly large part of any group, community, employment and we need to learn to improve on these factors. I particularly enjoyed the pyramid (from a Google project) regarding effective teams. I feel like I can take some of the knowledge shared in this talk into work to improve my life and that of those around me.

From Developer to Architect (and back again) @matthewrudy

The slides are available already. Matthew seemed to do some cool work, including working with the MoJ. I thought the next step after Lead Developer was Lead Developer and then again in bigger letters. It's interesting that more experienced coders and seniors do less code first. A wise, young ex-colleague said that 80% of the work should be done without touching the keyboard.

Embracing Openness in Open Source @a_adewusi

This was a brilliant talk. Getting starting in open source or just tech in general can sometimes be overwhelming or completely daunting. There is more we can do to make people feel welcome and Amina helps explain how.

Fixing Performance Problems with ruby-prof @fglc2

Frederik wrote about his experience at the conference.

Better Coding Through Unit Tests @valeriecodes

This was a great talk about animals. So many beautiful animals. Huh? What? She talked about testing too? Riiiiight, yes, yes.

This was a brilliant talk. So many of our problems are based around testing right now. I probably should have took notes on this section. I spent too much time bashing my head against the seat in front of me. It felt like I was being attacked.

The Life Changing Magic of Tidying Technical Debt @sroopsunar

Six Years of Ruby Performance: A History @codefolio

You may have encountered a bug in the Ruby interpreter @qyliss

Ruby like it’s 1995 @matiaskorhonen


Defragging Ruby @tenderlove


If the conference was bad... you could have called it a BrightOFF.

contact: email - twitter / Terms / Privacy