Narrator: What they didn't realise was that there were no production examples as it's experimental code. What @Kingy will actually show is examples of pattern matching from other programming languages. @jamgregory, you're fired! 🔥

Do you remember when you joined Twitter? I do! #MyTwitterAnniversary #ruby #rubyfriends

Spotted in this week's @RubyWeekly - our @piotr_murach and the TTY::Logger gem 👏 You can read the newsletter here: rubyweekly.com/issues/460 Give the gem a look here: github.com/piotrmurach/tty-l…

There's a balance to be struck between correctness, design and speed. There's an argument that design and performance kind of go hand and hand - good design will include thoughts about performance.

Within the Ruby community, lots of people say you should use 'single quoted strings' over "double quoted string". However, benchmarking both methods shows there's really no difference!

Lots of people will have heard the quote "premature optimization is the root of all evil". However, that misses out a very important part of the quote - "we should not pass up our opportunity in that critical 3%"

We're going to be thinking about how we can use RSpec to do performance testing. There's three angles we want to focus on: - Execution speed - Resource usage - Scalability

We're delighted to welcome @piotr_murach back to ShRUG to talk about testing... but specifically whether the code is fast and memory efficient.

In summary, you can help improve the dev/PM communication by being proactive, asking for feedback, defining what isn't working, finding a solution, and reviewing and iterating on those solutions as needed. Great suggestions from @fannivuniconnu, and lots to think about!

Is Scrum appropriate for the team? Or would Kanban be better? Do you need estimates? Define the workflow for your team, and then negotiate scope that you will work on.