Skip to main content

Benjamin Oakes

Photo of Ben Oakes

Hi, I'm Ben Oakes and this is my geek blog. Currently, I'm a Ruby/JavaScript Developer at Liaison. Previously, I was a Developer at Continuity and Hedgeye, a Research Assistant in the Early Social Cognition Lab at Yale University and a student at the University of Iowa. I also organize TechCorridor.io, ICRuby, OpenHack Iowa City, and previously organized NewHaven.rb. I have an amazing wife named Danielle Oakes.

Filtering for the Programming category. Clear

JWT: JSON Web Tokens

by Ben

JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties.

Source: JWT.IO

If you think good architecture is expensive, try bad architecture

by Ben

Source: Daniel Bryant on Twitter

Deleting Lines that don’t Match a Pattern

by Ben

And we want to delete all lines that don’t contain calculate. We can do that with :v. Simply running:

:v/calculate/d

Source: Deleting Lines that don’t Match a Pattern

Giving Up on TDD

by Ben

Not just the tests. You have to DESIGN period. No matter what you are writing; whether a unit test, or an acceptance test, or production code, or a mock, or a stub, you have to DESIGN.

Source: Clean Coder Blog

Lua as a Python’s secret weapon

by Ben

As you can see, it was easy to embed Lua in Python and the results are outstanding! Thus, we can say that Lua is definitely of a great help when you need to speed up some critical parts of your Python code.

Source: Lua as a Python’s secret weapon.

Google mtail

by Ben

extract whitebox monitoring data from application logs for collection in a timeseries database

Source: google/mtail

Using CCMenu with Travis CI

by Ben

CCMenu is a little tool for the OS X status bar to keep track of your repositories’ latest build status from the convenience of your Mac.

CCTray is the equivalent tool for your Windows environment, BuildNotify for Linux systems. The general instructions apply to all of them.

They were originally built for use with CruiseControl, but they work just as well with Travis CI, and you can use either to poll your Travis CI repositories and have their status show in the menu bar or tray.

Source: Using CCMenu with Travis CI – Travis CI

AMA: We pair program (almost) everything. Ask us anything!

by Ben

A talk I gave at Iowa Code Camp in May 2015.

Source: AMA: We pair program (almost) everything. Ask us anything!

Thoughtbot guides

by Ben

guides – A guide for programming in style.

Source: Thoughtbot guides

Jay Fields’ Thoughts: Testing: One assertion per test

by Ben

Limiting your tests to using one assertion is a controversial topic. I originally stumbled upon the idea on Dave Astels’ blog. I liked the style of development that Dave described and decided to give it a try, that was over 2 years ago. Since then I’ve worked on teams ranging from 4 developers to 16, codebases in Ruby and C#, and project timelines ranging from 3 months to 8. I think it’s fair to say I’ve given the concept plenty of chances to fall down. But, regardless of the variables, the guideline has always remained valuable.

For me, the main motivator for using one assertion per test is the resulting maintainability of the test. Tests that focus on one behavior of the system are almost always easier to write and to comprehend at a later date.

Source: Jay Fields’ Thoughts: Testing: One assertion per test