Do you ever stop and wonder if the library you’re about to “gem install” is safe? Have you thought about what’s the worst that could happen by using a gem? Today, I (yes, yours truly) explore those questions in a talk I gave a RuLu this summer.
What’s the worst that could happen if your app has a dependency on a malicious gem? How easy would it be to write a gem that could compromise a box? Much of the Ruby community blindly trusts our gems. This talk will make you second guess that trust. It will also show you how to vet gems that you do choose to use.
Being a Pivot means pair programming 8 hours a day, 5 days a week. If you’ve never paired before that might sound crazy, but ask any Pivot and they will tell you how incredibly awesome it is! If you can’t find a Pivot nearby to buy a beer and pick their brain on how full-time pairing works, check out this video of John Foley talking at RubyKaigi 2013 about his experiences pairing at Pivotal Labs.
Pair programming shares a similar philosophy with Ruby- the focus is on people solving problems for other people, not the machine. I want to share my experiences with pair programming and how it helped me become a better engineer, enjoy coding more, and maybe even grow as a person.
Ever wonder how that one gem you use all the time came to be? New York Pivot, Mike Dalessio, tells the story of Nokogiri in today’s video from GoRuCo 2013. Watch to see how what started as an email conversation, turned into a gem with 12 million downloads!
Today I present to you Lisa Crispin speaking at TestBash 2.0! Lisa discusses why you should learn the business domain you are working in, how you can do it, and follows it up with some great success stories from her and the audience. Understanding the business you’re working in is SUPER important not only for testers like Lisa, but also for developers, designers, and everyone else on the team!
You don’t have to learn the business domain to do a lot of valuable testing activities, such as exploratory testing. However, if you want to really make sure a feature will solve the business problem as intended, or help your stakeholders get the minimum they need cost-effectively, you should aim to become an expert in your company’s business domain.
I will share some of the ways my teams and I have been successful in learning about businesses and customers, and how you can apply that knowledge to deliver solutions that exceed both of their expectations. Participants are invited to share their own experiences in becoming business experts and how that helped them, or perhaps held them back.
This week on Pivots Talking Tuesday, I present to you Austin Vance speaking on using Ruby with Arduinos at Ruby Conf 2012. If you’re wondering what the thing is he’s standing next to, it’s a Ruby and Arduino powered tshirt cannon… and yes he fires it during his talk.
What’s the deal Writing software is great, websites, applications, and scripts are things we interact with every day. What about writing software that we can interact with in the physical world? From automated sprinkler systems that turn off when you pull into your drive way, to scoreboards at the company foosball table physical computing opens a door for the innovator inside every software engineer.
It’s too hard Not true, there are amazing libraries and compilers that let us write software for Arduinos in the best language, Ruby. Think about it no C, no headers, and no static types, just plain old ruby. That is a good deal.
In this talk I will go over a few of the most popular Ruby libraries for interacting with an Arduino, talk about some basics of each library and then spend time on how these libraries and Arduino can interact to create applications that respond in the physical world. There will be t-shirts shot from a robotic cannon.
Welcome to the first of many Pivots Talking Tuesday blog posts! On a biweekly basis, we will be posting videos of Pivots speaking at conferences, user groups, and other awesome places. So if you didn’t get a chance to see us live, check back here once a week and get the lowdown on what we’re talking about.