Close Sourcing as Strategy

Exceptions are Part of the Interface

Refactoring Nitrolinks Part 3: Pondo Cleanup

This is Part 3 of a series of posts about refactoring Nitrolinks out of Pondo. Last time we’ve successfully copied the Nitrolinks tests from Pondo but left the original tests on Pondo. This time we’ll move them out of Pondo for good.

Refactoring Nitrolinks, Part 2: Tests for a Rails Engine

This is Part 2 of a series of posts about refactoring Nitrolinks out of Pondo. Last time we’ve successfully moved Nitrolinks out of Pondo but we left most of the Nitrolinks-specific tests on the Pondo source code itself. This time we’ll move the tests to Nitrolinks so we can narrow Pondo’s test concerns.

Refactoring Nitrolinks, Part 1: Creating a Gem

I am building Pondo as an experiment on how to build a functional, modern web application without necessarily using a large front-end framework (e.g. Angular, Ember, React). The idea is to mostly develop applications as one would within the usual semantics of the normal Request-Response cycle. If you’ve used Pjax, or Turbolinks then you’re familiar with this.