Join us this Wednesday night at Pivotal Labs for Ruby talks and socializing.
6:30-7: appetizers & drinks
7-7:45ish: Slogging Through the Refactoring Swamp, 30 Minutes at a Time
Speaker: Ken Mayer
RED-GREEN-REFACTOR WITHOUT REFACTOR IS ABOUT AS USEFUL AS A TWO-LEGGED STOOL
The test-driven development “mantra” is red ➔ green ➔ refactor ⟲ repeat. It is an essential step in the development process. Without it, over time, your code will develop unnecessary dependencies, poor separation of responsibilities, confusing interfaces; the opposite of SOLID design.
HOW CAN I BE EXPECTED TO WORK UNDER THESE CONDITIONS?
Refactoring can be hard to balance against the urge to go right back in to delivering features. The good news, though, is that refactoring can take place anywhere, can be done solo, and can be done in pieces. Recently, when I needed to refactor an annoying patch of code in an open source project, I worked on it during my daily commute to and from the office. It didn’t interfere with client work or family time, and I accomplished a significant amount of work with zero opportunity cost. I’ll show you what that looks like, and how to fit refactoring in to an already-packed schedule.
IT’S OKAY TO MAKE MISTAKES
I won’t conceal my blunders with the benefit of hindsight, either. As I continued to refactor the code, I discovered new patterns where I could improve the overall design. My knowledge of the problem increased and that made things even better. So go ahead; Try something new or something that you read about last week. You have the “permission” to experiment.
8-8:30ish: Ruby for Big Data
Speaker: Ari Lerner
Ari will tell us about his experiences interacting with big data using Ruby!
8:30-9: wrap up, clean up, repair to a bar.