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.

How to win at Tetris (and code)

by Ben

Problems in our code are less like “debt” & more like the clutter of unfilled lines that accumulate in Tetris, slowly but surely reducing our maneuvering room.

Source: How to win at Tetris (and code)

Tetris as a metaphor for technical debt.

If you think good architecture is expensive, try bad architecture

by Ben

Source: Daniel Bryant on Twitter

Technical Debt via Technical Drift

by Ben

Are you experiencing technical drift? – Code Climate Blog.

In summary: technical drift leads to technical debt, which can be prevented through iterative design.

This will definitely factor into the future plans for our codebase. Sometimes it’s easy to forget that you’re contemplating “Big Design” when you should really focus on iterative design.

From their post:

If you’re not taking an active role in refactoring your application every week chances are you’re experiencing “technical drift”. Having a problem space that is continually changing necessitates continuous reworking of how your application is designed — what Agile practitioners call “iterative design”. When you’re able to do this effectively, you can round off the peaks and avoid some of the pitfalls of Big Design.